public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/109593] valgrind error doing build of latest gcc trunk
Date: Sat, 22 Apr 2023 19:36:30 +0000 [thread overview]
Message-ID: <bug-109593-4-YB0IoUKF4E@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109593-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109593
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Component|c |tree-optimization
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to David Binderman from comment #6)
> (In reply to Aldy Hernandez from comment #5)
> > Can you verify that's the commit?
>
> git bisect says:
>
> 10e481b154c5fc63e6ce4b449ce86cecb87a6015 is the first bad commit.
r14-32-g10e481b154c5fc63
next prev parent reply other threads:[~2023-04-22 19:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-22 11:47 [Bug c/109593] New: " dcb314 at hotmail dot com
2023-04-22 12:54 ` [Bug c/109593] " sjames at gcc dot gnu.org
2023-04-22 13:21 ` dcb314 at hotmail dot com
2023-04-22 17:14 ` dcb314 at hotmail dot com
2023-04-22 17:53 ` dcb314 at hotmail dot com
2023-04-22 19:04 ` aldyh at gcc dot gnu.org
2023-04-22 19:14 ` dcb314 at hotmail dot com
2023-04-22 19:36 ` pinskia at gcc dot gnu.org [this message]
2023-04-22 19:36 ` [Bug tree-optimization/109593] [14 Regression] " pinskia at gcc dot gnu.org
2023-04-23 6:07 ` [Bug tree-optimization/109593] [14 Regression] Valgrind error doing build of latest gcc trunk since r14-32-g10e481b154c5fc63 aldyh at gcc dot gnu.org
2023-04-23 8:02 ` dcb314 at hotmail dot com
2023-04-23 9:04 ` cvs-commit at gcc dot gnu.org
2023-04-23 9:05 ` aldyh 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-109593-4-YB0IoUKF4E@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).