public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: middle-end/7198: ia64.md missing usual fnma patterns
Date: Sat, 01 Mar 2003 14:46:00 -0000	[thread overview]
Message-ID: <20030301144600.23755.qmail@sources.redhat.com> (raw)

The following reply was made to PR target/7198; it has been noted by GNATS.

From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: tprince@computer.org
Cc: gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Subject: Re: middle-end/7198: ia64.md missing usual fnma patterns
Date: 01 Mar 2003 15:44:36 +0100

 Op za 01-03-2003, om 15:28 schreef Tim Prince:
 > On Saturday 01 March 2003 04:01, Steven Bosscher wrote:
 > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&
 > >pr=7198
 > >
 > > Does this bug still exist in the 3.3 branch and mainline?  It looks like
 > > the patterns from your patch are already in ia64.md.
 > That's interesting; I don't find them in the gcc-20030224 (3.3) snapshot.  In 
 > fact, I just checked this week, and that snapshot was not employing fnma 
 > instructions in my test code, so I applied this patch again.  The patterns 
 > which came in ia64.md require a sign change, to match the more common source 
 > code pattern, so it seems that a pattern with the sign change already applied 
 > is needed.
 
 Ah, you're right, I overlooked the "neg:[SDT]F" part" in ia64.md.
 
 


             reply	other threads:[~2003-03-01 14:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-01 14:46 Steven Bosscher [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-01 14:36 Tim Prince
2003-03-01 12:06 Steven Bosscher
2002-07-03  8:36 tprince

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=20030301144600.23755.qmail@sources.redhat.com \
    --to=s.bosscher@student.tudelft.nl \
    --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).