[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#972789: qemu: FTBFS on arm{el,hf}: /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not compatible



Control: reassign -1 gcc-10 10.2.0-15
Control: tags -1 upstream
Control: forwarded -1 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97323
Control: affects -1 src:qemu

On 2020-10-24 07:38:39 +0300, Michael Tokarev wrote:
> 23.10.2020 19:50, Sebastian Ramacher wrote:
> > Source: qemu
> > Version: 1:5.1+dfsg-4
> > Severity: serious
> > Tags: ftbfs sid bullseye
> > Justification: fails to build from source (but built successfully in the past)
> 
> > binNMUs of qemu for the libbrlapi transition failed to build on armel
> > and armhf:
> 
> > | /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: error: ‘TYPE_CANONICAL’ is not compatible
> > |    44 | };
> > |       | ^
> 
> Hmm. So this looks like a gcc ICE bug. Here's the code in question:
> 
> struct target_sigframe
> {
>     abi_ulong pretcode;
>     int sig;
>     int code;
>     abi_ulong psc;
>     char retcode[8];
>     abi_ulong extramask[TARGET_NSIG_WORDS-1];
>     struct target_sigcontext sc;
> };
> 
> ...
> > | /<<PKGBUILDDIR>>/linux-user/m68k/signal.c:44:1: internal compiler error: ‘verify_type’ failed
> 
> I'm not sure what I have to do with this, besides reassigning it to gcc.
> 
> BTW, symbol TYPE_CANONICAL is not used/referenced by qemu sources.

Indeed, that's a bug in gcc which was already reported upstream.
Reassigning accordingly.

Cheers
-- 
Sebastian Ramacher

Attachment: signature.asc
Description: PGP signature


Reply to: