: c
Assignee: unassigned at gcc dot gnu.org
Reporter: mini at cs dot technion.ac.il
Target Milestone: ---
Hi,
I am compiling this code:
int cmov(int pred, int t_val, int f_val) {
int result;
__asm__ volatile (
"mov %2, %
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79425
--- Comment #3 from Marina Minkin ---
What do you mean by "You need to set the section to verify correct in top level
inline-asm and then"?
This is a stripped code just to reproduce this behavior.
What I initially tried to do, was to make a func
++
Assignee: unassigned at gcc dot gnu.org
Reporter: mini at cs dot technion.ac.il
Target Milestone: ---
I am getting inline assembly code clobbered if I #include, it is the
1st code in the .text segment, AND I use -std=c++11
This is the INCORRECT behavior. As you can see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79416
--- Comment #2 from Marina Minkin ---
I was able to get a different error on gcc 4.4.7
$ gcc -v
Using built-in specs.
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --wit
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mini at cs dot technion.ac.il
Target Milestone: ---
Target: x86_64-linux-gnu
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
I ran it about 10 times. 9 times I got this output:
$ g
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mini at cs dot technion.ac.il
Target Milestone: ---
I am getting internal error with the -fcall-saved-rax flag
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
to reproduce
