https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Jeffrey A. Law law at redhat dot com changed:
What|Removed |Added
Status|REOPENED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #16 from Kirill Yukhin kyukhin at gcc dot gnu.org ---
Author: kyukhin
Date: Mon Oct 13 17:26:49 2014
New Revision: 216154
URL: https://gcc.gnu.org/viewcvs?rev=216154root=gccview=rev
Log:
gcc/
PR target/8340
PR
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Jan Seiffert kaffeemonster at googlemail dot com changed:
What|Removed |Added
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Paulo César Pereira de Andrade pcpa at mandriva dot com.br changed:
What|Removed |Added
CC|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Eric Botcazou ebotcazou at gcc dot gnu.org changed:
What|Removed |Added
CC||ebotcazou at
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #10 from Ian Lance Taylor ian at airs dot com 2011-02-04 14:16:32
UTC ---
What advantage do we bring to our users by requiring them to be aware of the
details of the PIC register when writing inline asm code? Again, those who
*are*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #11 from Andreas Schwab sch...@linux-m68k.org 2011-02-04 14:28:00
UTC ---
If you are writing assembler code you need to know your ABI in and out.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #12 from H.J. Lu hjl.tools at gmail dot com 2011-02-04 15:01:56
UTC ---
(In reply to comment #10)
what way are we helping them by forcing them to know about it? How does that
help them write inline assembler which, e.g., uses the
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #13 from Eric Botcazou ebotcazou at gcc dot gnu.org 2011-02-04
15:23:22 UTC ---
In what way are we helping them by forcing them to know about it? How does
that help them write inline assembler which, e.g., uses the cpuid
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Andrew Pinski pinskia at gcc dot gnu.org changed:
What|Removed |Added
Component|rtl-optimization|middle-end
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #4 from Andrew Pinski pinskia at gcc dot gnu.org 2011-02-04
00:04:36 UTC ---
http://gcc.gnu.org/ml/gcc-patches/2002-11/msg01372.html
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #5 from Andrew Pinski pinskia at gcc dot gnu.org 2011-02-04
00:06:36 UTC ---
What happens on targets like PPC where r2 (the PIC register) is a fixed
register should we save and restore it or error out. I say we should error
out.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #6 from Ian Lance Taylor ian at airs dot com 2011-02-04 00:08:42
UTC ---
The old bug was about bad code generation, and that was fixed. I don't think
it needs to be reopened.
I can not find any discussion about fixing this issue in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #7 from H.J. Lu hjl.tools at gmail dot com 2011-02-04 01:42:03
UTC ---
(In reply to comment #6)
I can not find any discussion about fixing this issue in any way other than
forbidding it.
EBX is fixed in PIC. If it is changed in
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #8 from Ian Lance Taylor ian at airs dot com 2011-02-04 05:31:08
UTC ---
I'm suggesting saving and restoring it around the asm statement itself, not in
the prologue and epilogue.
15 matches
Mail list logo