[Bug target/62262] aarch64 gcc generates invalid assembler

2014-09-05 Thread mshawcroft at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 mshawcroft at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-27 Thread carrot at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #11 from carrot at gcc dot gnu.org --- Author: carrot Date: Wed Aug 27 23:00:54 2014 New Revision: 214610 URL: https://gcc.gnu.org/viewcvs?rev=214610&root=gcc&view=rev Log: PR target/62262 * config/aarch64/aarch64.md (*andim_a

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-27 Thread carrot at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #9 from amker at gcc dot gnu.org --- (In reply to Andrew Pinski from comment #6) > (In reply to Carrot from comment #5) > > Actually the original source code is guarded by assert, and the parameter > > passed to CLZ can be guaranteed n

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-26 Thread amker at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #8 from amker at gcc dot gnu.org --- (In reply to Carrot from comment #5) > (In reply to amker from comment #2) > > (In reply to Andrew Pinski from comment #1) > > > (insn 27 26 40 5 (set (reg:SI 73 [ D.2590 ]) > > > (and:SI (a

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-26 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #7 from Andrew Pinski --- Also the reason why it shows up in the first place is because the gimple level tracer produces: : # iftmp.0_13 = PHI <32(3)> value_5 = value_3 << iftmp.0_13; packed_6 = value_5 & 8388607; And never p

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-26 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #6 from Andrew Pinski --- (In reply to Carrot from comment #5) > Actually the original source code is guarded by assert, and the parameter > passed to CLZ can be guaranteed not 0, so "value <<= zeros" is well defined > in our original

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-26 Thread carrot at google dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #5 from Carrot --- (In reply to amker from comment #2) > (In reply to Andrew Pinski from comment #1) > > (insn 27 26 40 5 (set (reg:SI 73 [ D.2590 ]) > > (and:SI (ashift:SI (reg/v:SI 74 [ value ]) > > (const_in

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-25 Thread amker at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #4 from amker at gcc dot gnu.org --- (In reply to Andrew Pinski from comment #3) > (In reply to amker from comment #2) > > (In reply to Andrew Pinski from comment #1) > > > (insn 27 26 40 5 (set (reg:SI 73 [ D.2590 ]) > > > (an

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-25 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 --- Comment #3 from Andrew Pinski --- (In reply to amker from comment #2) > (In reply to Andrew Pinski from comment #1) > > (insn 27 26 40 5 (set (reg:SI 73 [ D.2590 ]) > > (and:SI (ashift:SI (reg/v:SI 74 [ value ]) > > (c

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-25 Thread amker at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 amker at gcc dot gnu.org changed: What|Removed |Added CC||amker at gcc dot gnu.org --- C

[Bug target/62262] aarch64 gcc generates invalid assembler

2014-08-25 Thread pinskia at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62262 Andrew Pinski changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|