public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/58346] ICE with SIGFPE at -O1 and above on x86_64-linux-gnu (affecting trunk, 4.8, 4.7, and 4.6) Date: Tue, 10 Sep 2013 22:22:00 -0000 [thread overview] Message-ID: <bug-58346-4-VVODmKB8Vc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58346-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58346 --- Comment #7 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- On Tue, 10 Sep 2013, rguenther at suse dot de wrote: > A similar (runtime) error can be provoked by subtracting pointers > to array elements of variable size that happen to have zero size > at runtime. Yes, that needs to be undefined at runtime. > This all seems to be a can of worms which I'd rather shield the > middle-end from. For example we assume that a[0] and a[1] never > alias. As I noted in bug 57725, code using zero-size objects should not care about whether their addresses compare equal - and any other consequence of a non-aliasing deduction shouldn't matter (given that stores to such objects will store zero bytes and reads from them will read zero bytes). > Can we at least make arrays of zero-sized elements trigger undefined > behavior in our extension documentation? We probably can paper > over the ICEs as they occur (testing coverage is very weak of course). It's specifically the subtraction of pointers that needs to be undefined. I'm doubtful about making such arrays undefined in the absence of such subtraction. Uses of zero-size objects are e.g. for when an object may be empty for some configurations of a program but not others (depending on whether a lock object is needed in that configuration, say), and it seems plausible someone might have an array of such conditionally zero-size objects, each corresponding to an element of another array (if there's a reason why using a single array of structs isn't appropriate).
next prev parent reply other threads:[~2013-09-10 22:22 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-58346-4@http.gcc.gnu.org/bugzilla/> 2013-09-08 8:13 ` [Bug ipa/58346] " mikpe at it dot uu.se 2013-09-09 8:29 ` [Bug c/58346] " rguenth at gcc dot gnu.org 2013-09-09 8:34 ` rguenth at gcc dot gnu.org 2013-09-09 17:04 ` joseph at codesourcery dot com 2013-09-10 7:49 ` rguenther at suse dot de 2013-09-10 22:22 ` joseph at codesourcery dot com [this message] 2014-01-10 16:27 ` mpolacek at gcc dot gnu.org 2014-01-17 10:15 ` mpolacek at gcc dot gnu.org 2014-01-17 10:19 ` mpolacek at gcc dot gnu.org 2014-01-17 14:52 ` mpolacek at gcc dot gnu.org 2014-01-17 17:06 ` law at redhat dot com 2014-01-23 19:19 ` mpolacek 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-58346-4-VVODmKB8Vc@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).