public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rodrigc@gcc.gnu.org To: alan.jones@sun.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, rodrigc@gcc.gnu.org Subject: Re: target/1984: mis-ordering of op codes causes kernel panic Date: Sun, 02 Dec 2001 17:23:00 -0000 [thread overview] Message-ID: <20011203012309.8161.qmail@sources.redhat.com> (raw) Synopsis: mis-ordering of op codes causes kernel panic State-Changed-From-To: feedback->closed State-Changed-By: rodrigc State-Changed-When: Sun Dec 2 17:23:09 2001 State-Changed-Why: No feedback provided. Please try gcc 3.0.2 or the upcoming gcc 3.0.3 release and see if that solves the problem. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&pr=1984&database=gcc
next reply other threads:[~2001-12-03 1:23 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-12-02 17:23 rodrigc [this message] -- strict thread matches above, loose matches on Subject: below -- 2001-12-02 17:26 rodrigc 2001-09-17 17:02 rodrigc
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=20011203012309.8161.qmail@sources.redhat.com \ --to=rodrigc@gcc.gnu.org \ --cc=alan.jones@sun.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).