public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ucko at ncbi dot nlm.nih.gov" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108137] [12/13 Regression] ICE: segfault during GIMPLE pass: warn-printf since r12-523-g2254b3233b5bfa69
Date: Tue, 20 Dec 2022 16:38:28 +0000 [thread overview]
Message-ID: <bug-108137-4-aZNxMwucWT@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108137-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108137
--- Comment #5 from ucko at ncbi dot nlm.nih.gov ---
> --- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
> I can fix that.
That would be great, thanks; I can fairly easily work around this bug in the
file where I first hit it, but we have another (non-public) file that's much
more severely affected. Our sysadmins are prepared to supply test
installations incorporating any patches you draft.
next prev parent reply other threads:[~2022-12-20 16:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 20:30 [Bug c/108137] New: [12 Regression] ICE: segfault during GIMPLE pass: warn-printf ucko at ncbi dot nlm.nih.gov
2022-12-15 21:59 ` [Bug tree-optimization/108137] [12/13 " pinskia at gcc dot gnu.org
2022-12-15 22:07 ` pinskia at gcc dot gnu.org
2022-12-15 23:02 ` ucko at ncbi dot nlm.nih.gov
2022-12-16 12:29 ` [Bug tree-optimization/108137] [12/13 Regression] ICE: segfault during GIMPLE pass: warn-printf since r12-523-g2254b3233b5bfa69 marxin at gcc dot gnu.org
2022-12-16 12:38 ` marxin at gcc dot gnu.org
2022-12-20 16:38 ` ucko at ncbi dot nlm.nih.gov [this message]
2022-12-21 12:43 ` rguenth at gcc dot gnu.org
2022-12-27 15:07 ` marxin at gcc dot gnu.org
2022-12-28 8:15 ` cvs-commit at gcc dot gnu.org
2022-12-28 8:15 ` [Bug tree-optimization/108137] [12 " marxin at gcc dot gnu.org
2023-01-10 15:43 ` ucko at ncbi dot nlm.nih.gov
2023-01-11 10:29 ` marxin at gcc dot gnu.org
2023-01-11 11:27 ` cvs-commit at gcc dot gnu.org
2023-01-11 11:27 ` marxin 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-108137-4-aZNxMwucWT@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).