[Bug target/31152] -(xy) generates wrong code

2007-06-23 Thread rearnsha at gcc dot gnu dot org
--- Comment #6 from rearnsha at gcc dot gnu dot org 2007-06-23 18:11 --- Fixed on trunk. -- rearnsha at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/31152] -(xy) generates wrong code

2007-06-23 Thread rearnsha at gcc dot gnu dot org
--- Comment #5 from rearnsha at gcc dot gnu dot org 2007-06-23 18:07 --- Subject: Bug 31152 Author: rearnsha Date: Sat Jun 23 18:07:04 2007 New Revision: 125973 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=125973 Log: PR target/31152 * arm.md (negscc): Match

[Bug target/31152] -(xy) generates wrong code

2007-06-23 Thread tbm at cyrius dot com
--- Comment #7 from tbm at cyrius dot com 2007-06-23 19:07 --- Are you not going to apply this to 4.1 and 4.2? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31152

[Bug target/31152] -(xy) generates wrong code

2007-06-23 Thread tbm at cyrius dot com
--- Comment #8 from tbm at cyrius dot com 2007-06-23 19:07 --- Richard, I think this patch should also be added to the 4.1 and 4.2 branches. -- tbm at cyrius dot com changed: What|Removed |Added

[Bug target/31152] -(xy) generates wrong code

2007-06-19 Thread rearnsha at gcc dot gnu dot org
--- Comment #4 from rearnsha at gcc dot gnu dot org 2007-06-19 09:41 --- Confirmed. This is a bug in the negscc pattern in arm.md. It's only been there since 1994! -- rearnsha at gcc dot gnu dot org changed: What|Removed |Added

[Bug target/31152] -(xy) generates wrong code

2007-03-23 Thread fb at frank-buss dot de
--- Comment #3 from fb at frank-buss dot de 2007-03-23 21:27 --- I can reproduce the problem on a Linkstation Pro with an ARM926EJ CPU. I compiled GCC SVN revision 123155 from the gcc-4_2-branch on it. Creating wrong assembler code is at least a major bug, even when using the optimizing

[Bug target/31152] -(xy) generates wrong code

2007-03-13 Thread rguenth at gcc dot gnu dot org
--- Comment #2 from rguenth at gcc dot gnu dot org 2007-03-13 10:20 --- It works for me on x86_64 and i686 with 4.0.0, 4.1.0 and 4.1.2. So this looks like a target issue. -- rguenth at gcc dot gnu dot org changed: What|Removed |Added