public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wilson at specifixinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/7198] [IA64] missing usual fnma patterns
Date: Mon, 26 Jan 2004 23:44:00 -0000	[thread overview]
Message-ID: <20040126234440.2037.qmail@sources.redhat.com> (raw)
In-Reply-To: <20020703083601.7198.tprince@computer.org>


------- Additional Comments From wilson at specifixinc dot com  2004-01-26 23:44 -------
Subject: Re: Candidate patch for PR 7198

On Mon, 2004-01-26 at 10:23, Zack Weinberg wrote:
> Here's a candidate patch for PR 7198.  I cannot bootstrap mainline due
> to what looks like an unrelated bug in cselib.  However, the trivial
> test case

There is a known problem with sched-ebb's use of cselib that results in
accesses to memory that has already been freed.  This causes bootstrap
compare problems that go away if your environment size changes. 
However, I'd call this a sched-ebb bug rather than a cselib bug, because
sched-ebb is using cselib in a way that it was never designed for.  I've
never seen this on my machine, and there have been so many other IA-64
problems to deal with that it has never made it to my high priority list
of problems.  This doesn't result in incorrect code, it only results in
code that is scheduled differently.

Thanks for fixing PR 7198.

I don't really see a need for the nmaddsf4_alts pattern.  This can only
be created via expanders, and we currently don't have any expanders that
need it.  It doesn't hurt to have it though, and it does make the
patterns more symmetrical, so I don't mind if you add it.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7198


  parent reply	other threads:[~2004-01-26 23:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020703083601.7198.tprince@computer.org>
2003-06-02  3:46 ` dhazeghi@yahoo.com
2003-12-09 23:16 ` dhazeghi at yahoo dot com
2003-12-16 10:04 ` wilson at gcc dot gnu dot org
2003-12-16 14:57 ` tprince at computer dot org
2004-01-26 23:44 ` wilson at specifixinc dot com [this message]
2004-01-27 18:04 ` zack at codesourcery dot com
2004-01-28  0:08 ` wilson at specifixinc dot com
2004-01-28 21:40 ` zack at gcc dot gnu dot org
2004-01-28 21:43 ` pinskia at gcc dot gnu dot org

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=20040126234440.2037.qmail@sources.redhat.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).