public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Tim Prince <tprince@computer.org>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: optimization/6010: sse code appears to have issues with some instructions
Date: Thu, 18 Apr 2002 08:36:00 -0000 [thread overview]
Message-ID: <20020418153603.29756.qmail@sources.redhat.com> (raw)
The following reply was made to PR optimization/6010; it has been noted by GNATS.
From: Tim Prince <tprince@computer.org>
To: Jan Hubicka <jh@suse.cz>
Cc: jakub@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
haganc@cray.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: optimization/6010: sse code appears to have issues with some instructions
Date: Thu, 18 Apr 2002 08:27:59 -0700
On Thursday 18 April 2002 07:15, Jan Hubicka wrote:
> > > Synopsis: sse code appears to have issues with some instructions
> >
> > Cau,
> > tak jsem zjistil, ze na to mam patch a dokonce uz zapprovovany (mam v tom
> > vetsi binec, nez bych cekal). Az dobootstrapuje, tak ho commitnu, takze
> > asi muzes bugreport uzavrit.
>
> Oops, I apologize for Czech Language, I tought I am sending email only to
> Jakub. I have patch approved to fix the testcase, so I will install it
> once re-bootstrapping passes.
>
> Honza
>
>
You'd better apologize to the language purity police, if any are watching.
Even I can see a significant non-Czech content there. Speaking of purity,
thanks for the work on weeding out the instructions which require P4.
--
Tim Prince
next reply other threads:[~2002-04-18 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-18 8:36 Tim Prince [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-05 15:14 hubicka
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=20020418153603.29756.qmail@sources.redhat.com \
--to=tprince@computer.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: 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).