target/592: [ARM/Thumb] Poor choice of PIC register
rearnsha@gcc.gnu.org
rearnsha@gcc.gnu.org
Tue Apr 23 08:57:00 GMT 2002
Synopsis: [ARM/Thumb] Poor choice of PIC register
Responsible-Changed-From-To: pb->rearnsha
Responsible-Changed-By: rearnsha
Responsible-Changed-When: Tue Apr 23 08:44:20 2002
Responsible-Changed-Why:
.
State-Changed-From-To: analyzed->suspended
State-Changed-By: rearnsha
State-Changed-When: Tue Apr 23 08:44:20 2002
State-Changed-Why:
Having given this some consideration, I'm no-longer convinced that
fixing a lo reigster is a good idea: it would unduly pessimize
other code and might lead to situations where we would run
out of registers.
The best solution would be to make the PIC register a pseudo,
but apparently there are other issues that prevent this.
I believe the orignal problem that provoked this report has now
been resolved.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=592
More information about the Gcc-bugs
mailing list