public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@libertysurf.fr>
To: Nick Clifton <nickc@redhat.com>
Cc: Kelvin Lee <Kelvin.Lee@lansa.com.au>,
"'bug-binutils@gnu.org'" <bug-binutils@gnu.org>,
"'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>
Subject: Re: binutils-2.15 - work around for gcc optimization problem on sparc -sun-solaris2.7
Date: Wed, 14 Jul 2004 06:55:00 -0000 [thread overview]
Message-ID: <200407140856.08437.ebotcazou@libertysurf.fr> (raw)
In-Reply-To: <40F3DDB8.2050503@redhat.com>
> Thanks very much for discovering this problem and producing a
> workaround. I have applied the patch you suggested, together with this
> ChangeLog entry:
>
> bfd/ChangeLog
> 2004-07-13 Kelvin Lee <Kelvin.Lee@lansa.com.au>
>
> * elflink.c (elf_sort_symbol): Restructure code to avoid bug in
> Solairs hosted versions of gcc.
I'm a bit confused by this patch:
- is there really a bug "in Solaris hosted versions of gcc" involved here?
If so, it would be nice to produce a testcase and file a PR with GCC
bugzilla (cc-ing ebotcazou@gcc.gnu.org would be even nicer).
- is the bug reported by Kevin not a mere duplicate of
http://sources.redhat.com/ml/binutils/2004-06/msg00089.html
which has been fixed by
http://sources.redhat.com/ml/binutils/2004-06/msg00114.html
in which case the patch is superfluous and the ChangeLog entry a bit
misleading?
--
Eric Botcazou
next prev parent reply other threads:[~2004-07-14 6:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <817522051E65D511A2740001028074C4C2F507@EX1>
2004-07-13 12:55 ` Nick Clifton
2004-07-14 6:55 ` Eric Botcazou [this message]
2004-07-14 8:51 ` Nick Clifton
2004-07-14 9:58 ` Eric Botcazou
2004-07-14 13:54 ` Nick Clifton
2004-07-14 13:58 ` Nick Clifton
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=200407140856.08437.ebotcazou@libertysurf.fr \
--to=ebotcazou@libertysurf.fr \
--cc=Kelvin.Lee@lansa.com.au \
--cc=bug-binutils@gnu.org \
--cc=gcc-bugs@gcc.gnu.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).