public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/66661] incorrect memory access in optimization with flexible array member Date: Thu, 25 Jun 2015 07:54:00 -0000 [thread overview] Message-ID: <bug-66661-4-EiwHh0VPNl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66661-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66661 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> --- Yes, consider struct X { int n; char x[1]; }; which has sizeof(X) == 8 unless you use __attribute__((packed)) (in which case alignment also gets dropped down to 1).
next prev parent reply other threads:[~2015-06-25 7:54 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-25 1:25 [Bug c/66661] New: " P at draigBrady dot com 2015-06-25 1:26 ` [Bug c/66661] " P at draigBrady dot com 2015-06-25 2:01 ` [Bug middle-end/66661] " P at draigBrady dot com 2015-06-25 7:54 ` rguenth at gcc dot gnu.org [this message] 2015-06-25 11:04 ` P at draigBrady dot com 2015-06-25 17:13 ` joseph at codesourcery dot com
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-66661-4-EiwHh0VPNl@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).