> So looking at it again, this seems to be happening during stage3.
Yes, I should have realized it a while ago, you don't compile g-exptty.adb for
the compiler but only for the runtime... The backtrace seems to show that the
abort at libgcc/unwind-dw2.c:1386 is raised:
int size = dwarf_reg_s
entes; nd
Subject: Re: testsuite result updates for x86_64-w64-mingw32
> It's built with --disable-sjlj-exceptions --with-dwarf2
>
> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-gcc/PKGBUILD
> #L150
Then, if both the base compiler and the compiler to be built a
>
> Then, if both the base compiler and the compiler to be built are configured
> that way, there is no reason why this cannot work.
>
> What's a little strange is that there is a .cold part in the backtrace:
>
> #14 0x015fd511 in uw_init_context_1.cold () at ../../../gcc-8-
> 20181214/libgcc/
> It's built with --disable-sjlj-exceptions --with-dwarf2
>
> https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-gcc/PKGBUILD
> #L150
Then, if both the base compiler and the compiler to be built are configured
that way, there is no reason why this cannot work.
What's a little stran
> > Ah, that makes sense since the 32-bit SEH is different from the 64-bit
> > one, explains why the 64-bit builds work.
>
> Which EH mechanism does the base compiler use? The default one? We
> know that this works with the DWARF-2 mechanism (--disable-sjlj-
> exceptions).
It's built with --dis
> Ah, that makes sense since the 32-bit SEH is different from the 64-bit one,
> explains why the 64-bit builds work.
Which EH mechanism does the base compiler use? The default one? We know that
this works with the DWARF-2 mechanism (--disable-sjlj-exceptions).
--
Eric Botcazou
> -Original Message-
> From: Eric Botcazou
> Sent: Tuesday, January 22, 2019 11:19
> To: Tamar Christina
> Cc: Óscar Fuentes ; gcc@gcc.gnu.org
> Subject: Re: testsuite result updates for x86_64-w64-mingw32
>
> > The gnat1 command that fails is
> >
>
> The gnat1 command that fails is
>
> mingw-w64-gcc/src/build-i686-w64-mingw32/gcc/gnat1.exe -gnatwa -quiet
> -nostdinc -dumpbase g-exptty.adb -auxbase-strip g-exptty.o -O2 -Wextra
> -Wall -g -gnatpg -mtune=generic -march=i686 -gnatO g-exptty.o g-exptty.adb
> -o E:\msys32-devel\tmp\ccAujHCD.s
>
>
Forwarding to list as well.
> -Original Message-
> From: Tamar Christina
> Sent: Tuesday, January 22, 2019 11:02
> To: 'Óscar Fuentes' ; Eric Botcazou
>
> Cc: gcc@gcc.gnu.org
> Subject: RE: testsuite result updates for x86_64-w64-mingw32
>
> Hi Eric,
Eric Botcazou writes:
>> About the Ada compiler: it doesn't build on i686-w64-mingw32. It is
>> the reason why MSYS2 is stuck with 7.3 for 32 bits.
>
> Why doesn't it build? Because of PR ada/81878?
More specifically:
xgcc.exe: internal compiler error: Aborted signal terminated program gnat1
Eric Botcazou writes:
>> About the Ada compiler: it doesn't build on i686-w64-mingw32. It is
>> the reason why MSYS2 is stuck with 7.3 for 32 bits.
>
> Why doesn't it build? Because of PR ada/81878?
xgcc crashes.
https://github.com/Alexpux/MINGW-packages/issues/4125#issuecomment-425741895
Thi
> -Original Message-
> From: gcc-ow...@gcc.gnu.org On Behalf Of Eric
> Botcazou
> Sent: Thursday, October 18, 2018 16:40
> To: Óscar Fuentes
> Cc: gcc@gcc.gnu.org
> Subject: Re: testsuite result updates for x86_64-w64-mingw32
>
> > About the Ada compiler
> About the Ada compiler: it doesn't build on i686-w64-mingw32. It is
> the reason why MSYS2 is stuck with 7.3 for 32 bits.
Why doesn't it build? Because of PR ada/81878?
--
Eric Botcazou
Eric Botcazou writes:
>> There are new testsuite results for x86_64-w64-mingw32, for versions
>> 6.4.1, 7.3.1, 8.2.1 and 9.0.0.
>>
>> https://gcc.gnu.org/ml/gcc-testresults/2018-10/msg02309.html
>> https://gcc.gnu.org/ml/gcc-testresults/2018-10/msg02310.html
>> https://gcc.gnu.org/ml/gcc-testres
> There are new testsuite results for x86_64-w64-mingw32, for versions
> 6.4.1, 7.3.1, 8.2.1 and 9.0.0.
>
> https://gcc.gnu.org/ml/gcc-testresults/2018-10/msg02309.html
> https://gcc.gnu.org/ml/gcc-testresults/2018-10/msg02310.html
> https://gcc.gnu.org/ml/gcc-testresults/2018-10/msg02312.html
So
15 matches
Mail list logo
