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 c/105675] Segmentation fault
Date: Fri, 20 May 2022 17:56:54 +0000 [thread overview]
Message-ID: <bug-105675-4-X0iXfUpg30@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105675-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105675
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
Last reconfirmed| |2022-05-20
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>Running gcc on input file from an attachment resulting in segmentation fault
The file didn't attach, maybe it was too big. Can you try to compress it and
attach that?
next prev parent reply other threads:[~2022-05-20 17:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 16:26 [Bug c/105675] New: " watarai775 at gmail dot com
2022-05-20 17:56 ` pinskia at gcc dot gnu.org [this message]
2022-05-20 18:20 ` [Bug c++/105675] " watarai775 at gmail dot com
2022-05-20 18:38 ` [Bug c/105675] " pinskia at gcc dot gnu.org
2022-05-22 12:44 ` watarai775 at gmail dot com
2022-05-23 7:39 ` watarai775 at gmail dot com
2022-05-23 7:44 ` watarai775 at gmail dot com
2022-05-23 7:49 ` 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-105675-4-X0iXfUpg30@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).