From: Sanjiv Kumar Gupta <sanjiv.gupta@oracle.com>
To: Ian Lance Taylor <ian@airs.com>
Cc: Sanjiv Kumar Gupta <skgnu@yahoo.com>, gcc@gcc.gnu.org
Subject: Re: GCC 3.3.1 -O2 problem with sqrt.c
Date: Mon, 30 May 2005 15:28:00 -0000 [thread overview]
Message-ID: <429B1B23.8070301@oracle.com> (raw)
In-Reply-To: <m3br6wbt9u.fsf@gossamer.airs.com>
Ian Lance Taylor wrote:
> Sanjiv Kumar Gupta <skgnu@yahoo.com> writes:
>
>
>>I am using gcc 3.3.1 release as my port, and looks
>>like I have hit a problem with greg.
>
>
> You neglected to mention what target you are using.
>
Ian, the port is for a 32-bit RISC and not complete yet,
hence still not contributed.
This probably makes difficult for you to suggest any
fix, but I still asked in case I could get any pointers
for investigation.
>
>>I couldn't understand why the insns 620 and 621 are
>>being generated here as DI moves.
>
>
> I'm not sure specifically why it got a DI move here, but it doesn't
> look wrong. It's treating the struct named parts as DImode.
>
>
>>This is creating problem since insn 621 gets splitted
>>after reload into two SI moves,i.e. @(r21, -8) and
>>@(r21, -4).
>>This renders insns 619 as dead and hence insns 618 and
>>insn 429 as dead, which are eliminated by flow2.
>
>
> It does look rather suspicious, but it's hard to know whether it is
> wrong without seeing the value in r1.
>
r1 looks unrelated to struct members, and is being used by the
ifcvt pass to expand some comparison insns.
> Does the behaviour change if you use -fno-strict-aliasing? (I can't
> remember what the default was in 3.3.1).
>
> Ian
>
The behaviour doesn't changes with -fno-strict-aliasing or
-fstrict-aliasing.
Thanks
Sanjiv
next prev parent reply other threads:[~2005-05-30 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-27 13:42 Sanjiv Kumar Gupta
2005-05-27 17:49 ` Ian Lance Taylor
2005-05-30 15:28 ` Sanjiv Kumar Gupta [this message]
2005-06-02 13:19 ` Dave Korn
2005-06-04 2:58 ` Ian Lance Taylor
2005-06-17 12:55 ` Sanjiv Kumar Gupta
2005-05-30 15:28 ` Sanjiv Kumar Gupta
2005-05-31 12:13 ` Sanjiv Kumar Gupta
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=429B1B23.8070301@oracle.com \
--to=sanjiv.gupta@oracle.com \
--cc=gcc@gcc.gnu.org \
--cc=ian@airs.com \
--cc=skgnu@yahoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).