https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57333
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57333
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|1 |0
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57333
Andrew Pinski changed:
What|Removed |Added
Target||x86_64-linux-gnu
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57333
Richard Biener rguenth at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|4.7.4 |---
---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57333
Uroš Bizjak ubizjak at gmail dot com changed:
What|Removed |Added
CC||tmsriram at google
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57333
--- Comment #3 from bernhard.hartleb at gmail dot com ---
(In reply to Uroš Bizjak from comment #2)
LZCNT insn is part of ABM abi, and is enabled with -mabm. Does LZCNT insn
really cause SIGILL on your target?
No sorry, this was an error on my
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57333
--- Comment #1 from bernhard.hartleb at gmail dot com ---
It seems the illegal instructions is caused by the use of LTO.
Without LTO everything is fine.
The second point is still valid, however.
