public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Geoff Keating <geoffk@geoffk.org>,
	"mrs@apple.com" <mrs@apple.com>, "steby@enea.se" <steby@enea.se>,
	"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: GCC floating point usage
Date: Wed, 16 Oct 2002 14:56:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0210162240400.20702-100000@wotan.suse.de> (raw)
In-Reply-To: <359490000.1034799942@warlock.codesourcery.com>

Hi,

On Wed, 16 Oct 2002, Mark Mitchell wrote:

> > (a) Does this affect codegen when the new feature is not enabled?
> >     Zack's patch does, and it shouldn't.
>
> I certainly agree that people not using the flag should see no change.
>
> Why does Zack's patch do that, given his caveat that the sense of the
> flag would be reversed so that the flag is off by default?

Because it adds an additional insn pattern, with equal predicates as
the following one, but with different constraints.  This means, that in
the case this pattern is activated (which it is by default, given Zacks
changed default proposal) it will be preferred, which means, because it
only lists float regs in constraints, that float regs will be preferred.

Indeed I'm not even sure, that the second pattern will be used at all (if
the first is activated), because for insn recognition only predicates are
used, which make the first pattern match.  Then when reload is running it
doesn't rerecognize the insn, and instead reloads all operands of this
insn into either float regs or memory, which means, that _no_ integer regs
would be used at all for it.  That's one of the reason for the requirement
that things allowed by the predicates need to have at least one
alternative which accepts them.  And also that it's suboptimal to have
non-disjoint sets of predicates (i.e. which are active at the same time,
and match the same insns) with different constraints.


Ciao,
Michael.

  reply	other threads:[~2002-10-16 20:53 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-14  9:59 Stefan Bylund
2002-10-14 10:16 ` David Edelsohn
2002-10-14 10:25   ` Zack Weinberg
2002-10-14 10:55     ` Dale Johannesen
2002-10-14 22:22     ` Mark Mitchell
2002-10-15 15:35       ` Geoff Keating
2002-10-15 16:10         ` Mark Mitchell
2002-10-15 17:20           ` Geoff Keating
2002-10-15 18:09             ` Mark Mitchell
2002-10-16  7:40               ` Joel Sherrill
2002-10-15 19:04             ` Mike Stump
2002-10-16 12:06               ` Mark Mitchell
2002-10-16 13:35                 ` Geoff Keating
2002-10-16 14:29                   ` Mark Mitchell
2002-10-16 14:56                     ` Michael Matz [this message]
2002-10-16 15:03                       ` Mark Mitchell
2002-10-16 15:27                         ` David Edelsohn
2002-10-16 15:36                           ` Mark Mitchell
2002-10-16 16:35                             ` Zack Weinberg
2002-10-16 16:36                               ` Mark Mitchell
2002-10-16 16:46                             ` David Edelsohn
2002-10-17  8:37                             ` Paul Koning
2002-10-16 17:57                           ` Mike Stump
2002-10-17  4:12                   ` Mike Stump
2002-10-16 13:43               ` Richard Henderson
2002-10-16 14:35                 ` Mark Mitchell
2002-10-16 14:56                   ` Joel Sherrill
2002-10-16 16:38                   ` Richard Henderson
2002-10-16 16:53                     ` Zack Weinberg
2002-10-16 17:52                       ` Michael Matz
2002-10-16 22:50                       ` Richard Henderson
2002-10-21 12:21                         ` Jeff Law
2002-10-16 17:29                 ` Mike Stump
2002-10-17  2:19                   ` Richard Henderson
2002-10-15 17:19         ` Mike Stump
2002-10-15 18:41         ` Zack Weinberg
2002-10-16  1:48           ` Fergus Henderson
2002-10-14 10:37   ` Stefan Bylund
2002-10-14 11:28     ` Mike Stump
2002-10-14 12:39       ` Joel Sherrill

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=Pine.LNX.4.33.0210162240400.20702-100000@wotan.suse.de \
    --to=matz@suse.de \
    --cc=gcc@gcc.gnu.org \
    --cc=geoffk@geoffk.org \
    --cc=mark@codesourcery.com \
    --cc=mrs@apple.com \
    --cc=steby@enea.se \
    /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).