public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/111974] internal error: Segmentation fault on Ubuntu 23.10 (x86-64) - compiling RefPerSys
Date: Wed, 25 Oct 2023 10:21:55 +0000 [thread overview]
Message-ID: <bug-111974-4-zLyON8VtRg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111974-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111974
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Basile Starynkevitch from comment #0)
> Please submit a full bug report, with preprocessed source (by using
> -freport-bug).
^^^
next prev parent reply other threads:[~2023-10-25 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 9:18 [Bug c++/111974] New: internal error: Segmentation fault on Ubuntu 23.10 (x86-64) basile at starynkevitch dot net
2023-10-25 10:02 ` [Bug c++/111974] internal error: Segmentation fault on Ubuntu 23.10 (x86-64) - compiling RefPerSys basile at starynkevitch dot net
2023-10-25 10:21 ` redi at gcc dot gnu.org [this message]
2023-10-25 11:19 ` basile at starynkevitch dot net
2023-10-27 12:39 ` rguenth at gcc dot gnu.org
2023-10-28 3:34 ` sjames at gcc dot gnu.org
2024-02-16 18:34 ` mpolacek 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-111974-4-zLyON8VtRg@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).