Grub Development Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: NEED_REGISTER_FRAME_INFO can be replaced by -static-libgcc
Date: Mon, 19 Apr 2010 17:13:10 +0200	[thread overview]
Message-ID: <4BCC7306.8030501@t-online.de> (raw)
In-Reply-To: <4BCA1F7B.7080601@gmail.com>

Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> Christian Franke wrote:
>    
>>
>> According to 'gcc -dumpspecs' of Cygwin gcc 4.3.4-3, options '-u
>> ___[de]register_frame_info' are always passed to the linker if
>> -static-libgcc is not specified. This is Cygwin and MinGW specific: In
>> the exe startup code these symbols are loaded only if present, so the
>> DLL must be forced to load first.
>>
>> As a consequence, the symbols are also set undefined when the GRUB
>> pre-*.o files are generated with 'ld -r'.
>>
>> The attached patch works for me with the bzr revision preceding the
>> NEED_REGISTER_FRAME_INFO fix.
>>
>>      
> Doesn't it risk linking e.g. __bswapsi2 into every module which uses it
> during partial link? It would increase module size on RISC
>    

Partial linking with '-Wl,-r' does never pull any code from libraries. 
Specifying '-lgcc' has no effect in this case.

Cannot test this on RISC, it is at least true on i686-linux, -freebsd 
and -cygwin.

-- 
Regards,
Christian Franke




  reply	other threads:[~2010-04-19 15:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-13 19:10 NEED_REGISTER_FRAME_INFO can be replaced by -static-libgcc Christian Franke
2010-04-13 19:24 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-14 10:35   ` Christian Franke
2010-04-17 20:52     ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-19 15:13       ` Christian Franke [this message]
2010-04-24 21:19     ` Vladimir 'φ-coder/phcoder' Serbinenko

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BCC7306.8030501@t-online.de \
    --to=christian.franke@t-online.de \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox