https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Jeffrey A. Law changed:
What|Removed |Added
Status|REOPENED|RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #16 from Kirill Yukhin ---
Author: kyukhin
Date: Mon Oct 13 17:26:49 2014
New Revision: 216154
URL: https://gcc.gnu.org/viewcvs?rev=216154&root=gcc&view=rev
Log:
gcc/
PR target/8340
PR middle-end/47602
PR rtl-optimizatio
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Jan Seiffert changed:
What|Removed |Added
CC||kaffeemonster at googlemail
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Paulo César Pereira de Andrade changed:
What|Removed |Added
CC||pcpa at mandriva dot com.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #13 from Eric Botcazou 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 instruction,
> or makes a kernel syst
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #12 from H.J. Lu 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 cpuid instruction, or
U
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #11 from Andreas Schwab 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 #10 from Ian Lance Taylor 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* aware of the PIC regi
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
Eric Botcazou changed:
What|Removed |Added
CC||ebotcazou at gcc dot
|
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #8 from Ian Lance Taylor 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.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #7 from H.J. Lu 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 asm, it should be saved
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #6 from Ian Lance Taylor 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 any way other than
f
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #5 from Andrew Pinski 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. Really I think it is a good th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602
--- Comment #4 from Andrew Pinski 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
Andrew Pinski changed:
What|Removed |Added
Component|rtl-optimization|middle-end
Severity|normal
15 matches
Mail list logo
