From: David Edelsohn <dje@watson.ibm.com>
To: degger@fhm.edu
Cc: gcc@gcc.gnu.org
Subject: Re: rs6000: Trivial code generation stupidity
Date: Mon, 17 Dec 2001 13:21:00 -0000 [thread overview]
Message-ID: <200112172120.QAA22932@makai.watson.ibm.com> (raw)
In-Reply-To: Message from degger@fhm.edu of "Mon, 17 Dec 2001 19:44:55 +0100." <20011217195138.8D51E6C3A@Nicole.fhm.edu>
>>>>> degger writes:
degger> Is there anything that can be done about it? Gcc 3.1 (or what it is now)
degger> generates quite good code for me at the moment except for in some really
degger> obvious cases (like the ones mentioned) and thus it would be a shame to
degger> give away some performance by those nasties.
Also, you can look at the output from intermediate passes and see
where gcc-2.95 chose the output in the correct register while gcc-3.1
introduces the extra copies. Track down which phase in gcc-3.1 is not
collapsing the register copies or why it is introducing register copies.
David
next prev parent reply other threads:[~2001-12-17 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-17 10:30 degger
2001-12-17 10:31 ` David Edelsohn
2001-12-17 12:54 ` degger
2001-12-17 13:12 ` David Edelsohn
2001-12-17 13:21 ` David Edelsohn [this message]
2001-12-18 3:53 ` Analysis try (was: Re: rs6000: Trivial code generation stupidity) degger
2001-12-25 23:13 ` cant_combine_insn_p hard_reg->reg moves David Edelsohn
2001-12-26 1:18 ` Richard Henderson
2001-12-26 4:13 ` Jan Hubicka
2001-12-26 11:25 ` Richard Henderson
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=200112172120.QAA22932@makai.watson.ibm.com \
--to=dje@watson.ibm.com \
--cc=degger@fhm.edu \
--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).