public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames 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: Fri, 02 Feb 2024 20:27:37 +0000 [thread overview] Message-ID: <bug-113727-4-mQzG0VLdwr@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 Sam James <sjames at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |sjames at gcc dot gnu.org --- Comment #1 from Sam James <sjames at gcc dot gnu.org> --- With UBSAN, I get: ``` $ gcc-13 -ggdb3 -fsanitize=address,undefined /tmp/PR113727.c -o /tmp/PR113727 $ /tmp/PR113727 runData/keep/in.9954.c:416:134: runtime error: store to misaligned address 0x55a497188a23 for type 'uint32_t', which requires 4 byte alignment 0x55a497188a23: note: pointer points here 00 a5 07 00 83 88 64 91 23 2a 00 28 bc 14 00 50 fe ff 15 00 00 00 00 00 00 00 00 00 00 00 00 00 ^ #0 0x55a49716fda5 in func_46 runData/keep/in.9954.c:416 #1 0x55a49716c2fb in func_19 runData/keep/in.9954.c:352 #2 0x55a49716661e in func_1 runData/keep/in.9954.c:153 #3 0x55a49717dc21 in main runData/keep/in.9954.c:838 #4 0x7f9632452e69 (/usr/lib64/libc.so.6+0x25e69) #5 0x7f9632452f1c in __libc_start_main (/usr/lib64/libc.so.6+0x25f1c) #6 0x55a4971632e0 in _start (/tmp/PR113727+0x172e0) ```
next prev parent reply other threads:[~2024-02-02 20:27 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 ` sjames at gcc dot gnu.org [this message] 2024-02-02 20:40 ` [Bug c/113727] " 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 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-mQzG0VLdwr@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).