public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54038] New: finalize_type_size enters infinite loop becasue TYPE_NEXT_VARIANT (variant) == variant
Date: Thu, 19 Jul 2012 22:23:00 -0000	[thread overview]
Message-ID: <bug-54038-4@http.gcc.gnu.org/bugzilla/> (raw)

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

             Bug #: 54038
           Summary: finalize_type_size enters infinite loop becasue
                    TYPE_NEXT_VARIANT (variant) == variant
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: jamborm@gcc.gnu.org
              Host: x86_64-linux-gnu
            Target: x86_64-linux-gnu


Created attachment 27837
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27837
Delta reduced testcase

When compiling the attached testcase, which is delta-reduced from
Mozilla Firefox, gcc ends up in an endless loop at the end of
finalize_type_size in stor-layout.c because TYPE_NEXT_VARIANT
(variant) is variant itself.

This value is assigned to it in function build_cplus_array_type in
cp/tree.c (near line 811).

I compile the testcase with the following flags, no optimization is
required:

g++ -S -fpermissive -std=gnu++0x zzz.i

I'm currently on revision 189631.  I'll try to do some bisecting
tomorrow.


             reply	other threads:[~2012-07-19 22:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 22:23 jamborm at gcc dot gnu.org [this message]
2012-07-19 23:07 ` [Bug c++/54038] " markus at trippelsdorf dot de
2012-07-20  6:16 ` markus at trippelsdorf dot de
2012-07-20  8:55 ` [Bug c++/54038] [4.7/4.8 Regression] " rguenth at gcc dot gnu.org
2012-07-20 11:09 ` jakub at gcc dot gnu.org
2012-07-20 11:33 ` rguenth at gcc dot gnu.org
2012-07-20 11:48 ` jakub at gcc dot gnu.org
2012-07-20 16:12 ` jason at gcc dot gnu.org
2012-07-20 16:12 ` jason at gcc dot gnu.org
2012-07-20 16:13 ` jason at gcc dot gnu.org
2012-07-20 17:44 ` jason 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-54038-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).