From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: NEED_REGISTER_FRAME_INFO can be replaced by -static-libgcc
Date: Tue, 13 Apr 2010 21:24:42 +0200 [thread overview]
Message-ID: <4BC4C4FA.2050005@gmail.com> (raw)
In-Reply-To: <4BC4C189.6020409@t-online.de>
[-- Attachment #1: Type: text/plain, Size: 875 bytes --]
Christian Franke wrote:
> Hi,
>
> a note regarding this fix:
>
>
> The *_frame_info symbols are set undefined to force linkage of the
> libgcc_s shared library or dll.
>
> This can be prevented by TARGET_LDFLAGS=-static-libgcc. To build from
> grub-1.98 tarball on Cygwin, run configure with this argument.
>
> May also be necessary on other build platforms when -shared-libgcc is
> the default. It may be possible simply set -static-libgcc
> unconditionally.
>
We already supply -lgcc --static-libgcc. Do you know why it still had
issues?
And I also doubt usefullness of pulling these functions since reference
to them is purely dummy: no relocation uses it so it will only increase
code size. Another concern is the behviour of these functions in grub
environment if they ever get called.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-04-13 19:25 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 [this message]
2010-04-14 10:35 ` Christian Franke
2010-04-17 20:52 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-04-19 15:13 ` Christian Franke
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=4BC4C4FA.2050005@gmail.com \
--to=phcoder@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.