https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101718
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2021-08-16
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Matt Jacobson from comment #2)
> (In reply to Iain Sandoe from comment #1)
> > can you give me some idea of the platform? it would help with testing at
> > least (assuming that there is a suitable machine on the cfarm).
>
> Sure, but I'm guessing it's not going to be very helpful! The platform I'm
> using is an AVR microcontroller, with my own custom NeXT-v2-ABI-compliant
> runtime.
>
> <https://mjacobson.net/blog/2021-07-objc-avr.html>
> <https://github.com/mhjacobson/avr-objc>
As you say, maybe not immediately helpful - but coul even so.
> > Having said that, there could be some types for which this would fire even
> > on Darwin.
>
> Hm -- I'm not so sure.
It is possible to find an example - if AVX is disabled, GCC returns __m256 in
memory (so can be tried for manual testing). However, the clang version of
this on Darwin platforms actually returns in xmm0/xmm1 (which has an ABI bug
filed against it on LLVM IIRC) - so not useful outside manual testing.
My guess is that there are no [other] non-struct cases for the powerpc(64b) and
x86 cases, I've not poked at the aarch64 case yet, so the bug went unnoticed
all this time.
initial patch under test now.
