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 c/113727] csmith: differences from nothing to -O1 Date: Sat, 03 Feb 2024 10:11:24 +0000 [thread overview] Message-ID: <bug-113727-4-kjzZspRxpQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113727-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113727 Xi Ruoyao <xry111 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xry111 at gcc dot gnu.org See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=109982 --- Comment #8 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- #pragma pack(push) #pragma pack(1) struct S0 { signed f0 : 22; uint32_t f1; unsigned f2 : 5; unsigned f3 : 21; unsigned f4 : 8; signed f5 : 22; signed f6 : 1; signed f7 : 23; signed f8 : 10; }; #pragma pack(pop) Removing these #pragma silence the UBSan. But I bet the code is just invalid with those #pragma and with #pragma removed the issue will just gone, like PR109982.
next prev parent reply other threads:[~2024-02-03 10:11 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-02 19:40 [Bug c/113727] New: " dcb314 at hotmail dot com 2024-02-02 20:27 ` [Bug c/113727] " sjames at gcc dot gnu.org 2024-02-02 20:40 ` dcb314 at hotmail dot com 2024-02-02 21:03 ` dcb314 at hotmail dot com 2024-02-02 21:15 ` dcb314 at hotmail dot com 2024-02-02 21:40 ` dcb314 at hotmail dot com 2024-02-02 21:47 ` dcb314 at hotmail dot com 2024-02-02 21:49 ` sjames at gcc dot gnu.org 2024-02-03 10:11 ` xry111 at gcc dot gnu.org [this message] 2024-02-03 10:15 ` xry111 at gcc dot gnu.org 2024-02-03 11:07 ` dcb314 at hotmail dot com 2024-02-03 11:08 ` dcb314 at hotmail dot com 2024-02-03 18:54 ` xry111 at gcc dot gnu.org 2024-02-04 19:42 ` [Bug c/113727] [14 Regression] " pinskia at gcc dot gnu.org 2024-03-15 15:01 ` [Bug tree-optimization/113727] " law at gcc dot gnu.org 2024-03-18 8:45 ` sjames at gcc dot gnu.org 2024-03-19 5:58 ` sjames at gcc dot gnu.org 2024-03-19 6:04 ` sjames at gcc dot gnu.org 2024-03-19 6:09 ` pinskia at gcc dot gnu.org 2024-03-19 6:24 ` pinskia at gcc dot gnu.org 2024-03-19 6:41 ` pinskia at gcc dot gnu.org 2024-03-19 6:47 ` pinskia at gcc dot gnu.org 2024-03-19 9:46 ` [Bug tree-optimization/113727] [14 Regression] csmith: differences from nothing to -O1 since r14-4612-g6decda1a35be57 rguenth at gcc dot gnu.org 2024-03-19 10:51 ` rguenth at gcc dot gnu.org 2024-03-19 11:22 ` rguenth at gcc dot gnu.org 2024-03-19 13:40 ` rguenth at gcc dot gnu.org 2024-03-21 7:33 ` cvs-commit at gcc dot gnu.org 2024-03-21 7:34 ` 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-113727-4-kjzZspRxpQ@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).