[Bug c/114597] [GCC-14] Miscompilation of pointer assignment with inline assembly

2024-09-30 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114597 Andrew Pinski changed: What|Removed |Added Resolution|INVALID |DUPLICATE --- Comment #6 from Andrew Pi

[Bug c/114597] [GCC-14] Miscompilation of pointer assignment with inline assembly

2024-04-05 Thread 141242068 at smail dot nju.edu.cn via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114597 --- Comment #5 from wierton <141242068 at smail dot nju.edu.cn> --- (In reply to Xi Ruoyao from comment #4) > I believe the second form is still incorrect and it just works by luck. To > ensure it work you have to do: > > asm("mov %1,%0":"=r"(n

[Bug c/114597] [GCC-14] Miscompilation of pointer assignment with inline assembly

2024-04-04 Thread xry111 at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114597 Xi Ruoyao changed: What|Removed |Added CC||xry111 at gcc dot gnu.org --- Comment #4 fr

[Bug c/114597] [GCC-14] Miscompilation of pointer assignment with inline assembly

2024-04-04 Thread 141242068 at smail dot nju.edu.cn via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114597 --- Comment #3 from wierton <141242068 at smail dot nju.edu.cn> --- Thanks a lot, I have checked it out. I'm still somewhat confused. Does the difference in compilation stem from GCC interpreting "=m" and "=r" differently, leading it to assume t

[Bug c/114597] [GCC-14] Miscompilation of pointer assignment with inline assembly

2024-04-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114597 Andrew Pinski changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c/114597] [GCC-14] Miscompilation of pointer assignment with inline assembly

2024-04-04 Thread pinskia at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114597 Andrew Pinski changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED