[Bug target/86387] [RISCV][ABI] GCC fails to sign/zero-ext integers as necessary for passing/returning int+fp structs on hard-float ABIs

[wilson at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86387

Jim Wilson  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|ASSIGNED|RESOLVED

--- Comment #3 from Jim Wilson  ---
This was fixed with a psABI change in Nov 2018 and we forgot to update this bug
report.
https://github.com/riscv/riscv-elf-psabi-doc/pull/74

[Bug target/86387] [RISCV][ABI] GCC fails to sign/zero-ext integers as necessary for passing/returning int+fp structs on hard-float ABIs

[rguenth at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86387

Richard Biener  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED

[Bug target/86387] [RISCV][ABI] GCC fails to sign/zero-ext integers as necessary for passing/returning int+fp structs on hard-float ABIs

[wilson at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86387

Jim Wilson  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEW
   Last reconfirmed||2018-07-03
   Assignee|unassigned at gcc dot gnu.org  |wilson at gcc dot 
gnu.org
 Ever confirmed|0   |1

--- Comment #2 from Jim Wilson  ---
I don't see any gcc regression.  I think the psABI spec was updated without
checking gcc.  Unfortunately, fixing gcc would cause a non-backward compatible
ABI change.  Given that we fixed the ABI back in January when we upstreamed
glibc, we can't change it now without causing a lot of trouble.  Hence, the
easy solution is to fix the paABI spec to match what gcc actually emits.