This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: testsuite result updates for x86_64-w64-mingw32
- From: Eric Botcazou <ebotcazou at adacore dot com>
- To: Tamar Christina <Tamar dot Christina at arm dot com>
- Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>, Óscar Fuentes <ofv at wanadoo dot es>, nd <nd at arm dot com>
- Date: Tue, 22 Jan 2019 23:03:20 +0100
- Subject: Re: testsuite result updates for x86_64-w64-mingw32
- References: <8cfa796c-f85c-3f22-b0ea-10d90051149e@emrich-ebersheim.de> <1798926.xjLkxICdue@polaris> <DB6PR0802MB23090A7A8C3F84CDF68C4FC8FF980@DB6PR0802MB2309.eurprd08.prod.outlook.com>
> 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_size_table[__builtin_dwarf_sp_column ()];
if (size == sizeof(_Unwind_Ptr))
tmp_sp->ptr = (_Unwind_Ptr) cfa;
else
{
gcc_assert (size == sizeof(_Unwind_Word));
tmp_sp->word = (_Unwind_Ptr) cfa;
}
which is quite unexpected.
--
Eric Botcazou