public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/95413] [11 regression] i686-linux --enable-targets=all cannot configure m64 libgomp
Date: Fri, 29 May 2020 13:02:34 +0000 [thread overview]
Message-ID: <bug-95413-4-rXHPGJPObb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95413-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95413
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2020-05-29
Ever confirmed|0 |1
--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Rainer Orth from comment #0)
> Between 20200515 and 20200522, Linux/i686 bootstrap with --enable-targets=all
> broke: after configuring with
>
> $ .../configure CC='gcc -m32' CXX='g++ -m32' --enable-targets=all
> --enable-languages=c --build=i686-pc-linux-gnu --disable-lto-plugin
>
> configuring the stage1 64-bit libgomp fails:
>
> checking whether the C compiler works... no
> configure: error: in
> `/var/gcc/gcc-11.0.0-20200529/4.20.4-gcc-32/i686-pc-linux-gnu/64/libgomp':
> configure: error: C compiler cannot create executables
> See `config.log' for more details
> make[2]: *** [Makefile:20360: configure-stage1-target-libgomp] Error 1
>
> config.log has
>
> configure:3935:
> /var/gcc/regression/master/4.20.4-gcc-gas-gld-32/build/./gcc/xgcc
> -B/var/gcc/regression/master/4.20.4-gcc-gas-gld-32/build/./gcc/
> -B/vol/gcc/i686-pc-linux-gnu/bin/ -B/vol/gcc/i686-pc-linux-gnu/lib/ -isystem
> /vol/gcc/i686-pc-linux-gnu/include -isystem
> /vol/gcc/i686-pc-linux-gnu/sys-include -fno-checking -m64 -g -O2 -pthread
> -Wall -Werror -ftls-model=initial-exec -DUSING_INITIAL_EXEC_TLS -march=i486
> -mtune=i686 conftest.c >&5
> cc1: error: CPU you selected does not support x86-64 instruction set
>
> whereas before this was
>
> configure:3913: checking whether the C compiler works
> configure:3935:
> /var/gcc/regression/master/4.20.4-gcc-gas-gld-32/build/./gcc/xgcc
> -B/var/gcc/regression/master/4.20.4-gcc-gas-gld-32/build/./gcc/
> -B/vol/gcc/i686-pc-linux-gnu/bin/ -B/vol/gcc/i686-pc-linux-gnu/lib/ -isystem
> /vol/gcc/i686-pc-linux-gnu/include -isystem
> /vol/gcc/i686-pc-linux-gnu/sys-include -fno-checking -m64 -g -O2 -pthread
> conftest.c >&5
>
> I strongly suspect the CET patches, but haven't yet figured out what's going
> wrong.
How did CET changes add -march=i486 -mtune=i686? Can you bisect to the commit?
next prev parent reply other threads:[~2020-05-29 13:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 11:56 [Bug bootstrap/95413] New: " ro at gcc dot gnu.org
2020-05-29 11:56 ` [Bug bootstrap/95413] " ro at gcc dot gnu.org
2020-05-29 13:02 ` hjl.tools at gmail dot com [this message]
2020-05-29 14:19 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-05-29 14:24 ` hjl.tools at gmail dot com
2020-05-29 14:25 ` hjl.tools at gmail dot com
2020-05-29 14:39 ` hjl.tools at gmail dot com
2020-05-29 15:57 ` jakub at gcc dot gnu.org
2020-05-29 17:51 ` hjl.tools at gmail dot com
2020-05-29 18:57 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-05-29 19:53 ` hjl.tools at gmail dot com
2020-05-29 19:56 ` cvs-commit at gcc dot gnu.org
2020-05-29 19:57 ` hjl.tools at gmail dot com
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-95413-4-rXHPGJPObb@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).