public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/62631] gcc.dg/tree-ssa/ivopts-lt-2.c FAILs
Date: Sat, 07 Feb 2015 23:14:00 -0000 [thread overview]
Message-ID: <bug-62631-4-6XfPYsb2yo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-62631-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62631
--- Comment #27 from dave.anglin at bell dot net ---
On 2015-02-07, at 5:24 PM, ebotcazou at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62631
>
> --- Comment #26 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
>> The generated code on PA looks optimal to me:
>>
>> zdep %r25,29,30,%r28
>> b .L2
>> ldi 99,%r19
>> .L6:
>> zdep %r25,29,30,%r28
>> .L2:
>> addl %r26,%r28,%r28
>> ldo 1(%r25),%r25
>> comb,>>= %r19,%r25,.L6
>> stw %r0,0(%r28)
>> bv,n %r0(%r2)
>
> For most other architectures the BIV (%r25) is eliminated to the GIV (%r28) so
> you only have one additive operation in the loop. This happens for 64-bit PA:
>
> .L5:
> ldo 4(%r26),%r26
> cmpb,*>>,n %r28,%r26,.L5
> stw %r0,0(%r26)
> bve,n (%r2)
>
> Why couldn't such a code be generated for 32-bit PA too?
There is no reason that I can see.
Dave
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2015-02-07 23:14 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-01 13:52 [Bug tree-optimization/62631] New: " ro at gcc dot gnu.org
2014-09-01 13:53 ` [Bug tree-optimization/62631] " ro at gcc dot gnu.org
2014-09-01 14:06 ` ro at gcc dot gnu.org
2014-09-01 14:26 ` ro at gcc dot gnu.org
2014-09-01 14:27 ` ro at gcc dot gnu.org
2014-09-02 6:00 ` amker.cheng at gmail dot com
2014-09-07 19:37 ` danglin at gcc dot gnu.org
2014-09-11 5:48 ` amker at gcc dot gnu.org
2014-09-11 8:43 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-09-12 10:58 ` ro at CeBiTec dot Uni-Bielefeld.DE
2015-02-02 23:22 ` [Bug target/62631] " ebotcazou at gcc dot gnu.org
2015-02-03 9:57 ` ebotcazou at gcc dot gnu.org
2015-02-03 10:54 ` amker at gcc dot gnu.org
2015-02-04 4:06 ` amker at gcc dot gnu.org
2015-02-04 11:45 ` ebotcazou at gcc dot gnu.org
2015-02-04 14:43 ` ebotcazou at gcc dot gnu.org
2015-02-06 6:20 ` amker at gcc dot gnu.org
2015-02-06 7:10 ` ebotcazou at gcc dot gnu.org
2015-02-06 11:18 ` ebotcazou at gcc dot gnu.org
2015-02-06 11:26 ` ebotcazou at gcc dot gnu.org
2015-02-06 11:33 ` ebotcazou at gcc dot gnu.org
2015-02-06 15:52 ` dave.anglin at bell dot net
2015-02-07 19:08 ` dave.anglin at bell dot net
2015-02-07 22:24 ` ebotcazou at gcc dot gnu.org
2015-02-07 23:14 ` dave.anglin at bell dot net [this message]
2015-02-08 14:07 ` amker at gcc dot gnu.org
2015-02-08 14:09 ` amker at gcc dot gnu.org
2015-02-08 14:59 ` dave.anglin at bell dot net
2015-02-08 21:44 ` ebotcazou at gcc dot gnu.org
2015-02-09 3:24 ` amker at gcc dot gnu.org
2015-02-09 8:11 ` amker at gcc dot gnu.org
2015-04-22 12:01 ` jakub at gcc dot gnu.org
2015-07-16 9:13 ` rguenth at gcc dot gnu.org
2022-01-09 0:42 ` pinskia at gcc dot gnu.org
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=bug-62631-4-6XfPYsb2yo@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).