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 bootstrap/95413] [11 regression] i686-linux --enable-targets=all cannot configure m64 libgomp
Date: Fri, 29 May 2020 15:57:17 +0000 [thread overview]
Message-ID: <bug-95413-4-8hn6g1yE0Y@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
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #1)
> > 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?
-march=i486 -mtune=i686 is something added by libgomp/configure.tgt:
# Note that bare i386 is not included here. We need cmpxchg.
i[456]86-*-linux*)
config_path="linux/x86 linux posix"
case " ${CC} ${CFLAGS} " in
*" -m64 "*|*" -mx32 "*)
;;
*)
if test -z "$with_arch"; then
XCFLAGS="${XCFLAGS} -march=i486 -mtune=${target_cpu}"
fi
esac
;;
But that should enable it only when building the 32-bit libgomp and not 32-bit.
So something else must be adding -m64 somewhere later.
next prev parent reply other threads:[~2020-05-29 15:57 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
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 [this message]
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-8hn6g1yE0Y@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).