From: LIU Hao <lh_mouse@126.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: GCC trunk bootstrap failure on i686-w64-mingw32
Date: Wed, 26 Oct 2022 18:52:14 +0800 [thread overview]
Message-ID: <9cf3144a-d796-b7ee-e0e6-5a3119ad342c@126.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2177 bytes --]
Greetings,
Since at least a week ago, GCC trunk fails to bootstrap with a lot such errors during stage1:
```
D:\lh_mouse\GitHub\MINGW-packages\mingw-w64-gcc\src\build-MINGW32\i686-w64-mingw32\libstdc++-v3\src\c++11/../../../../../gcc/libstdc++-v3/src/c++11/functexcept.cc:74:
undefined reference to `_Unwind_SjLj_Register'
C:\MSYS2\mingw32\i686-w64-mingw32\bin\ld.exe:
D:\lh_mouse\GitHub\MINGW-packages\mingw-w64-gcc\src\build-MINGW32\i686-w64-mingw32\libstdc++-v3\src\c++11/../../../../../gcc/libstdc++-v3/src/c++11/functexcept.cc:74:
undefined reference to `_Unwind_SjLj_Resume'
```
It seems that SJLJ exception is enabled (it shouldn't have been) for xgcc, but not for libgcc:
```
build-MINGW32/gcc $ ./xgcc -E -xc /dev/null -B $(pwd) -dM | fgrep SJLJ
#define __USING_SJLJ_EXCEPTIONS__ 1
```
There is clearly `--disable-sjlj-exceptions`:
```
$ ../gcc/configure --prefix=/mingw32 --with-local-prefix=/mingw32/local --build=i686-w64-mingw32
--host=i686-w64-mingw32 --target=i686-w64-mingw32 --with-native-system-header-dir=/mingw32/include
--libexecdir=/mingw32/lib --enable-bootstrap --enable-checking=release --with-arch=i686
--with-tune=generic --enable-languages=c,lto,c++,fortran --enable-shared --enable-static
--enable-libatomic --enable-threads=mcf --enable-graphite --enable-fully-dynamic-string
--enable-libstdcxx-filesystem-ts --enable-libstdcxx-time --disable-libstdcxx-pch --enable-lto
--enable-libgomp --disable-multilib --disable-rpath --disable-win32-registry --disable-nls
--disable-werror --disable-symvers --with-libiconv --with-system-zlib --with-gmp=/mingw32
--with-mpfr=/mingw32 --with-mpc=/mingw32 --with-isl=/mingw32 --with-pkgversion=GCC with MCF thread
model, built by LH_Mouse --with-bugurl=https://github.com/lhmouse/MINGW-packages/issues
--with-gnu-as --with-gnu-ld --disable-libstdcxx-debug --disable-sjlj-exceptions --with-dwarf2
--with-boot-ldflags="-static-libstdc++" --with-stage1-ldflags="-static-libstdc++"
```
GCC 12 release branch doesn't suffer from this issue. So what could be causing it? Thanks in advance.
--
Best regards,
LIU Hao
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next reply other threads:[~2022-10-26 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 10:52 LIU Hao [this message]
2022-10-29 12:15 ` Eric Botcazou
2022-10-29 12:20 ` LIU Hao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9cf3144a-d796-b7ee-e0e6-5a3119ad342c@126.com \
--to=lh_mouse@126.com \
--cc=gcc@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).