From: cgd@broadcom.com
To: "Andrew Cagney" <cagney@gnu.org>
Cc: "Richard Sandiford" <rsandifo@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: [rfa/mips] Second go at vr5500 hilo hazard fix
Date: Fri, 26 Mar 2004 00:01:00 -0000 [thread overview]
Message-ID: <yov5fzbw7a07.fsf@ldt-sj3-010.sj.broadcom.com> (raw)
In-Reply-To: <406359BA.9000302@gnu.org>
At Thu, 25 Mar 2004 17:14:18 -0500, Andrew Cagney wrote:
> Look at it this way, if the igen mechanism is used, gcc is able to
> eliminate everything :-)
In the case of a single-architecture sim (i.e., not 'multi', then
yes), GCC will automatically eliminate the test.
In the case of a multiple-architecture sim, it won't. But (a) at
least in my mind, i'm not worried about absolute maximal performance
from that configuration (if you want max performance, build a single
arch sim), and (b) until somebody quantifies the difference, I'll
claim that i don't believe it'll be a measurable difference. 8-)
cgd
next prev parent reply other threads:[~2004-03-26 0:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 15:05 Richard Sandiford
[not found] ` <mailpost.1079622402.27828@news-sj1-1>
2004-03-19 0:09 ` cgd
2004-03-18 17:57 ` cgd
2004-03-18 20:55 ` Richard Sandiford
2004-03-19 0:09 ` Richard Sandiford
2004-03-19 15:19 ` Andrew Cagney
2004-03-24 7:59 ` Richard Sandiford
2004-03-24 15:59 ` cgd
2004-03-25 7:15 ` cgd
2004-03-25 7:45 ` Richard Sandiford
[not found] ` <mailpost.1080200738.13330@news-sj1-1>
2004-03-25 18:53 ` cgd
2004-03-25 22:14 ` Andrew Cagney
2004-03-26 0:01 ` cgd [this message]
2004-03-26 0:28 ` Andrew Cagney
[not found] ` <mailpost.1080260907.10999@news-sj1-1>
2004-03-26 2:19 ` cgd
2004-03-28 10:16 ` Richard Sandiford
[not found] ` <mailpost.1080469040.8967@news-sj1-1>
2004-03-29 19:38 ` cgd
2004-04-10 6:59 ` cgd
2004-03-19 0:09 ` Richard Sandiford
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=yov5fzbw7a07.fsf@ldt-sj3-010.sj.broadcom.com \
--to=cgd@broadcom.com \
--cc=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=rsandifo@redhat.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