public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rafael.espindola at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/50284] New: possible miscompilation with -fstrict-aliasing
Date: Sat, 03 Sep 2011 18:50:00 -0000	[thread overview]
Message-ID: <bug-50284-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50284

             Bug #: 50284
           Summary: possible miscompilation with -fstrict-aliasing
    Classification: Unclassified
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rafael.espindola@gmail.com


I am not sure if the attached program is valid, but I think it is covered by
c99 6.5 p7. On irc pinkia points out that it might be invalid. His arguments
are

* upcast is undefined in general, 6.5 p7 is trying to allow downcasting.
* upcasting is defined when the type was originally that type.

Two followup observations are that

* If we read "z->data.XXX" as an access to the member (an not the full
structure), all the access in the program are of the correct type.
* On the implementation side, this "bug" show up when main is in a another
translation unit too, a case where gcc could not know if "the type was
originally that type".

Philip Taylor pointed me at
http://davmac.wordpress.com/2010/02/26/c99-revisited/ which has an interesting
discussion about "Does accessing an object constitute access to the containing
object"?

This bug is "fixed" on trunk by 160947, but since that is an optimization
change, it probably has just deactivated the code path that caused this
behavior.

For some context, this testcase is a reduction from:

http://hg.mozilla.org/mozilla-central/file/a351ae35f2c4/js/src/jscntxtinlines.h#l179


             reply	other threads:[~2011-09-03 18:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-03 18:50 rafael.espindola at gmail dot com [this message]
2011-09-03 18:54 ` [Bug c/50284] " rafael.espindola at gmail dot com
2011-09-03 19:08 ` rafael.espindola at gmail dot com
2011-09-03 20:53 ` rguenth at gcc dot gnu.org
2011-09-03 22:54 ` rafael.espindola at gmail dot com
2011-09-04  3:50 ` rafael.espindola at gmail dot com
2011-09-04  8:58 ` 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-50284-4@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).