From: "Eric Botcazou" <ebotcazou@libertysurf.fr>
To: "Greg Schafer" <gschafer@zip.com.au>, "DJ Delorie" <dj@redhat.com>
Cc: <binutils@sourceware.org>
Subject: Re: GNU hash-style compatibility problem on x86_64
Date: Sat, 25 Aug 2007 00:05:00 -0000 [thread overview]
Message-ID: <02ba01c7e687$368de1f0$0a00000a@galilee> (raw)
In-Reply-To: <20070815005828.GA1267@eyo32.local>
> But it's still a mystery why x86 and ppc don't need this.. oh well.
Their BFD backend is more liberal and accepts sections with unknown IDs.
--
Eric Botcazou
next prev parent reply other threads:[~2007-08-24 19:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-14 7:22 Greg Schafer
2007-08-14 12:48 ` H.J. Lu
2007-08-14 12:56 ` Daniel Jacobowitz
2007-08-14 13:02 ` H.J. Lu
2007-08-14 13:07 ` Mike Frysinger
2007-08-14 13:23 ` Jakub Jelinek
2007-08-14 13:31 ` Mike Frysinger
2007-08-14 13:39 ` Daniel Jacobowitz
2007-08-14 22:45 ` Greg Schafer
2007-08-14 23:35 ` DJ Delorie
2007-08-15 0:58 ` Greg Schafer
2007-08-15 1:01 ` DJ Delorie
2007-08-25 0:05 ` Eric Botcazou [this message]
2007-08-29 17:12 ` Mike Frysinger
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='02ba01c7e687$368de1f0$0a00000a@galilee' \
--to=ebotcazou@libertysurf.fr \
--cc=binutils@sourceware.org \
--cc=dj@redhat.com \
--cc=gschafer@zip.com.au \
/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).