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 c++/22488] C++ frontend generates RECORD_TYPEs with overlapping FIELD_DECLs
Date: Tue, 02 Apr 2013 08:04:00 -0000	[thread overview]
Message-ID: <bug-22488-4-mcMjr8pDu0@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-22488-4@http.gcc.gnu.org/bugzilla/>


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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.6.4                       |---
            Summary|[4.6/4.7/4.8/4.9            |C++ frontend generates
                   |Regression]                 |RECORD_TYPEs with
                   |push_fields_onto_fieldstack |overlapping FIELD_DECLs
                   |calculates offset           |
                   |incorrectly                 |

--- Comment #57 from Richard Biener <rguenth at gcc dot gnu.org> 2013-04-02 08:04:05 UTC ---
Re-confirmed and summary adjusted.  The code in tree-ssa-structalias.c is
still there:

      /* We can't sort them if we have a field with a variable sized type,
         which will make notokay = true.  In that case, we are going to return
         without creating varinfos for the fields anyway, so sorting them is a
         waste to boot.  */
      if (!notokay)
        {
          sort_fieldstack (fieldstack);
          /* Due to some C++ FE issues, like PR 22488, we might end up
             what appear to be overlapping fields even though they,
             in reality, do not overlap.  Until the C++ FE is fixed,
             we will simply disable field-sensitivity for these cases.  */
          notokay = check_for_overlaps (fieldstack);

I am not aware of other code in the middle-end that might be confused
about this issue (well, SRA maybe, but it handles overlaps well as it
also handles accesses to unions).

I believe that the C++ frontend issue might not be a regression after all,
the tree-ssa-structalias.c "regression" was fixed by the above kludge.

The C++ frontend issue makes it impossible to implement a GENERIC verifier
for RECORD_TYPEs (verify FIELD_DECLs are sorted after offset and not
overlapping).


  parent reply	other threads:[~2013-04-02  8:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-22488-4@http.gcc.gnu.org/bugzilla/>
2010-10-01 12:03 ` [Bug c++/22488] [4.3/4.4/4.5/4.6 Regression] push_fields_onto_fieldstack calculates offset incorrectly jakub at gcc dot gnu.org
2011-04-16 10:46 ` [Bug c++/22488] [4.3/4.4/4.5/4.6/4.7 " jakub at gcc dot gnu.org
2012-03-13 13:34 ` [Bug c++/22488] [4.5/4.6/4.7/4.8 " jakub at gcc dot gnu.org
2012-07-02 13:28 ` [Bug c++/22488] [4.6/4.7/4.8 " rguenth at gcc dot gnu.org
2012-11-09 22:37 ` steven at gcc dot gnu.org
2013-03-30  0:30 ` [Bug c++/22488] [4.6/4.7/4.8/4.9 " jason at gcc dot gnu.org
2013-04-02  8:04 ` rguenth at gcc dot gnu.org [this message]
2013-04-02 14:37 ` [Bug c++/22488] C++ frontend generates RECORD_TYPEs with overlapping FIELD_DECLs ebotcazou 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-22488-4-mcMjr8pDu0@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).