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 middle-end/113077] New: [14 Regression] ICE in  dwarf2out_frame_debug_cfa_offset with `-O2 -fstack-protector-strong -fstack-clash-protection`
Date: Tue, 19 Dec 2023 03:44:43 +0000	[thread overview]
Message-ID: <bug-113077-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 113077
           Summary: [14 Regression] ICE in
                    dwarf2out_frame_debug_cfa_offset with `-O2
                    -fstack-protector-strong -fstack-clash-protection`
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: middle-end
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64-linux-gnu

Reduced testcase:
```
void add_key(const void *payload);
void act_keyctl_test(void) {
  char buf[1030 * 1024];
  int i = 0;
  for (i = 0; i < sizeof(buf); i++) 
  {
    add_key(buf);
  }
}

```

```
$ ./install/bin/aarch64-linux-gnu-gcc Hgs7.i -O2  -S   
-fstack-protector-strong -fstack-clash-protection
during RTL pass: dwarf2
keyctl_testing.c: In function ‘act_keyctl_test_limits2’:
keyctl_testing.c:225:1: internal compiler error: in
dwarf2out_frame_debug_cfa_offset, at dwarf2cfi.cc:1376
0x78228a dwarf2out_frame_debug_cfa_offset
        ../../gcc/dwarf2cfi.cc:1376
0x78228a dwarf2out_frame_debug
        ../../gcc/dwarf2cfi.cc:2285
0x78228a scan_insn_after
        ../../gcc/dwarf2cfi.cc:2726
0xb8c55b scan_trace
        ../../gcc/dwarf2cfi.cc:2893
0xb8ccbe create_cfi_notes
        ../../gcc/dwarf2cfi.cc:2933
0xb8ccbe execute_dwarf2_frame
        ../../gcc/dwarf2cfi.cc:3309
0xb8ccbe execute
        ../../gcc/dwarf2cfi.cc:3797
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
```

             reply	other threads:[~2023-12-19  3:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19  3:44 pinskia at gcc dot gnu.org [this message]
2023-12-19  3:45 ` [Bug middle-end/113077] " pinskia at gcc dot gnu.org
2023-12-19  3:47 ` pinskia at gcc dot gnu.org
2023-12-19  3:52 ` pinskia at gcc dot gnu.org
2023-12-19  9:44 ` acoplan at gcc dot gnu.org
2024-01-08 12:51 ` [Bug target/113077] " jakub at gcc dot gnu.org
2024-01-08 14:50 ` acoplan at gcc dot gnu.org
2024-01-08 15:00 ` jakub at gcc dot gnu.org
2024-01-08 15:05 ` acoplan at gcc dot gnu.org
2024-01-09  9:13 ` acoplan at gcc dot gnu.org
2024-01-09 11:30 ` acoplan at gcc dot gnu.org
2024-01-09 15:38 ` acoplan at gcc dot gnu.org
2024-01-10  9:57 ` acoplan at gcc dot gnu.org
2024-01-10 17:02 ` acoplan at gcc dot gnu.org
2024-01-11  9:39 ` acoplan at gcc dot gnu.org
2024-01-11 10:17 ` cvs-commit at gcc dot gnu.org
2024-01-11 10:19 ` acoplan 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-113077-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).