public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "larry9 at ffdlr dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110229] Segment fault with initializer an array (unrolled) in a function
Date: Mon, 12 Jun 2023 17:54:07 +0000	[thread overview]
Message-ID: <bug-110229-4-Cqc1ihiF1B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110229-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110229

--- Comment #2 from Larry Fiedler <larry9 at ffdlr dot com> ---
Created attachment 55313
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55313&action=edit
script to make the c++ file that segfaults

  parent reply	other threads:[~2023-06-12 17:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 17:44 [Bug c++/110229] New: Segment fault on git clone larry9 at ffdlr dot com
2023-06-12 17:47 ` [Bug c++/110229] Segment fault with initializer an array (unrolled) in a function pinskia at gcc dot gnu.org
2023-06-12 17:54 ` larry9 at ffdlr dot com [this message]
2023-06-12 18:02 ` [Bug middle-end/110229] " pinskia at gcc dot gnu.org
2023-06-12 18:11 ` larry9 at ffdlr dot com

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-110229-4-Cqc1ihiF1B@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).