From: David Edelsohn <dje@watson.ibm.com>
To: Gabriel Paubert <paubert@iram.es>
Cc: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>,
Sean Harding <sharding@dogcow.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: compiler optimization? something else?
Date: Fri, 10 Mar 2000 10:58:52 -0500 [thread overview]
Message-ID: <200003101558.KAA23082@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Gabriel Paubert <paubert@iram.es> of "Fri, 10 Mar 2000 10:18:36 +0100." <Pine.HPX.4.10.10003100954580.22162-100000@gra-ux1.iram.es>
>>>>> Gabriel Paubert writes:
Gabriel> If you don't have a 601 -fgfxopt might also help since it will generate
Gabriel> fsel instructions for min/max/conditional moves. fsel is unfortunately not
Gabriel> implemented on 601 so you can't set gfxopt for distributions.
Using the appropriate -mcpu=XXX option (e.g., -mcpu=604) sets
-fgfxopt accordingly.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-10 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20000308113436.A3472@dogcow.org>
2000-03-09 14:46 ` compiler optimization? something else? Franz Sirl
2000-03-09 16:04 ` David Edelsohn
2000-03-11 22:32 ` Giuliano Pochini
2000-03-11 19:44 ` David Edelsohn
2000-03-10 9:18 ` Gabriel Paubert
2000-03-10 15:58 ` David Edelsohn [this message]
2000-03-11 22:31 ` Giuliano Pochini
[not found] <Pine.GSO.4.05.10003081359150.17227-100000@ophelia.dogcow.org>
2000-03-09 7:33 ` Geert Uytterhoeven
2000-03-09 8:53 ` Timothy A. Seufert
2000-03-09 10:24 ` Gabriel Paubert
2000-03-08 23:01 Dan Bethe
[not found] <20000308204420.29276.qmail@web1705.mail.yahoo.com>
2000-03-08 21:22 ` David Edelsohn
[not found] <20000308150957.A12031@drow.res.cmu.edu>
2000-03-08 20:21 ` Sean Harding
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=200003101558.KAA23082@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=sharding@dogcow.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 NNTP newsgroup(s).