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: Tamar Christina <Tamar dot Christina at arm dot com>
- To: Eric Botcazou <ebotcazou at adacore 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 12:33:40 +0000
- Subject: RE: testsuite result updates for x86_64-w64-mingw32
- References: <8cfa796c-f85c-3f22-b0ea-10d90051149e@emrich-ebersheim.de> <3883008.hKdS3qPX7z@polaris> <DB6PR0802MB2309E9E8221E1761EAC11AEAFF980@DB6PR0802MB2309.eurprd08.prod.outlook.com> <1798926.xjLkxICdue@polaris>
>
> 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/unwind-dw2.c:1386
>
> and this shouldn't happen for the compiler built during stage #1. Do you add
> -O2 to the STAGE1_CFLAGS or some such? If so, can you lower it to -O1 or -
> O0?
I don't see it being set from the PKGBUILD but I'll double check when I get back tonight and reply.
I don't have the builddir available atm.
Thanks,
Tamar
>
> --
> Eric Botcazou