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/52977] [4.8 Regression] internal compiler error: Segmentation fault with `-x c-header' or `-x cxx-header' option
Date: Mon, 16 Apr 2012 10:15:00 -0000	[thread overview]
Message-ID: <bug-52977-4-xqVbOlDqSi@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52977-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-04-16 10:15:35 UTC ---
ugh...

#0  0x00000000004d7255 in gt_pch_p_14lang_tree_node (this_obj=0x7ffff5bf64c0, 
    x_p=0x7ffff5bf64c0, op=0x8b1a27 <relocate_ptrs>, cookie=0x7fffffffdb20)
    at ./gt-c-decl.h:1448

        case TS_VECTOR:
          if ((void *)(x) == this_obj)
            op (&((*x).generic.vector.typed.type), cookie);
          {
            size_t i0;
            size_t l0 = (size_t)(TYPE_VECTOR_SUBPARTS (TREE_TYPE
((tree)&((*x).generic.vector))));
            for (i0 = 0; i0 != l0; i0++) {
              if ((void *)(x) == this_obj)
                op (&((*x).generic.vector.elts[i0]), cookie);
            }
          }
          break;

so we relocate TREE_TYPE before accessing it to find the number of elements.

Other than trying to teach gengtype to compute all required lengths before
changing pointers I only see the less efficient solution of repeating the
element count in-line :/


  parent reply	other threads:[~2012-04-16 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-13 16:08 [Bug c/52977] New: " ai.azuma at gmail dot com
2012-04-14  6:25 ` [Bug c/52977] " markus at trippelsdorf dot de
2012-04-16  8:48 ` [Bug c/52977] [4.8 Regression] " rguenth at gcc dot gnu.org
2012-04-16 10:15 ` rguenth at gcc dot gnu.org [this message]
2012-04-16 13:22 ` rguenth at gcc dot gnu.org
2012-04-17 14:42 ` rguenth at gcc dot gnu.org
2012-04-19 13:33 ` matz 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-52977-4-xqVbOlDqSi@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).