public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109093] [13 regression] csmith: a February runtime bug ? Date: Tue, 14 Mar 2023 19:56:39 +0000 [thread overview] Message-ID: <bug-109093-4-8HoC35VbZe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109093-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109093 --- Comment #15 from H.J. Lu <hjl.tools at gmail dot com> --- The crash went away after r13-6661-gbd6e566e9dc543 which removed variables only used with .DEFERRED_INIT. If variables are used, they will be captured by ix86_find_max_used_stack_alignment. Is there a testcase without unused variables?
next prev parent reply other threads:[~2023-03-14 19:56 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-10 17:32 [Bug c/109093] New: " dcb314 at hotmail dot com 2023-03-10 18:51 ` [Bug target/109093] " dcb314 at hotmail dot com 2023-03-10 20:03 ` dcb314 at hotmail dot com 2023-03-10 20:17 ` dcb314 at hotmail dot com 2023-03-10 20:19 ` [Bug target/109093] [13 regression] " pinskia at gcc dot gnu.org 2023-03-10 20:26 ` dcb314 at hotmail dot com 2023-03-13 13:06 ` jakub at gcc dot gnu.org 2023-03-13 13:13 ` jakub at gcc dot gnu.org 2023-03-13 13:15 ` jakub at gcc dot gnu.org 2023-03-13 15:24 ` jakub at gcc dot gnu.org 2023-03-13 18:28 ` pinskia at gcc dot gnu.org 2023-03-13 20:53 ` jakub at gcc dot gnu.org 2023-03-14 1:08 ` hjl.tools at gmail dot com 2023-03-14 7:09 ` jakub at gcc dot gnu.org 2023-03-14 16:06 ` hjl.tools at gmail dot com 2023-03-14 18:47 ` jakub at gcc dot gnu.org 2023-03-14 19:13 ` jakub at gcc dot gnu.org 2023-03-14 19:56 ` hjl.tools at gmail dot com [this message] 2023-03-14 20:42 ` jakub at gcc dot gnu.org 2023-03-14 20:51 ` hjl.tools at gmail dot com 2023-03-15 9:19 ` jakub at gcc dot gnu.org 2023-03-15 19:24 ` hjl.tools at gmail dot com 2023-03-15 19:38 ` jakub at gcc dot gnu.org 2023-03-15 19:50 ` hjl.tools at gmail dot com 2023-03-31 14:59 ` jakub at gcc dot gnu.org 2023-03-31 15:07 ` [Bug target/109093] " jakub at gcc dot gnu.org 2023-04-26 6:58 ` rguenth at gcc dot gnu.org 2023-05-09 13:13 ` dcb314 at hotmail dot com 2023-05-09 13:14 ` dcb314 at hotmail dot com 2023-07-27 9:25 ` rguenth at gcc dot gnu.org 2024-05-16 9:10 ` rguenth at gcc dot gnu.org 2024-05-21 9:14 ` 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-109093-4-8HoC35VbZe@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).