[Bug target/52034] __builtin_copysign optimization suboptimal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52034 Andrew Pinski changed: What|Removed |Added Target Milestone|--- |11.0 Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #6 from Andrew Pinski --- This was a scrach_register issue which was fixed in r11-4577.
[Bug target/52034] __builtin_copysign optimization suboptimal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52034 --- Comment #5 from Andrew Pinski --- Th
[Bug target/52034] __builtin_copysign optimization suboptimal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52034 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill ||a/show_bug.cgi?id=89984 Severity|normal |enhancement --- Comment #4 from Andrew Pinski --- related to PR 89984.
[Bug target/52034] __builtin_copysign optimization suboptimal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52034 Marc Glisse changed: What|Removed |Added Last reconfirmed|2012-01-29 00:00:00 |2018-8-30 Known to fail||8.2.0 --- Comment #3 from Marc Glisse --- I don't understand why we keep UNSPEC_COPYSIGN so long, it is only expanded in split2, after register allocation. Maybe splitting earlier into and+and+or would help RA...
[Bug target/52034] __builtin_copysign optimization suboptimal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52034 --- Comment #2 from Richard Guenther rguenth at gcc dot gnu.org 2012-01-30 09:35:37 UTC --- It's an RA issue I think - the RA isn't very clever when it comes to coalescing pseudos with incoming or outgoing fixed regs.
[Bug target/52034] __builtin_copysign optimization suboptimal
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52034 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Target||x86_64-*-* i?86-*-* Status|UNCONFIRMED |NEW Keywords||missed-optimization, ra Last reconfirmed||2012-01-29 Component|tree-optimization |target Ever Confirmed|0 |1 --- Comment #1 from Andrew Pinski pinskia at gcc dot gnu.org 2012-01-29 01:27:53 UTC --- Confirmed. This is either the way copysign rtl is done on x86_64 or is a register allocator issue with the copysign rtl.