public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: hubicka@gcc.gnu.org To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, jh@suse.cz, kelleycook@comcast.net, nobody@gcc.gnu.org Subject: Re: target/9068: [3.4 regression] [x86] comisd & comiss constraints are incorrect Date: Fri, 21 Mar 2003 21:09:00 -0000 [thread overview] Message-ID: <20030321210948.16662.qmail@sources.redhat.com> (raw) Synopsis: [3.4 regression] [x86] comisd & comiss constraints are incorrect State-Changed-From-To: analyzed->closed State-Changed-By: hubicka State-Changed-When: Fri Mar 21 21:09:48 2003 State-Changed-Why: Fixed by my earlier patch http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9068
next reply other threads:[~2003-03-21 21:09 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-21 21:09 hubicka [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-01-11 10:06 Jan Hubicka 2003-01-11 0:32 bangerth
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=20030321210948.16662.qmail@sources.redhat.com \ --to=hubicka@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ --cc=gcc-gnats@gcc.gnu.org \ --cc=gcc-prs@gcc.gnu.org \ --cc=jh@suse.cz \ --cc=kelleycook@comcast.net \ --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).