This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: PR 6394


>>>>> John David Anglin writes:

John> This would be definitely helpful.  I have investigated this enough
John> to know that the floating pointer register is being allocated in
John> global_alloc.  What I don't understand is why this happens as it
John> would seem that a general register should have been selected.
John> The ICE occurs selecting one of two addresses for the return value
John> and there shouldn't be many conflicts at this point.

	Alan Modra and the IBM ppc64 Linux team found similar bad register
allocation for 64-bit PowerPC.  As an interim solution, we added splitters
that handle FP registers for those patterns to rs6000.md.  I would suggest
implementing something similar for PA-RISC GCC 3.1 or GCC 3.1.1.

	For GCC 3.2, we should focus on the new register allocator instead
of trying to fix an inherently limited and broken implementation.

David


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]