[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [avr-gcc-list] modulo vs. loop (gcc 4.3.x bug)

From: Erik Christiansen
Subject: Re: [avr-gcc-list] modulo vs. loop (gcc 4.3.x bug)
Date: Mon, 29 Mar 2010 17:07:16 +1100
User-agent: Mutt/1.5.15+20070412 (2007-04-11)

On Mon, Mar 29, 2010 at 06:19:51AM +0200, Joerg Wunsch wrote:
> Erik Christiansen <address@hidden> wrote:
> > Since the discussion has proceeded this far, you've presumably not had
> > satisfaction from choosing for yourself where a function lives?:
> > 
> > void foo(void) __attribute__ ((section (".bootloader")));
> That doesn't really help to also place functions from libgcc.a into
> a separate section.

Ah, that is a rather special case. It is possible to edit the function
prototypes in the gcc source, and build a custom compiler for this
special task, but is the section attribute preserved in an archive?  

It may be more convenient and reliable to use -nodefaultlibs, instead of
modifying gcc, and supply a copy of the the functions ourselves, with
modified function prototypes. Alternatively, simple linker scripting
provides full control of placement, with unmodified code.

That seems a small effort, especially if the result is highly desirable.

Note: I am just guessing that a simple:

     mysection : { libgcc.a(.*) }

     in the linker script won't be honoured during the process of
     satisfying missing externals from an archive. I haven't checked
     whether that could be all that is needed to do the job.


If at first you don't succeed, destroy all evidence that you tried.
                           - Ralf Hildebrandt, on postfix-users.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]