From: Richard Earnshaw <rearnsha@arm.com>
To: Joe Buck <Joe.Buck@synopsys.com>
Cc: Richard Earnshaw <rearnsha@arm.com>,
Philip Blundell <pb@nexus.co.uk>,
Matthias Klose <doko@cs.tu-berlin.de>,
gcc@gcc.gnu.org, debian-gcc@lists.debian.org, gt@debian.org,
pb@debian.org
Subject: Re: 3.3.4 status, and some questions
Date: Fri, 12 Mar 2004 17:23:00 -0000 [thread overview]
Message-ID: <200403121723.i2CHNDts003791@pc960.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Fri, 12 Mar 2004 09:18:48 PST." <20040312091848.A5904@synopsys.com>
> > I don't think there is a PR for it since the code in question does not
> > provoke the bug on a vanilla FSF build.
>
> Now I'm confused. If the bug is not present in 3.3.3, then what is there
> to backport?
The bug is present, by inspection.
> Or are you saying that the bug is present, but that this
> particular testcase doesn't tweak the bug because of some other difference
> between Debian's gcc and ours?
That seems to be the case.
R.
next prev parent reply other threads:[~2004-03-12 17:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 23:58 Joe Buck
2004-03-12 2:49 ` Ian Lance Taylor
2004-03-12 6:42 ` Matthias Klose
2004-03-12 10:44 ` Philip Blundell
2004-03-12 12:08 ` Richard Earnshaw
2004-03-12 12:44 ` Philip Blundell
2004-03-12 17:18 ` Joe Buck
2004-03-12 17:23 ` Richard Earnshaw [this message]
2004-03-12 16:46 ` Joe Buck
2004-03-12 16:50 ` Phil Blundell
2004-03-12 17:12 ` Joe Buck
2004-03-12 13:21 ` Gerhard Tonn
2004-03-12 17:17 ` Phil Blundell
2004-03-12 6:58 ` Gabriel Dos Reis
2004-03-12 9:57 ` Andreas Schwab
2004-03-14 22:12 ` Hans-Peter Nilsson
2004-03-16 8:57 ` Jim Wilson
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=200403121723.i2CHNDts003791@pc960.cambridge.arm.com \
--to=rearnsha@arm.com \
--cc=Joe.Buck@synopsys.com \
--cc=debian-gcc@lists.debian.org \
--cc=doko@cs.tu-berlin.de \
--cc=gcc@gcc.gnu.org \
--cc=gt@debian.org \
--cc=pb@debian.org \
--cc=pb@nexus.co.uk \
/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).