public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jeremy.rutman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/114855] New: ICE: Segfault
Date: Thu, 25 Apr 2024 20:00:22 +0000	[thread overview]
Message-ID: <bug-114855-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 114855
           Summary: ICE: Segfault
           Product: gcc
           Version: 13.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jeremy.rutman at gmail dot com
  Target Milestone: ---

Created attachment 58041
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=58041&action=edit
output from  gcc -v

Attempt to compile some autogenerated code resulted in `cc: internal compiler
error: Segmentation fault signal terminated program cc1` . Compile command was 

gcc -v -Wall -O3 -DNDEBUG -fomit-frame-pointer -freport-bug -save-temps -c
aesDecrypt.c -o aesDecrypt.o

I put the offending source file 
aesDecrypt.c
here:
https://paste.c-net.org/ExamineLarch
and the .i file from the -save-temps 
aesDecrypt.i 
here
https://paste.c-net.org/TiredInduce
I'm not sure what the -freport-bug is doing but I used it in the compile
command anyway.  Apologies for the unwieldy size of the autogenerated code
being compiled.

             reply	other threads:[~2024-04-25 20:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-25 20:00 jeremy.rutman at gmail dot com [this message]
2024-04-25 20:09 ` [Bug middle-end/114855] " pinskia at gcc dot gnu.org
2024-04-25 20:13 ` pinskia at gcc dot gnu.org
2024-04-26  6:00 ` jeremy.rutman at gmail dot com
2024-04-26 14:25 ` rguenth at gcc dot gnu.org
2024-04-26 19:50 ` jeremy.rutman at gmail dot com
2024-04-30  9:13 ` rguenth at gcc dot gnu.org
2024-05-03 21:46 ` amacleod at redhat dot com
2024-05-09 15:57 ` amacleod at redhat dot com
2024-06-22 13:08 ` rguenth at gcc dot gnu.org
2024-06-24 13:04 ` rguenth at gcc dot gnu.org
2024-06-24 13:14 ` rguenth at gcc dot gnu.org
2024-06-24 14:47 ` rguenth at gcc dot gnu.org
2024-06-25  9:23 ` rguenth 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-114855-4@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).