public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59956] internal compiler error: unexpected expression ‘P_S’ of kind template_parm_index
Date: Mon, 27 Jan 2014 13:17:00 -0000	[thread overview]
Message-ID: <bug-59956-4-0hkDW86M1T@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59956-4@http.gcc.gnu.org/bugzilla/>

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

Markus Trippelsdorf <trippels at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-01-27
                 CC|                            |trippels at gcc dot gnu.org
   Target Milestone|---                         |4.8.3
     Ever confirmed|0                           |1
      Known to fail|                            |4.8.3, 4.9.0

--- Comment #1 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
Confirmed.

markus@x4 tmp % cat test.ii
template <int> struct A;
template <int> class B {
  template <int A_S> friend void A<A_S>::impl();
};
B<0> a;

markus@x4 tmp % g++ test.ii
test.ii: In instantiation of ‘class B<0>’:
test.ii:5:6:   required from here
test.ii:3:34: internal compiler error: unexpected expression ‘A_S’ of kind
template_parm_index
   template <int A_S> friend void A<A_S>::impl();
                                  ^
0x6e2af5 cxx_eval_constant_expression
        ../../gcc/gcc/cp/semantics.c:9784
0x6e5875 cxx_eval_outermost_constant_expr
        ../../gcc/gcc/cp/semantics.c:9804
0x6e854b maybe_constant_value(tree_node*)
        ../../gcc/gcc/cp/semantics.c:9914
0x5c6512 convert_nontype_argument
        ../../gcc/gcc/cp/pt.c:5671
0x5c6512 convert_template_argument
        ../../gcc/gcc/cp/pt.c:6477
0x5be4a0 coerce_template_parms
        ../../gcc/gcc/cp/pt.c:6851
0x5c8369 lookup_template_class_1
        ../../gcc/gcc/cp/pt.c:7422
0x5c8369 lookup_template_class(tree_node*, tree_node*, tree_node*, tree_node*,
int, int)
        ../../gcc/gcc/cp/pt.c:7720
0x5cdb73 tsubst_aggr_type
        ../../gcc/gcc/cp/pt.c:10023
0x5d2705 tsubst_decl
        ../../gcc/gcc/cp/pt.c:10401
0x5c025f tsubst(tree_node*, tree_node*, int, tree_node*)
        ../../gcc/gcc/cp/pt.c:11349
0x5eed53 tsubst_friend_function
        ../../gcc/gcc/cp/pt.c:8211
0x5eed53 instantiate_class_template_1
        ../../gcc/gcc/cp/pt.c:9176
0x5eed53 instantiate_class_template(tree_node*)
        ../../gcc/gcc/cp/pt.c:9262
0x680473 complete_type(tree_node*)
        ../../gcc/gcc/cp/typeck.c:134
0x569418 start_decl_1(tree_node*, bool)
        ../../gcc/gcc/cp/decl.c:4719
0x5922c7 start_decl(cp_declarator const*, cp_decl_specifier_seq*, int,
tree_node*, tree_node*, tree_node**)
        ../../gcc/gcc/cp/decl.c:4682
0x66c6fe cp_parser_init_declarator
        ../../gcc/gcc/cp/parser.c:16710
0x66e189 cp_parser_simple_declaration
        ../../gcc/gcc/cp/parser.c:11217
0x651463 cp_parser_block_declaration
        ../../gcc/gcc/cp/parser.c:11098
Please submit a full bug report,
>From gcc-bugs-return-441612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 27 13:23:45 2014
Return-Path: <gcc-bugs-return-441612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13949 invoked by alias); 27 Jan 2014 13:23:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13835 invoked by uid 48); 27 Jan 2014 13:23:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59733] [4.9 Regression] bootstrap-asan failed to bootstrap
Date: Mon, 27 Jan 2014 13:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: kcc at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59733-4-ZjYrITcJI2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-01/txt/msg02754.txt.bz2
Content-length: 1246

http://gcc.gnu.org/bugzilla/show_bug.cgi?idY733

--- Comment #26 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Kostya Serebryany from comment #25)
> Even with this workaround asan is almost unusable with the buggy kernel.
> I suspect that when a process has too many mappings it gets too slow.
> The machine where we have our clang-asan bootstrap gets very slow and
> unreliable.
>
> We have reverted the kernel on that bot
> (http://lab.llvm.org:8011/builders/sanitizer-x86_64-linux-bootstrap/)
> and reverted the above workaround in llvm trunk.
> http://llvm.org/viewvc/llvm-project?rev 0217&view=rev
>
> The kernel fix went into Linus's tree for 3.14 last week,
> and was tagged for stable backport. Nothing else we could do here.

Yeah, except perhaps putting your #c24 testcase into the kernel bug as comment
for others to have quicker test than gimp, and perhaps filing bugs in distro
bugzillas to have this fixed there quicker, best mentioning that testcase.
Though, for a portable testcase that:
  char *p = (char*)0x600000000000;
is clearly undesirable, you probably just want to mmap with NULL base address,
perhaps with PROT_NONE, a .5GB region, then munmap it and use the result as p
(if that hasn't failed).


  reply	other threads:[~2014-01-27 13:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-27 12:58 [Bug c++/59956] New: " chretien at lirmm dot fr
2014-01-27 13:17 ` trippels at gcc dot gnu.org [this message]
2014-01-27 19:31 ` [Bug c++/59956] " trippels at gcc dot gnu.org
2014-01-28 15:53 ` trippels at gcc dot gnu.org
2014-01-29 16:52 ` jason at gcc dot gnu.org
2014-01-29 20:34 ` [Bug c++/59956] [4.8/4.9 regression] " jason at gcc dot gnu.org
2014-01-29 20:45 ` jason at gcc dot gnu.org
2014-01-29 21:29 ` [Bug c++/59956] [4.8 " jason at gcc dot gnu.org
2014-05-22  9:05 ` rguenth at gcc dot gnu.org
2014-08-01 18:34 ` jason at gcc dot gnu.org
2014-08-01 18:35 ` 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-59956-4-0hkDW86M1T@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).