From: Scott Robert Ladd <coyote@coyotegulch.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Status Report (2004-09-13)
Date: Wed, 15 Sep 2004 21:25:00 -0000 [thread overview]
Message-ID: <4148A7A2.2030309@coyotegulch.com> (raw)
In-Reply-To: <414627A4.4080109@codesourcery.com>
Mark Mitchell wrote:
> Some people have expressed interest in knowing which PRs I see as
> particularly high priority. For now, I'm going to confine myself to
> wrong-code bugs -- of which there are 35.
>
> For now, I've confined myself to wrong-code regressions; here are some
> that concern me especially much:
Two bugs that are giving Gentoo-amd64 developers a stomache ache include
15617 and 14631, both "wrong code" problems with SSE code generation. As
-mfpmath=sse is default for AMD64, this is causing problems in using
GCC 3.4.2 for gentoo's 2004.3 release.
Neither bug is assigned, though one (14631) appears to have had an
unsubmitted patch. I'm willing to look at these if no one else is.
..Scott
--
Scott Robert Ladd
site: http://www.coyotegulch.com
blog: http://chaoticcoyote.blogspot.com
next prev parent reply other threads:[~2004-09-15 20:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-14 0:30 Mark Mitchell
2004-09-14 1:14 ` Andrew Pinski
2004-09-14 1:28 ` Jan Hubicka
2004-09-14 5:02 ` Jeffrey A Law
2004-09-14 5:58 ` Mark Mitchell
2004-09-14 6:29 ` Jeffrey A Law
2004-09-14 15:54 ` Jan Hubicka
2004-09-14 17:07 ` Mark Mitchell
2004-09-14 6:28 ` Mark Mitchell
2004-09-15 21:25 ` Scott Robert Ladd [this message]
2004-09-16 21:58 ` Mark Mitchell
2004-09-16 15:58 ` GCC Status Report (2004-09-13) [--enable-mapped-location] Per Bothner
2004-09-16 18:45 ` Mark Mitchell
2004-09-16 18:56 ` Per Bothner
2004-09-16 19:02 ` Mark Mitchell
2004-09-16 19:03 ` Matt Austern
2004-09-16 19:31 ` Mark Mitchell
2004-09-16 22:50 ` Steven Bosscher
2004-09-16 19:28 ` Per Bothner
2004-09-16 19:46 ` Mark Mitchell
2004-09-14 4:48 GCC Status Report (2004-09-13) Wolfgang Bangerth
2004-09-18 11:02 Paolo Bonzini
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=4148A7A2.2030309@coyotegulch.com \
--to=coyote@coyotegulch.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.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).