public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/110294] [10/11 Regression] Segmentation fault with '-O3 -fno-dce -fno-toplevel-reorder -fno-tree-dce -fno-tree-pta -fno-tree-sink -ftoplevel-reorder'
Date: Fri, 30 Jun 2023 09:31:23 +0000 [thread overview]
Message-ID: <bug-110294-4-PWGbvc65t6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110294-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110294
--- Comment #4 from Xi Ruoyao <xry111 at gcc dot gnu.org> ---
(In reply to CTC from comment #3)
> Another related and smaller reproducer:
>
> # cat tmp.i
> a;
> *const b;
> main() { a != *b; }
This is an undefined behavior and the compiler is allowed to generate code to
crash. When you use tools like cvise for reducing a "crashing" test case you
need to add more constraints so it won't result such an invalid test case.
next prev parent reply other threads:[~2023-06-30 9:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 4:49 [Bug c/110294] New: " 19373742 at buaa dot edu.cn
2023-06-17 4:49 ` [Bug c/110294] " 19373742 at buaa dot edu.cn
2023-06-17 6:50 ` xry111 at gcc dot gnu.org
2023-06-19 6:58 ` [Bug middle-end/110294] [10/11 Regression] " rguenth at gcc dot gnu.org
2023-06-30 9:08 ` 19373742 at buaa dot edu.cn
2023-06-30 9:31 ` xry111 at gcc dot gnu.org [this message]
2023-07-07 10:45 ` [Bug middle-end/110294] [11 " rguenth at gcc dot gnu.org
2024-01-10 15:23 ` jamborm at gcc dot gnu.org
2024-01-11 1:05 ` pinskia 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-110294-4-PWGbvc65t6@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).