public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/54038] [4.7/4.8 Regression] finalize_type_size enters infinite loop becasue TYPE_NEXT_VARIANT (variant) == variant
Date: Fri, 20 Jul 2012 11:09:00 -0000	[thread overview]
Message-ID: <bug-54038-4-vGnKG5mH7Z@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54038-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-07-20 11:08:49 UTC ---
Created attachment 27844
  --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27844
gcc48-pr54038.patch

Untested fix.  On array23.C testcase, we have Foo as main variant of Foo2 and
we have:
t: const Foo2 []
c: const Foo []
m: Foo []
and in that case we want to change c's TYPE_MAIN_VARIANT to m.  On this new
testcase we have char as TYPE_MAIN_VARIANT of gchar, and have:
t: const gchar *const []
c: const char *const []
m: const gchar * []
and trying to change TYPE_MAIN_VARIANT of c in that case (whose
TYPE_MAIN_VARIANT is const char * [] at that point) is fatal.  I believe the
important difference between the two is that in array23.C TYPE_MAIN_VARIANT
(TREE_TYPE (c)) is the same as TREE_TYPE (m) (aka TYPE_MAIN_VARIANT
(elt_type)),
but on this PR it is different and as the element type's of c vs. m + t aren't
variants of the same type, neither should the array types be variants of one
another.


  parent reply	other threads:[~2012-07-20 11:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-19 22:23 [Bug c++/54038] New: " jamborm at gcc dot gnu.org
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 [this message]
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-vGnKG5mH7Z@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).