From: Andrew Pinski <pinskia@physics.uc.edu>
To: Sergei Organov <osv@topconrd.ru>
Cc: gcc@gcc.gnu.org
Subject: Re: How to replace -O1 with corresponding -f's?
Date: Mon, 20 Jun 2005 15:36:00 -0000 [thread overview]
Message-ID: <a4baf1b1fb19764a670afa80d385edd2@physics.uc.edu> (raw)
In-Reply-To: <87r7ex82ur.fsf@osv.topcon.com>
On Jun 20, 2005, at 11:28 AM, Sergei Organov wrote:
> Andrew Pinski <pinskia@physics.uc.edu> writes:
>
>> On Jun 20, 2005, at 10:54 AM, Sergei Organov wrote:
>>
>>> so SYMBOL_FLAG_SMALL (flags 0x6 vs 0x2) is somehow being missed when
>>> -O1
>>
>>> is turned on. Seems to be something at tree-to-RTX conversion time.
>>> Constant folding?
>>
>> No, it would mean that the target says that this is not a small data.
>> Also try it with the following code and you will see there is no
>> difference:
>>
>> double osvf() { return 314314314; }
>
> There is no difference in the sense that here both -O0 and -O1 behave
> roughly the same. So the problem is with detecting "smallness" for true
> constants by the target, right?
I think the bug is in rs6000_elf_in_small_data_p but since I have not
debuged it yet I don't know for sure.
Could you file a bug? This is a target bug.
-- Pinski
next prev parent reply other threads:[~2005-06-20 15:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-20 13:40 Sergei Organov
2005-06-20 14:04 ` Andrew Haley
2005-06-20 14:26 ` Andrew Pinski
2005-06-20 14:55 ` Sergei Organov
2005-06-20 15:01 ` Andrew Pinski
2005-06-20 15:29 ` Sergei Organov
2005-06-20 15:36 ` Andrew Pinski [this message]
2005-06-20 15:58 ` Sergei Organov
2005-06-21 9:55 ` Michael Meissner
2005-06-21 12:49 ` Sergei Organov
2005-06-20 17:18 ` Sergei Organov
2005-06-24 16:09 ` Sergei Organov
2005-06-20 14:28 ` Sergei Organov
2005-06-22 19:29 ` Zack Weinberg
2005-06-20 14:25 ` Scott Robert Ladd
2005-06-20 14:35 ` Andrew Pinski
2005-06-20 15:04 ` Sergei Organov
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=a4baf1b1fb19764a670afa80d385edd2@physics.uc.edu \
--to=pinskia@physics.uc.edu \
--cc=gcc@gcc.gnu.org \
--cc=osv@topconrd.ru \
/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).