public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stefansf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/114432] [13 Regression] ICE in connect_traces, at dwarf2cfi.cc:3079 on s390x-linux-gnu Date: Mon, 22 Apr 2024 15:45:30 +0000 [thread overview] Message-ID: <bug-114432-4-ZJMAZeint2@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-114432-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114432 --- Comment #4 from Stefan Schulze Frielinghaus <stefansf at gcc dot gnu.org> --- Ignore the previous comment. With -fstack-check and -mbackchain we have for trace 2 an incoming edge from trace 1 (fallthrough) where cur_trace->end_true_args_size == 48 and from further incoming edges as e.g. from trace 7 where cur_trace->end_true_args_size == 0 which is why the args_size is supposed to be undefined. Interestingly, trace 2 resides in the function body whereas trace 7 resides in the epilogue, i.e., we have a jump from the epilogue into the function body: (note 597 810 634 NOTE_INSN_PROLOGUE_END) ... (insn 635 677 566 (set (reg/f:DI 15 %r15) (plus:DI (reg/f:DI 15 %r15) (const_int 8216 [0x2018]))) "libalog-0.6.2/src/alog-active_logger.adb":244:4 1481 {*la_64} (expr_list:REG_ARGS_SIZE (const_int 48 [0x30]) (nil))) ... (code_label 48 573 49 152 (nil) [2 uses]) ... (note 673 768 599 NOTE_INSN_EPILOGUE_BEG) ... (insn 159 163 160 (set (reg/f:DI 15 %r15) (reg/f:DI 6 %r6 [orig:79 saved_stack.186_50 ] [79])) "libalog-0.6.2/src/alog-active_logger.adb":260:0 discrim 10 1477 {*movdi_64} (expr_list:REG_DEAD (reg/f:DI 6 %r6 [orig:79 saved_stack.186_50 ] [79]) (expr_list:REG_ARGS_SIZE (const_int 0 [0]) (nil)))) ... (jump_insn 645 644 646 (set (pc) (label_ref 48)) 2170 {*jump64} (nil) -> 48) This is also the case when -fno-shrink-wrap is used.
next prev parent reply other threads:[~2024-04-22 15:45 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-22 13:13 [Bug target/114432] New: " doko at gcc dot gnu.org 2024-03-22 14:23 ` [Bug target/114432] " rguenth at gcc dot gnu.org 2024-04-17 8:44 ` stefansf at gcc dot gnu.org 2024-04-17 11:06 ` stefansf at gcc dot gnu.org 2024-04-17 11:07 ` stefansf at gcc dot gnu.org 2024-04-22 15:45 ` stefansf at gcc dot gnu.org [this message] 2024-05-08 12:28 ` [Bug target/114432] [13/14/15 " rguenth at gcc dot gnu.org 2024-05-08 12:29 ` rguenth at gcc dot gnu.org 2024-05-21 9:19 ` jakub 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-114432-4-ZJMAZeint2@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: linkBe 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).