public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/100246] [11/12 Regression] GCC will not bootstrap with clang 3.4/3.5 [xcode 5/6, Darwin 12/13]
Date: Fri, 05 Nov 2021 15:59:36 +0000 [thread overview]
Message-ID: <bug-100246-4-vpka7nasKe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100246-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100246
--- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:858d7ee1a0cd97c01d844ea73ab81918da738344
commit r12-4944-g858d7ee1a0cd97c01d844ea73ab81918da738344
Author: Jakub Jelinek <jakub@redhat.com>
Date: Fri Nov 5 16:39:14 2021 +0100
x86: Make stringop_algs::stringop_strategy ctor constexpr [PR100246]
> Several older compilers fail to build modern GCC because of missing
> or incomplete C++11 support.
>
> * config/i386/i386.h (struct stringop_algs): Define a CTOR for
> this type.
Unfortunately, as mentioned in my
https://gcc.gnu.org/pipermail/gcc-patches/2021-November/583289.html
mail, without the new dyninit pass this causes dynamic initialization of
many variables, 6.5KB _GLOBAL__sub_I_* on x86_64 and 12.5KB on i686.
The following patch makes the ctor constexpr so that already the FE
is able to statically initialize all those.
I have tested on godbolt a reduced testcase without a constructor,
with constructor and with constexpr constructor.
clang before 3.3 is unhappy about all the 3 cases, clang 3.3 and 3.4
is ok with ctor and ctor with constexpr and optimizes it into static
initialization, clang 3.5+ is ok with all 3 versions and optimizes,
gcc 4.8 and 5+ is ok with all 3 versions and no ctor and ctor with
constexpr
is optimized, gcc 4.9 is unhappy about the no ctor case and happy with the
other two.
2021-11-05 Jakub Jelinek <jakub@redhat.com>
PR bootstrap/100246
* config/i386/i386.h
(stringop_algs::stringop_strategy::stringop_strategy): Make the
ctor
constexpr.
next prev parent reply other threads:[~2021-11-05 15:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-24 15:52 [Bug bootstrap/100246] New: " iains at gcc dot gnu.org
2021-04-24 15:54 ` [Bug bootstrap/100246] " iains at gcc dot gnu.org
2021-04-24 20:21 ` iains at gcc dot gnu.org
2021-04-26 7:23 ` rguenth at gcc dot gnu.org
2021-04-27 19:34 ` gcc@Denis-Excoffier.org
2021-05-05 7:43 ` iains at gcc dot gnu.org
2021-05-07 19:44 ` iains at gcc dot gnu.org
2021-05-09 9:01 ` gcc@Denis-Excoffier.org
2021-05-10 8:40 ` iains at gcc dot gnu.org
2021-05-13 18:53 ` pinskia at gcc dot gnu.org
2021-07-06 10:14 ` cvs-commit at gcc dot gnu.org
2021-07-20 6:58 ` cvs-commit at gcc dot gnu.org
2021-07-20 6:59 ` iains at gcc dot gnu.org
2021-11-05 15:59 ` cvs-commit at gcc dot gnu.org [this message]
2021-11-29 8:49 ` cvs-commit 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-100246-4-vpka7nasKe@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).