public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/13918] [3.3.3 regression] [ia64] bootstrap comparision failure Date: Thu, 29 Jan 2004 06:55:00 -0000 [thread overview] Message-ID: <20040129065533.9756.qmail@sources.redhat.com> (raw) In-Reply-To: <20040129063437.13918.debian-gcc@lists.debian.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-29 06:55 ------- Based a discusion with Zack, this is minor as yyou can still continue from this with just make and the compiler will still work right as it is just two instructions have been interchanged and in this case the order does not matter. see <http://gcc.gnu.org/ml/gcc/2003-07/msg00780.html> for even more info about this bug. (do not trust H. J. Lu on his analysis of the problem). -- What |Removed |Added ---------------------------------------------------------------------------- Severity|critical |minor http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13918
next prev parent reply other threads:[~2004-01-29 6:55 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-29 6:34 [Bug target/13918] New: " debian-gcc at lists dot debian dot org 2004-01-29 6:41 ` [Bug target/13918] " pinskia at gcc dot gnu dot org 2004-01-29 6:49 ` pinskia at gcc dot gnu dot org 2004-01-29 6:55 ` pinskia at gcc dot gnu dot org [this message] 2004-01-29 6:59 ` pinskia at gcc dot gnu dot org 2004-01-29 21:41 ` wilson at gcc dot gnu dot org 2004-02-15 12:43 ` gdr at gcc dot gnu dot org 2004-02-22 16:57 ` schwab at suse dot de 2004-02-22 17:01 ` gdr at integrable-solutions dot net 2004-02-22 17:56 ` cvs-commit at gcc dot gnu dot org 2004-02-22 17:59 ` schwab at suse dot de
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=20040129065533.9756.qmail@sources.redhat.com \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).