From: Paolo Bonzini <bonzini@gnu.org>
To: Andrew_Pinski@PlayStation.Sony.Com
Cc: Kenneth Zadeck <zadeck@naturalbridge.com>,
Serge Belyshev <belyshev@depni.sinp.msu.ru>,
"Berlin, Daniel" <dberlin@dberlin.org>,
"Edelsohn, David" <dje@watson.ibm.com>,
echristo@apple.com, gcc-patches <gcc-patches@gcc.gnu.org>,
Ian Lance Taylor <iant@google.com>,
richard.earnshaw@arm.com, "Park,
Seongbae" <seongbae.park@gmail.com>,
Steven Bosscher <stevenb.gcc@gmail.com>,
"Weigand, Ulrich" <Ulrich.Weigand@de.ibm.com>
Subject: Re: dataflow branch merging plans.
Date: Thu, 24 May 2007 07:51:00 -0000 [thread overview]
Message-ID: <4655440F.9010502@gnu.org> (raw)
In-Reply-To: <OF781E582C.3916D180-ON882572E5.00078CD6-882572E5.00082C95@playstation.sony.com>
> The instruction at the time we are verifying:
> (insn 147 146 148 7 (set (reg:SI 240)
> (mult:SI (zero_extend:SI (subreg:HI (reg:SI 234) 2))
> (zero_extend:SI (subreg:HI (reg:SI 238) 2)))) -1
> (expr_list:REG_EQUAL (mult:SI (zero_extend:SI (subreg:HI (reg:SI 234) 2))
> (const_int 43690 [0xaaaa]))
> (nil)))
This is an RTL sharing problem between insn 146 and insn 147, caused by
the umulsi3_highpart pattern of spu.md (but the same applies to
smulsi3_highpart), expanded by loop unrolling.
I think you have to use a define_insn_and_split the same way you do with
mulsi3 vs. _mulsi3.
Paolo
WARNING: multiple messages have this Message-ID
From: Paolo Bonzini <bonzini@gnu.org>
To: gcc-patches@gcc.gnu.org
Cc: Kenneth Zadeck <zadeck@naturalbridge.com>,
Serge Belyshev <belyshev@depni.sinp.msu.ru>,
"Berlin, Daniel" <dberlin@dberlin.org>,
"Edelsohn, David" <dje@watson.ibm.com>,
echristo@apple.com, gcc-patches <gcc-patches@gcc.gnu.org>,
Ian Lance Taylor <iant@google.com>,
richard.earnshaw@arm.com, "Park,
Seongbae" <seongbae.park@gmail.com>,
Steven Bosscher <stevenb.gcc@gmail.com>,
"Weigand, Ulrich" <Ulrich.Weigand@de.ibm.com>
Subject: Re: dataflow branch merging plans.
Date: Thu, 24 May 2007 08:12:00 -0000 [thread overview]
Message-ID: <4655440F.9010502@gnu.org> (raw)
Message-ID: <20070524081200.eOIrOIzDRbby4J6j4U-yM5kY9OQ-Mv367x8uT4r4hdE@z> (raw)
In-Reply-To: <OF781E582C.3916D180-ON882572E5.00078CD6-882572E5.00082C95@playstation.sony.com>
> The instruction at the time we are verifying:
> (insn 147 146 148 7 (set (reg:SI 240)
> (mult:SI (zero_extend:SI (subreg:HI (reg:SI 234) 2))
> (zero_extend:SI (subreg:HI (reg:SI 238) 2)))) -1
> (expr_list:REG_EQUAL (mult:SI (zero_extend:SI (subreg:HI (reg:SI 234) 2))
> (const_int 43690 [0xaaaa]))
> (nil)))
This is an RTL sharing problem between insn 146 and insn 147, caused by
the umulsi3_highpart pattern of spu.md (but the same applies to
smulsi3_highpart), expanded by loop unrolling.
I think you have to use a define_insn_and_split the same way you do with
mulsi3 vs. _mulsi3.
Paolo
next prev parent reply other threads:[~2007-05-24 7:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 13:19 Kenneth Zadeck
2007-05-24 1:29 ` Andrew_Pinski
2007-05-24 7:51 ` Paolo Bonzini [this message]
2007-05-24 8:12 ` Paolo Bonzini
2007-05-24 11:47 ` Bernd Schmidt
2007-05-24 20:02 ` Kenneth Zadeck
2007-05-25 9:51 ` Bernd Schmidt
2007-05-25 10:32 ` Paolo Bonzini
2007-05-25 13:00 ` Kenneth Zadeck
2007-05-28 20:55 ` Mark Mitchell
2007-05-29 1:16 ` Kenneth Zadeck
2007-05-29 15:58 ` Mark Mitchell
2007-05-24 21:09 ` Steven Bosscher
2007-05-24 22:23 ` Vladimir N. Makarov
2007-05-24 23:03 ` Steven Bosscher
2007-05-25 13:50 ` Vladimir N. Makarov
2007-05-25 17:15 ` Richard Sandiford
2007-05-25 18:21 ` Jan Hubicka
2007-05-25 20:13 ` Steven Bosscher
2007-05-25 20:11 ` Steven Bosscher
[not found] <OF781E582C.3916D180-ON882572E5.00078CD6-882572E5.00082C95@LocalDomain>
2007-05-25 0:12 ` Andrew_Pinski
2007-05-25 19:04 Zack Weinberg
[not found] <OF1BD0F1DA.E933CF3F-ON422572E9.006B2EF9-422572E9.006B85BF@de.ibm.com>
2007-05-29 1:05 ` Kenneth Zadeck
2007-05-30 13:11 ` Andreas Krebbel1
2007-05-30 14:17 ` Kenneth Zadeck
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=4655440F.9010502@gnu.org \
--to=bonzini@gnu.org \
--cc=Andrew_Pinski@PlayStation.Sony.Com \
--cc=Ulrich.Weigand@de.ibm.com \
--cc=belyshev@depni.sinp.msu.ru \
--cc=dberlin@dberlin.org \
--cc=dje@watson.ibm.com \
--cc=echristo@apple.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--cc=richard.earnshaw@arm.com \
--cc=seongbae.park@gmail.com \
--cc=stevenb.gcc@gmail.com \
--cc=zadeck@naturalbridge.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).