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/111663] profiledbootstrap fails on master: gcc/genmodes.cc:2152:1: error: ‘gcc/build/genmodes.gcda’ profile count data file not found [-Werror=missing-profile]
Date: Fri, 06 Oct 2023 19:25:48 +0000 [thread overview]
Message-ID: <bug-111663-4-PaiKiouJgp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111663-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111663
--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Sergei Trofimovich <slyfox@gcc.gnu.org>:
https://gcc.gnu.org/g:2551e10038a70901f30b2168e6e3af4536748f3c
commit r14-4439-g2551e10038a70901f30b2168e6e3af4536748f3c
Author: Sergei Trofimovich <siarheit@google.com>
Date: Mon Oct 2 12:08:17 2023 +0100
Makefile.tpl: disable -Werror for feedback stage [PR111663]
Without the change profiled bootstrap fails for various warnings on
master branch as:
$ ../gcc/configure
$ make profiledbootstrap
...
gcc/genmodes.cc: In function âint main(int, char**)â:
gcc/genmodes.cc:2152:1: error: âgcc/build/genmodes.gcdaâ profile
count data file not found [-Werror=missing-profile]
...
gcc/gengtype-parse.cc: In function âvoid parse_error(const char*,
...)â:
gcc/gengtype-parse.cc:142:21: error: â%sâ directive argument is
null [-Werror=format-overflow=]
The change removes -Werror just like autofeedback does today.
/
PR bootstrap/111663
* Makefile.tpl (STAGEfeedback_CONFIGURE_FLAGS): Disable -Werror.
* Makefile.in: Regenerate.
next prev parent reply other threads:[~2023-10-06 19:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 12:03 [Bug bootstrap/111663] New: " slyfox at gcc dot gnu.org
2023-10-02 12:06 ` [Bug bootstrap/111663] " slyfox at gcc dot gnu.org
2023-10-06 19:25 ` cvs-commit at gcc dot gnu.org [this message]
2023-10-06 19:27 ` slyfox 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-111663-4-PaiKiouJgp@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).