public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/111330] [13 Regression] Bootstrap failure building SeqFile.lo
Date: Fri, 08 Sep 2023 20:08:35 +0000 [thread overview]
Message-ID: <bug-111330-4-RsD7hrCmAd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111330-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111330
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, narrowed it down to Fedora build doing essentially (stripped down from all
languages etc.):
CC=gcc \
CXX=g++ \
CFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -Wall -Wformat-security
-Wp,-D_GLIBCXX_ASSERTIONS -mtune=generic -fasynchronous-unwind-tables
-fstack-clash-protection -fcf-protection' \
CXXFLAGS=' -O2 -g -grecord-gcc-switches -Wformat -Wformat-security
-Wp,-D_GLIBCXX_ASSERTIONS -mtune=generic -fasynchronous-unwind-tables
-fstack-clash-protection -fcf-protection ' \
XCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -Wall -Wformat-security
-Wp,-D_GLIBCXX_ASSERTIONS -mtune=generic -fasynchronous-unwind-tables
-fstack-clash-protection -fcf-protection' \
TCFLAGS='-O2 -fexceptions -g -grecord-gcc-switches -Wall -Wformat-security
-Wp,-D_GLIBCXX_ASSERTIONS -mtune=generic -fasynchronous-unwind-tables
-fstack-clash-protection -fcf-protection' \
../configure --disable-bootstrap --enable-languages=c,c++,m2,lto
--enable-checking=release --enable-multilib --disable-libsanitizer
--with-gcc-major-version-only --enable-plugin --enable-gnu-indirect-function
--enable-cet --with-tune=generic --with-arch_32=i686
--build=x86_64-redhat-linux
make -j32 'BOOT_CFLAGS=-O2 -fexceptions -g -grecord-gcc-switches -Wall
-Wformat-security -Wp,-D_GLIBCXX_ASSERTIONS -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection'
LDFLAGS_FOR_TARGET=-Wl,-z,relro,-z,now
And what matters is using -Wall during the build in *FLAGS.
/builddir/build/BUILD/gcc-13.2.1-20230728/obj-x86_64-redhat-linux/./gcc/gm2
-B/builddir/build/BUILD/gcc-13.2.1-20230728/obj-x86_64-redhat-linux/./gcc/ -c
-O2 -Wall -fm2-pathname=m2iso -I. -Ilibm2iso
-I/builddir/build/BUILD/gcc-13.2.1-20230728/gcc/m2/gm2-libs-iso
-fm2-pathname=m2pim -I/builddir/build/BUILD/gcc-13.2.1-20230728/gcc/m2/gm2-libs
-fiso -fextended-opaque -fm2-g -g -Wreturn-type -fcase -fm2-prefix=m2iso
../../../../libgm2/libm2iso/../../gcc/m2/gm2-libs-iso/SeqFile.mod -fPIC -DPIC
-o .libs/SeqFile.o; echo $?
../../gcc/m2/gm2-compiler/M2SymInit.def:1:case statement has no matching
selection
1
while
/builddir/build/BUILD/gcc-13.2.1-20230728/obj-x86_64-redhat-linux/./gcc/gm2
-B/builddir/build/BUILD/gcc-13.2.1-20230728/obj-x86_64-redhat-linux/./gcc/ -c
-O2 -fm2-pathname=m2iso -I. -Ilibm2iso
-I/builddir/build/BUILD/gcc-13.2.1-20230728/gcc/m2/gm2-libs-iso
-fm2-pathname=m2pim -I/builddir/build/BUILD/gcc-13.2.1-20230728/gcc/m2/gm2-libs
-fiso -fextended-opaque -fm2-g -g -Wreturn-type -fcase -fm2-prefix=m2iso
../../../../libgm2/libm2iso/../../gcc/m2/gm2-libs-iso/SeqFile.mod -fPIC -DPIC
-o .libs/SeqFile.o; echo $?
0
Shouldn't -Wall affect just warnings (without -Werror) and not whether
compilation succeeds or fails?
next prev parent reply other threads:[~2023-09-08 20:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 19:55 [Bug modula2/111330] New: " jakub at gcc dot gnu.org
2023-09-08 18:21 ` [Bug modula2/111330] " jakub at gcc dot gnu.org
2023-09-08 18:23 ` jakub at gcc dot gnu.org
2023-09-08 19:57 ` jakub at gcc dot gnu.org
2023-09-08 20:08 ` jakub at gcc dot gnu.org [this message]
2023-09-08 20:36 ` jakub at gcc dot gnu.org
2023-09-09 12:37 ` gaius at gcc dot gnu.org
2023-09-09 12:49 ` gaius at gcc dot gnu.org
2023-09-11 14:02 ` gaius at gcc dot gnu.org
2023-09-11 20:21 ` gaius at gcc dot gnu.org
2023-09-11 21:28 ` cvs-commit at gcc dot gnu.org
2023-09-11 21:30 ` cvs-commit at gcc dot gnu.org
2023-09-12 11:27 ` rguenth at gcc dot gnu.org
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=bug-111330-4-RsD7hrCmAd@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).