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, haganc@cray.com,
	jh@suse.cz, nobody@gcc.gnu.org
Subject: Re: optimization/6010: sse code appears to have issues with some instructions
Date: Sun, 05 May 2002 15:14:00 -0000	[thread overview]
Message-ID: <20020505221412.19677.qmail@sources.redhat.com> (raw)

Synopsis: sse code appears to have issues with some instructions

State-Changed-From-To: analyzed->closed
State-Changed-By: hubicka
State-Changed-When: Sun May  5 15:14:12 2002
State-Changed-Why:
    Fixed and patch installed to 3.1.x/mainline tree.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=6010


             reply	other threads:[~2002-05-05 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-05 15:14 hubicka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-18  8:36 Tim Prince
2002-04-18  7:16 Jan Hubicka
2002-04-18  7:16 Jan Hubicka
2002-04-18  5:56 jakub
2002-03-19 23:16 haganc

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=20020505221412.19677.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=haganc@cray.com \
    --cc=jh@suse.cz \
    --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: 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).