From: Alexandre Oliva <aoliva@redhat.com>
To: "H. J. Lu" <hjl@lucon.org>
Cc: R Hill <dirtyepic.sk@gmail.com>, Nick Clifton <nickc@redhat.com>,
binutils@sources.redhat.com
Subject: Re: can't build x86-32 libc on x86-64 with mainline binutils
Date: Sun, 30 Apr 2006 06:53:00 -0000 [thread overview]
Message-ID: <or3bfwushl.fsf@free.oliva.athome.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20060429145053.GA3225@lucon.org> (H. J. Lu's message of "Sat, 29 Apr 2006 07:50:53 -0700")
On Apr 29, 2006, "H. J. Lu" <hjl@lucon.org> wrote:
> On Sat, Apr 29, 2006 at 12:14:03AM -0600, R Hill wrote:
>>
>> Testcase is:
>>
>> .tfloat 1.442695040888963407359924681002
>>
>> Binutils is 2.16.92, configured with:
>>
> It works for me with binutils in CVS and the Linux binutils
> 2.16.91.0.7. Does the Linux binutils 2.16.91.0.7 work for you?
H.J., we've gone through this before. You didn't use GCC trunk to
build binutils, which is what triggers the bug.
--
Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/
Secretary for FSF Latin America http://www.fsfla.org/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}
next prev parent reply other threads:[~2006-04-29 18:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-02 18:07 Alexandre Oliva
2006-03-02 18:33 ` H. J. Lu
2006-03-02 18:44 ` Alexandre Oliva
2006-03-02 18:49 ` H. J. Lu
2006-03-02 18:56 ` Alexandre Oliva
2006-03-02 19:01 ` H. J. Lu
2006-03-03 9:56 ` Nick Clifton
2006-04-29 23:54 ` R Hill
2006-04-30 0:02 ` H. J. Lu
2006-04-30 6:53 ` Alexandre Oliva [this message]
2006-04-30 11:23 ` Gcc 4.2 miscompiles binutils on x86 and x86-64 H. J. Lu
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=or3bfwushl.fsf@free.oliva.athome.lsd.ic.unicamp.br \
--to=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=dirtyepic.sk@gmail.com \
--cc=hjl@lucon.org \
--cc=nickc@redhat.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).