From: Ming Ouyang <mouyang@yahoo.com>
To: gcc@gcc.gnu.org
Cc: Dale Johannesen <dalej@apple.com>
Subject: Re: help on adding new insns like min/max
Date: Mon, 21 Oct 2002 17:39:00 -0000 [thread overview]
Message-ID: <20021021230559.19708.qmail@web13307.mail.yahoo.com> (raw)
In-Reply-To: <441B9D0E-E548-11D6-8BE6-000393D76DAA@apple.com>
I tried my gcc with definition of sminsi3/smaxsi3 and I dumpped
all debug info, gcc always treats min as a function call in my
test.c.00.rtl through test.c.30.dbr:
(call (mem:SI (symbol_ref/v:SI ("smin")) ))
I think once gcc found that is a function call, it would not
optimize it, am I right?
What I should get is something like "(smin: SI ...", is that right?
So probably I need to change something other than xxx.md?
Thanks.
--- Dale Johannesen <dalej@apple.com> wrote:
>
> On Monday, October 21, 2002, at 03:18 PM, Ming Ouyang wrote:
>
> > Dale,
> >
> > Thanks for your reply, but I wonder how gcc will handle code like:
> > c = min(a, b)
> > Does min/max will be treated as builtins? Or can you demonstrate
> > how to make gcc to use sminsi3/smaxsi3... to use min/max insns for
> > code like that?
>
> The optimization phases should create min/max from simpler RTL.
> See noce_try_minmax in ifcvt.c. That won't necessarily handle
> whatever case you want to handle, but it will give you an idea.
>
__________________________________________________
Do you Yahoo!?
Y! Web Hosting - Let the expert host your web site
http://webhosting.yahoo.com/
next parent reply other threads:[~2002-10-21 23:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <441B9D0E-E548-11D6-8BE6-000393D76DAA@apple.com>
2002-10-21 17:39 ` Ming Ouyang [this message]
2002-10-21 18:02 ` Dale Johannesen
2002-10-21 18:21 ` Ming Ouyang
2002-10-21 20:42 ` Ming Ouyang
2002-10-21 23:00 ` Andrew Pinski
2002-10-21 23:27 ` Ming Ouyang
2002-10-21 23:30 ` Andrew Pinski
2002-10-21 23:31 ` Ming Ouyang
2002-10-21 16:22 Ming Ouyang
2002-10-21 16:22 ` Dale Johannesen
2002-10-21 17:11 ` Ming Ouyang
2002-10-21 16:31 ` Jan Hubicka
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=20021021230559.19708.qmail@web13307.mail.yahoo.com \
--to=mouyang@yahoo.com \
--cc=dalej@apple.com \
--cc=gcc@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).