public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/28595] [4.1/4.2 regression] ICE with invalid const static variable
Date: Sat, 26 Aug 2006 16:23:00 -0000	[thread overview]
Message-ID: <20060826162343.32370.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28595-1771@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from mmitchel at gcc dot gnu dot org  2006-08-26 16:23 -------
Subject: Bug 28595

Author: mmitchel
Date: Sat Aug 26 16:23:33 2006
New Revision: 116468

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116468
Log:
        PR c++/28588
        * class.c (resolve_address_of_overloaded_function): Add
        access_path parameter.  Perform access checks.
        (instantiate_type): Adjust call to
        resolve_address_of_overloaded_function.  Remove unnecessary code.
        * tree.c (is_overloaded_fn): Document.  Return 2 when there are
        acutally multiple functions.
        (really_overloaded_fn): Use is_overloaded_fn.
        * mangle.c (write_expression): Handle BASELINKs.
        * cp-tree.h (really_overloaded_fn): Return bool.
        (baselink_for_fns): Declare.
        * search.c (lookup_member): Check access for single static
        functions here.
        * pt.c (convert_nontype_argument_function): Handle BASELINKs.
        (tsubst_copy_and_build): Generate BASELINKs for template-ids.
        * semantics.c (finish_call_expr): Use baselink_for_fns.
        (baselink_for_fns): New function.
        (finish_id_expression): Use it.
        * parser.c (cp_parser_template_argument): Don't strip BASELINKs.
        PR c++/28595
        * pt.c (tsubst): Issue errors about attempts to create VLAs at
        template-instantiation time.
        PR c++/28588
        * g++.dg/inherit/access6.C: New test.
        * g++.dg/inherit/access7.C: Likewise.
        PR c++/28595
        * g++.dg/template/array15.C: New test.
        * g++.dg/template/crash2.C: Tweak error markers.

Added:
    trunk/gcc/testsuite/g++.dg/inherit/access6.C
    trunk/gcc/testsuite/g++.dg/inherit/access7.C
    trunk/gcc/testsuite/g++.dg/template/array15.C
Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/class.c
    trunk/gcc/cp/cp-tree.h
    trunk/gcc/cp/mangle.c
    trunk/gcc/cp/parser.c
    trunk/gcc/cp/pt.c
    trunk/gcc/cp/search.c
    trunk/gcc/cp/semantics.c
    trunk/gcc/cp/tree.c
    trunk/gcc/testsuite/ChangeLog
    trunk/gcc/testsuite/g++.dg/template/crash2.C


-- 


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


  parent reply	other threads:[~2006-08-26 16:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-04  0:55 [Bug c++/28595] New: " reichelt at gcc dot gnu dot org
2006-08-04  0:57 ` [Bug c++/28595] " reichelt at gcc dot gnu dot org
2006-08-11 22:24 ` janis at gcc dot gnu dot org
2006-08-14 19:02 ` reichelt at gcc dot gnu dot org
2006-08-20 22:27 ` mmitchel at gcc dot gnu dot org
2006-08-25 22:17 ` mmitchel at gcc dot gnu dot org
2006-08-26 16:23 ` mmitchel at gcc dot gnu dot org [this message]
2006-08-26 16:38 ` [Bug c++/28595] [4.1 " mmitchel at gcc dot gnu dot org
2006-08-26 17:14 ` mmitchel at gcc dot gnu dot org
2006-08-26 17:15 ` mmitchel at gcc dot gnu dot org
2006-08-26 17:17 ` mmitchel at gcc dot gnu dot 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=20060826162343.32370.qmail@sourceware.org \
    --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).