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++/52035] internal compiler error: tree code ‘template_type_parm’ is not supported in LTO streams
Date: Mon, 30 Jan 2012 09:42:00 -0000	[thread overview]
Message-ID: <bug-52035-4-RtKOUzzsNL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52035-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-30 09:34:37 UTC ---
We're writing a function decl:

 <function_decl 0x7ffff5b9b200 insert
    type <function_type 0x7ffff5b8cbd0
        type <void_type 0x7ffff5a36bd0 void type_6 VOID
            align 8 symtab 0 alias set -1 canonical type 0x7ffff5a36bd0
            pointer_to_this <pointer_type 0x7ffff5a36c78>>
        QI
        size <integer_cst 0x7ffff5a39120 constant 8>
        unit size <integer_cst 0x7ffff5a39140 constant 1>
        align 8 symtab 0 alias set -1 canonical type 0x7ffff5a54000
        arg-types <tree_list 0x7ffff5b89960 value <integer_type 0x7ffff5b8c9d8
size_type>
            chain <tree_list 0x7ffff5a289b0 value <void_type 0x7ffff5a36bd0
void>>>
        pointer_to_this <pointer_type 0x7ffff5b9c888>>
    addressable used nothrow public static weak decl_1 decl_5 decl_6 QI
defer-output file t.C line 6 col 28 align 16 context <record_type
0x7ffff5b9c348 QVector> initial <block 0x7ffff5ba00f0>
    arguments <parm_decl 0x7ffff5a267f8 n
        type <integer_type 0x7ffff5b8c9d8 size_type sizes-gimplified type_6 SI
            size <integer_cst 0x7ffff5a392e0 constant 32>
            unit size <integer_cst 0x7ffff5a39300 constant 4>
            align 32 symtab 0 alias set -1 canonical type 0x7ffff5a365e8
precision 32 min <integer_cst 0x7ffff5a39280 -2147483648> max <integer_cst
0x7ffff5a392a0 2147483647>>
        SI file t.C line 6 col 57 size <integer_cst 0x7ffff5a392e0 32> unit
size <integer_cst 0x7ffff5a39300 4>
        align 32 context <function_decl 0x7ffff5b9b200 insert>
        arg-type <integer_type 0x7ffff5b8c9d8 size_type>>
    result <result_decl 0x7ffff5b9d100 D.2212 type <void_type 0x7ffff5a36bd0
void>
        ignored VOID file t.C line 6 col 28
        align 8 context <function_decl 0x7ffff5b9b200 insert>>
    full-name "static void QVector<T>::insert(QVector<T>::size_type) [with T =
int; QVector<T>::size_type = int]"
    pending-inline-info 0x7ffff5b9e1e0 template-info 0x7ffff5b97940
    struct-function 0x7ffff5a29320>

from there its type, its argument type chain, the first arguments type-name,
its context

 <record_type 0x7ffff5b8c690 QVector type_0 type_5 type_6 VOID
    size <integer_cst 0x7ffff5a39000 type <integer_type 0x7ffff5a360a8
bitsizetype> constant 0>
    unit size <integer_cst 0x7ffff5a1dfa0 type <integer_type 0x7ffff5a36000
sizetype> constant 0>
    align 8 symtab 0 alias set -1 canonical type 0x7ffff5b8c690
    fields <type_decl 0x7ffff5b85b80 QVector
        type <record_type 0x7ffff5b8c738 QVector type_5 VOID
            align 8 symtab 0 alias set -1 canonical type 0x7ffff5b8c690
            full-name "struct QVector<T>"
            n_parents=0 use_template=0 interface-unknown
            chain <type_decl 0x7ffff5b85a10 QVector>>
        nonlocal decl_4 VOID file t.C line 1 col 38
        align 1 context <record_type 0x7ffff5b8c690 QVector> result
<record_type 0x7ffff5b8c690 QVector>

        chain <type_decl 0x7ffff5b85cf0 iterator type <pointer_type
0x7ffff5b8c888 iterator>
            nonlocal VOID file t.C line 2 col 20
            align 1 context <record_type 0x7ffff5b8c690 QVector> result
<pointer_type 0x7ffff5b8c7e0>
           >>
    full-name "struct QVector<T>"
    n_parents=0 use_template=0 interface-unknown
    pointer_to_this <pointer_type 0x7ffff5b8cdc8> chain <type_decl
0x7ffff5b85a10 QVector>>

its type fields and then one of its types:

 <pointer_type 0x7ffff5b8c888 iterator
    type <template_type_parm 0x7ffff5b8c5e8 T type_0 type_6 VOID
        align 8 symtab 0 alias set -1 canonical type 0x7ffff5b8c5e8
       index 0 level 1 orig_level 1
        pointer_to_this <pointer_type 0x7ffff5b8c7e0> chain <type_decl
0x7ffff5b85958 T>>
    unsigned DI
    size <integer_cst 0x7ffff5a1df60 type <integer_type 0x7ffff5a360a8
bitsizetype> constant 64>
    unit size <integer_cst 0x7ffff5a1df80 type <integer_type 0x7ffff5a36000
sizetype> constant 8>
    align 64 symtab 0 alias set -1 canonical type 0x7ffff5b8c7e0>

Not sure if it's a but that the DECL_CONTEXT ends up in an uninstantiated
template?


  parent reply	other threads:[~2012-01-30  9:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-29  1:31 [Bug c++/52035] New: " marbacz at gmail dot com
2012-01-29  1:34 ` [Bug c++/52035] " marbacz at gmail dot com
2012-01-29 11:12 ` pinskia at gcc dot gnu.org
2012-01-30  9:42 ` rguenth at gcc dot gnu.org [this message]
2012-02-01 23:39 ` marbacz at gmail dot com
2012-02-06 21:29 ` [Bug c++/52035] [4.7 regression] " jason at gcc dot gnu.org
2012-02-06 23:45 ` jason at gcc dot gnu.org
2012-02-08  9:53 ` jason at gcc dot gnu.org
2012-02-08 22:47 ` paolo.carlini at oracle dot com

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-52035-4-RtKOUzzsNL@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).