From: Bradley Lucier <lucier@math.purdue.edu>
To: neroden@fastmail.fm
Cc: Bradley Lucier <lucier@math.purdue.edu>, gcc@gcc.gnu.org
Subject: Re: wrong-code regressions review
Date: Wed, 15 Dec 2004 01:28:00 -0000 [thread overview]
Message-ID: <95C1438C-4E38-11D9-A170-003065BA681E@math.purdue.edu> (raw)
18548 is a regression (and it's not target specific, it happens on
sparc-solaris, x86-linux, and ppc-darwin), but it's very hard to figure
out what is causing the current problem. There were two previous
wrong-code regressions on this code base that have been fixed by
unrelated patches, so I don't know if fixing 18548 will just bring
other problems to the surface.
Brad
next reply other threads:[~2004-12-15 1:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 1:28 Bradley Lucier [this message]
2004-12-15 13:12 ` Giovanni Bajo
2004-12-15 13:42 ` Andrew Pinski
2004-12-15 14:54 ` Bradley Lucier
2004-12-15 15:10 ` Bradley Lucier
2004-12-15 15:15 ` Giovanni Bajo
2004-12-15 21:23 ` Bradley Lucier
2004-12-15 21:29 ` Daniel Jacobowitz
2004-12-16 1:18 ` Bradley Lucier
2004-12-15 21:37 ` Giovanni Bajo
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 19:52 Nathanael Nerode
2004-12-14 19:56 ` Jeffrey A Law
2004-12-14 20:46 ` David Edelsohn
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=95C1438C-4E38-11D9-A170-003065BA681E@math.purdue.edu \
--to=lucier@math.purdue.edu \
--cc=gcc@gcc.gnu.org \
--cc=neroden@fastmail.fm \
/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).