This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/51251] New: SPARC _64 instructions in V7 executables
- From: "joel at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 21 Nov 2011 00:51:19 +0000
- Subject: [Bug target/51251] New: SPARC _64 instructions in V7 executables
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51251
Bug #: 51251
Summary: SPARC _64 instructions in V7 executables
Classification: Unclassified
Product: gcc
Version: 4.7.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: joel@gcc.gnu.org
Sun Nov 20 19:34:53 UTC 2011 (revision 181531)
But this has probably existed a long time.
Target: sparc-rtems4.11
I am testing gfortran on rtems and it appears that about 1/2 of the failures on
sparc are related to this.
Some branches have ",pn" and ",pl" attached and it is not supported.
0x020012a4 <+36>: ble,pn %icc, 0x20013ec <foo_+364>
...
0x020012f8 <+120>: be,pn %icc, 0x20013fc <foo_+380>
I checked sparc.c and there are some cases where the ",pX" are only generated
for sparc64 and others where they are not.
I don't expect this is hard to fix for a sparc maintainer. :)