https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70593
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70593
--- Comment #5 from Jakub Jelinek ---
Author: jakub
Date: Fri Apr 8 17:28:20 2016
New Revision: 234834
URL: https://gcc.gnu.org/viewcvs?rev=234834&root=gcc&view=rev
Log:
PR middle-end/70593
* tree-ssa-coalesce.c (build_ssa_confl
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70593
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70593
--- Comment #3 from Jakub Jelinek ---
And there is another thing special on this testcase - a_6 has zero uses, so
isn't live.
If both the values would be live after the asm, there would be an conflict
added, even during the SSA_OP_DEF processing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70593
Jakub Jelinek changed:
What|Removed |Added
CC||aoliva at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70593
--- Comment #1 from Jakub Jelinek ---
Simplified testcase:
__attribute__((noinline, noclone)) unsigned long
foo (unsigned x)
{
unsigned long a, c = x;
asm volatile ("xorl\t%k1, %k1\n\tmovl\t$7, %k0"
: "=c" (c), "=a" (a) : "0"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70593
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
Status|UNCONFIRMED
