https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
John David Anglin changed:
What|Removed |Added
CC||danglin at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
--- Comment #7 from John Paul Adrian Glaubitz ---
Created attachment 49380
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49380=edit
Archive containing C source, preprocessed source as well as assembly and object
output
I have created the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
--- Comment #6 from Oleg Endo ---
(In reply to John Paul Adrian Glaubitz from comment #5)
So the difference seems to be only the -fPIC option? Can you get the
preprocessed .i file with -save-temps ?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
--- Comment #5 from John Paul Adrian Glaubitz ---
(In reply to Oleg Endo from comment #4)
> Just to point out the obvious, r13 is never initialized nor referenced by
> anything else throughout the function. What are the compiler options?
One
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
Oleg Endo changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
--- Comment #3 from John Paul Adrian Glaubitz ---
(In reply to Rich Felker from comment #1)
> Do you have a complete disassembly of the function it crashed in and
> register dump at the point of crash? That would help.
Register dump:
(gdb)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
--- Comment #2 from Yoshinori Sato ---
Since 0x296318e8 is data, we need to investigate where we jumped.
The backtrace looks normal, so I think you're getting anomalous jumps when
optimizing long_richcompare.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97431
--- Comment #1 from Rich Felker ---
Do you have a complete disassembly of the function it crashed in and register
dump at the point of crash? That would help.
