public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mrs@apple.com>
To: Joe Buck <Joe.Buck@synopsys.com>
Cc: Diego Novillo <dnovillo@redhat.com>, Syd Polk <spolk@apple.com>,
	GCC List <gcc@gcc.gnu.org>
Subject: Re: Help restricting args of an intrinsic function
Date: Mon, 02 Feb 2004 23:37:00 -0000	[thread overview]
Message-ID: <BB5C02CE-55D8-11D8-A1BE-003065A77310@apple.com> (raw)
In-Reply-To: <20040202152606.B7898@synopsys.com>

On Monday, February 2, 2004, at 03:26 PM, Joe Buck wrote:
> On Fri, Jan 30, 2004 at 07:59:34PM -0800, Mike Stump wrote:
>> On Friday, January 30, 2004, at 05:38  PM, Diego Novillo wrote:
>>> Yes, that's fine.  Here's what tree-ssa emits after the tree
>>> optimization passes for the test cases you mentioned.
>>
>> So, does your scheme work when the optimizer is off (-O0)?
>>
>> If not, why would that be a solution?
>
> Who says that exactly one instruction must be emitted with the 
> optimizer
> off?  It seems to me that it would suffice to have the builtin function
> emit the one instruction in the case where the mask arguments, after 
> any
> optimization, are constant, and otherwise emit whatever code is needed 
> to
> compute the correct result (or simply emit a call to a library 
> function).

This violates the users expectations.

The _point_ of having builtins for single machine instructions is so 
that the generated code will use them (or something better).  Tweaking 
a builtin to generate an external lib call or 5 instructions instead of 
using that one machine instruction isn't, uhm, winning.

The one case were it would be winning, is if you wanted to use x86 
builtins on the ppc and the compiler did its best to make it just work.

  reply	other threads:[~2004-02-02 23:37 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-31  0:53 Syd Polk
2004-01-31  0:54 ` Ian Lance Taylor
2004-01-31  1:21   ` Syd Polk
2004-01-31  1:38     ` Ian Lance Taylor
2004-01-31  1:52       ` David Edelsohn
2004-01-31  2:00         ` Syd Polk
2004-01-31  2:03           ` David Edelsohn
2004-01-31  2:20       ` Syd Polk
2004-01-31  3:18       ` Syd Polk
2004-01-31  0:55 ` Diego Novillo
2004-01-31  1:07   ` Syd Polk
2004-01-31  1:42     ` Diego Novillo
2004-01-31  4:29       ` Mike Stump
2004-01-31  7:34         ` Diego Novillo
2004-01-31  7:45           ` Mike Stump
2004-01-31 18:24             ` Diego Novillo
2004-02-02 19:58               ` Mike Stump
2004-02-02 23:44                 ` Syd Polk
2004-02-02 23:56                   ` Richard Henderson
2004-02-03  0:29                     ` Syd Polk
2004-02-03  0:39                       ` Richard Henderson
2004-02-02 23:26         ` Joe Buck
2004-02-02 23:37           ` Mike Stump [this message]
2004-02-02 23:45             ` Joe Buck
2004-02-03  0:31               ` Mike Stump
2004-02-03  0:35                 ` Daniel Jacobowitz
2004-02-03  1:16                   ` Mike Stump
2004-02-03  1:56                     ` Gabriel Dos Reis
2004-01-31  0:58 ` Ziemowit Laski
2004-01-31  1:38   ` Syd Polk
2004-01-31  8:12 ` Joseph S. Myers
2004-02-03 14:18 Etienne Lorrain

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=BB5C02CE-55D8-11D8-A1BE-003065A77310@apple.com \
    --to=mrs@apple.com \
    --cc=Joe.Buck@synopsys.com \
    --cc=dnovillo@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=spolk@apple.com \
    /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).