public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/26571] [4.0/4.1 regression] Bad diagnostic using type modifier with struct Date: Thu, 07 Sep 2006 22:27:00 -0000 [thread overview] Message-ID: <20060907222722.5060.qmail@sourceware.org> (raw) In-Reply-To: <bug-26571-1771@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from jason at gcc dot gnu dot org 2006-09-07 22:27 ------- Subject: Bug 26571 Author: jason Date: Thu Sep 7 22:27:01 2006 New Revision: 116763 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=116763 Log: PR c++/26195 * decl.c (make_rtl_for_nonlocal_decl), (start_preparsed_function): Don't use lbasename on input_filename when calling get_fileinfo. * semantics.c (begin_class_definition): Likewise. * lex.c (cxx_make_type): Likewise. (handle_pragma_interface): Call get_fileinfo on input_filename, not on the parameter to the directive. PR c++/26696 * cvt.c (convert_to_void): Replace a subexpression with no side effects with void_zero_node. * tree.c (is_overloaded_fn): Look through COMPONENT_REF. (get_first_fn): Ditto. * decl.c (grokdeclarator): No need to look through COMPONENT_REF. PR c++/26571 * parser.c (cp_parser_diagnose_invalid_type_name): Handle the case where the name is a type used incorrectly. PR c++/26671 * typeck.c (maybe_warn_about_returning_address_of_local): Look through COMPONENT_REF and ARRAY_REF. PR c++/26102 * name-lookup.c (do_class_using_decl): Try to find the base even if bases_dependent_p. * pt.c (type_dependent_expression_p): A USING_DECL is dependent. PR c++/19809 * pt.c (tsubst_friend_function): Set DECL_INITIAL before pushdecl. Modified: branches/gcc-4_1-branch/gcc/cp/ChangeLog branches/gcc-4_1-branch/gcc/cp/cvt.c branches/gcc-4_1-branch/gcc/cp/decl.c branches/gcc-4_1-branch/gcc/cp/lex.c branches/gcc-4_1-branch/gcc/cp/name-lookup.c branches/gcc-4_1-branch/gcc/cp/parser.c branches/gcc-4_1-branch/gcc/cp/pt.c branches/gcc-4_1-branch/gcc/cp/semantics.c branches/gcc-4_1-branch/gcc/cp/tree.c branches/gcc-4_1-branch/gcc/cp/typeck.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26571
next prev parent reply other threads:[~2006-09-07 22:27 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-03-06 2:56 [Bug c++/26571] New: [4.0/4.1/4.2 " reichelt at gcc dot gnu dot org 2006-03-06 13:05 ` [Bug c++/26571] " pinskia at gcc dot gnu dot org 2006-03-11 3:22 ` mmitchel at gcc dot gnu dot org 2006-06-04 18:00 ` mmitchel at gcc dot gnu dot org 2006-09-06 0:12 ` jason at gcc dot gnu dot org 2006-09-06 5:28 ` jason at gcc dot gnu dot org 2006-09-07 22:27 ` jason at gcc dot gnu dot org [this message] 2006-09-07 22:38 ` [Bug c++/26571] [4.0/4.1 " jason at gcc dot gnu dot org 2006-09-07 23:04 ` jason at gcc dot gnu dot org 2006-09-07 23:07 ` jason 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=20060907222722.5060.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: linkBe 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).