public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Pinski <pinskia@gmail.com>
Cc: Jie Zhang <jzhang918@gmail.com>, GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: Don't define USE_PT_GNU_EH_FRAME for uClibc
Date: Thu, 23 Aug 2007 12:20:00 -0000	[thread overview]
Message-ID: <20070823115921.GA11352@caradoc.them.org> (raw)
In-Reply-To: <de8d50360708230231y4e1bb032re3b34fac1724ac74@mail.gmail.com>

On Thu, Aug 23, 2007 at 02:31:39AM -0700, Andrew Pinski wrote:
> On 8/23/07, Jie Zhang <jzhang918@gmail.com> wrote:
> > 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.
> 
> This is wrong, it should never be pretending to be glibc.  This is
> just as bad as ICC pretending to be GCC.

Probably true, but irrelevant to Jie's patch.

-- 
Daniel Jacobowitz
CodeSourcery

  reply	other threads:[~2007-08-23 11:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-23  9:30 Jie Zhang
2007-08-23  9:46 ` Andrew Pinski
2007-08-23 12:20   ` Daniel Jacobowitz [this message]
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=20070823115921.GA11352@caradoc.them.org \
    --to=drow@false.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jzhang918@gmail.com \
    --cc=pinskia@gmail.com \
    /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).