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 debug/110308] [14 Regression] ICE on audiofile-0.3.6: RTL: vartrack: Segmentation fault in mode_to_precision(machine_mode)
Date: Mon, 19 Jun 2023 20:50:11 +0000 [thread overview]
Message-ID: <bug-110308-4-8sAMdTMskv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110308-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110308
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|rtl-optimization |debug
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So I think there are 2 bugs here. First the lost of debugging info because of
ch, and the latent segfault.
next prev parent reply other threads:[~2023-06-19 20:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 7:33 [Bug debug/110308] New: " slyfox at gcc dot gnu.org
2023-06-19 7:36 ` [Bug debug/110308] " slyfox at gcc dot gnu.org
2023-06-19 8:06 ` [Bug rtl-optimization/110308] " rguenth at gcc dot gnu.org
2023-06-19 20:47 ` pinskia at gcc dot gnu.org
2023-06-19 20:50 ` pinskia at gcc dot gnu.org [this message]
2023-06-20 9:55 ` [Bug debug/110308] " jakub at gcc dot gnu.org
2023-06-20 10:12 ` jakub at gcc dot gnu.org
2023-06-20 14:47 ` manolis.tsamis at vrull dot eu
2023-06-20 14:56 ` ptomsich at gcc dot gnu.org
2023-06-20 14:57 ` ptomsich at gcc dot gnu.org
2023-06-20 15:00 ` law at gcc dot gnu.org
2023-06-20 15:14 ` manolis.tsamis at vrull dot eu
2023-06-21 7:46 ` slyfox at gcc dot gnu.org
2023-06-21 8:45 ` burnus at gcc dot gnu.org
2023-06-21 8:46 ` burnus at gcc dot gnu.org
2023-06-22 13:18 ` thiago.bauermann at linaro dot org
2023-06-28 14:06 ` cvs-commit at gcc dot gnu.org
2023-11-05 21:52 ` pinskia 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-110308-4-8sAMdTMskv@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).