public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: rth@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, torbjorn.wassberg@swipnet.se Subject: Re: optimization/6845: ICE with -O -march=pentium3/pentium2/athlon Date: Tue, 28 May 2002 11:26:00 -0000 [thread overview] Message-ID: <20020528181240.15901.qmail@sources.redhat.com> (raw) Synopsis: ICE with -O -march=pentium3/pentium2/athlon State-Changed-From-To: open->feedback State-Changed-By: rth State-Changed-When: Tue May 28 11:12:39 2002 State-Changed-Why: Should have been fixed by Sun May 26 14:00:44 CEST 2002 Jan Hubicka <jh@suse.cz> * reload.c (find_valid_class): Accept new argument DEST, choose class accordingly. (push_reload): Update callers. Can you confirm? http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6845
next reply other threads:[~2002-05-28 18:12 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-05-28 11:26 rth [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-10-02 13:39 rth 2002-05-28 16:36 Torbjörn Wassberg 2002-05-28 14:06 rth 2002-05-28 6:56 torbjorn.wassberg
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=20020528181240.15901.qmail@sources.redhat.com \ --to=rth@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.org \ --cc=torbjorn.wassberg@swipnet.se \ /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).