https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114288
--- Comment #12 from Jeffrey A. Law <law at gcc dot gnu.org> --- Aren't we compiling for PA2.0? If so, shouldn't we have a full 14 bit offset support, even when a load/store hits the FP register file (feel free to correct me if I'm wrong, it's only been 20 years since I worked on this stuff ;-) So I don't really see why the offsets are an issue here. If we were compiling for PA1.0/PA1.1, then yes, there's a real issue, but it's with allowing the larger offsets as a legitimate address. That's lying to the compiler, reload in particular and as I said, it's ultimately going to backfire -- even with the workaround since you're going to have DImode loads/stores to the FP register file due to xmpyu or potentially even memcpy and friends. I already tried what you're doing years ago. It's doomed to failure. You might think this is a reload problem. But I'm far from convinced. It smells much more like a PA backend issue to me.
