From: Steven Bosscher <stevenb@suse.de>
To: gcc@gcc.gnu.org
Cc: fjahanian <fjahanian@apple.com>, Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: [RFH] - Less than optimal code compiling 252.eon -O2 for x86
Date: Sat, 25 Jun 2005 00:06:00 -0000 [thread overview]
Message-ID: <200506250206.23245.stevenb@suse.de> (raw)
In-Reply-To: <B2D126FA-DC85-4C3C-9006-39CE06374480@apple.com>
On Saturday 25 June 2005 01:48, fjahanian wrote:
> On Jun 24, 2005, at 3:16 PM, Andrew Pinski wrote:
> > I wonder why combine can do the simplification though which is why
> > still
> > produce good code for the simple testcase:
> > void f1(double *d,float *f2)
> > {
> > *f2 = 0.0;
> > *d = 0.0;
> > }
>
> It is hard to reproduce the simple test case, exhibiting the same
> problem (-O1 producing better code than -O2). Yes, small test cases
> move the desired simplification to other phases.
It often helps if you know what function your poorer code is in. You
could e.g. try to make the .optimized dump of that function compilable
and see if the problem shows up there again. Then work your way down
to something small.
Gr.
Steven
next prev parent reply other threads:[~2005-06-25 0:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 22:06 Fariborz Jahanian
2005-06-24 22:17 ` Andrew Pinski
2005-06-24 23:46 ` fjahanian
2005-06-25 0:06 ` Steven Bosscher [this message]
2005-06-30 14:42 ` fjahanian
2005-06-30 15:03 ` fjahanian
2005-06-27 19:20 ` Fariborz Jahanian
2005-06-27 19:56 ` Richard Henderson
2005-06-27 21:52 ` Fariborz Jahanian
2005-06-30 16:04 ` fjahanian
2005-06-30 16:08 ` Andrew Pinski
2005-06-30 16:55 ` Steven Bosscher
2005-06-30 17:48 ` Jeffrey A Law
2005-06-30 18:12 ` Bernd Schmidt
2005-06-30 18:19 ` Joe Buck
2005-06-30 18:25 ` Giovanni Bajo
2005-06-30 18:23 ` Jeffrey A Law
2005-06-30 19:06 ` Fariborz Jahanian
2005-06-30 19:47 ` Steven Bosscher
2005-06-30 21:30 ` Fariborz Jahanian
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=200506250206.23245.stevenb@suse.de \
--to=stevenb@suse.de \
--cc=fjahanian@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).