From: Jie Zhang <jzhang918@gmail.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Don't define USE_PT_GNU_EH_FRAME for uClibc
Date: Thu, 23 Aug 2007 09:30:00 -0000 [thread overview]
Message-ID: <46CD5396.8020302@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 204 bytes --]
uClibc pretends to be glibc 2.2. But currently it doesn't use
PT_GNU_EH_FRAME segment. So we cannot define USE_PT_GNU_EH_FRAME and
have to register and deregister frame info.
Is it OK to commit?
Jie
[-- Attachment #2: crtstuff-uclibc.diff --]
[-- Type: text/x-patch, Size: 800 bytes --]
* crtstuff.c (USE_PT_GNU_EH_FRAME): Don't define for uClibc.
Index: crtstuff.c
===================================================================
--- crtstuff.c (revision 127728)
+++ crtstuff.c (working copy)
@@ -92,7 +92,10 @@ call_ ## FUNC (void) \
&& !defined(inhibit_libc) && !defined(CRTSTUFFT_O) \
&& defined(__GLIBC__) && __GLIBC__ >= 2
#include <link.h>
-# if (__GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ > 2) \
+/* uClibc pretends to be glibc 2.2 and DT_CONFIG is defined in its link.h.
+ But it doesn't use PT_GNU_EH_FRAME ELF segment currently. */
+# if !defined(__UCLIBC__) \
+ && (__GLIBC__ > 2 || (__GLIBC__ == 2 && __GLIBC_MINOR__ > 2) \
|| (__GLIBC__ == 2 && __GLIBC_MINOR__ == 2 && defined(DT_CONFIG)))
# define USE_PT_GNU_EH_FRAME
# endif
next reply other threads:[~2007-08-23 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 9:30 Jie Zhang [this message]
2007-08-23 9:46 ` Andrew Pinski
2007-08-23 12:20 ` Daniel Jacobowitz
2007-08-23 14:50 ` Bernd Schmidt
2007-08-24 4:06 ` Jie Zhang
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=46CD5396.8020302@gmail.com \
--to=jzhang918@gmail.com \
--cc=gcc-patches@gcc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).