public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/13929] [3.4 Regression] Segfault in convert_nontype_argument with invalid pointer to member Date: Fri, 30 Jan 2004 12:32:00 -0000 [thread overview] Message-ID: <20040130123249.10226.qmail@sources.redhat.com> (raw) In-Reply-To: <20040130111607.13929.giovannibajo@libero.it> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-01-30 12:32 ------- I can confirm it on a mainline build from 20040118 but it is already fixed in 20040129 and 20040127. I think this is also fixed on the 3.4.0 branch but I did not test it. I almost think it was fixed by: 2004-01-26 Mark Mitchell <mark@codesourcery.com> * class.c (add_method): Just check processing_template_decl to determine whether or not we are within a template. * decl2.c (maybe_retrofit_in_chrg): Likewise. * init.c (decl_constant_value): Check the type of the declaration, not TREE_READONLY. * name-lookup.c (maybe_push_to_top_level): Rename to ... (push_to_top_level): ... this. * name-lookup.h (maybe_push_to_top_level): Do not declare it. * pt.c (push_template_decl_real): Reorder condition for speed. (convert_template_argument): Use dependency-checking functions in place of uses_template_parms. (lookup_template_class): Avoid calling uses_template_parms more than once. (uses_template_parms): Reimplement, using dependency-checking functions. (instantiate_class_template): Use push_to_top_level, not maybe_push_to_top_level. (type_unification_real): Simplify. (type_dependent_expression_p): Handle OFFSET_REFs and TEMPLATE_DECLs. (any_dependent_template_arguments_p): Handle multiple levels of template argument. * semantics.c (expand_or_defer_fn): Do not check uses_template_parms for template instantiations. * typeck.c (comptypes): Avoid calling cp_type_quals. -- What |Removed |Added ---------------------------------------------------------------------------- Summary|[3.4/3.5 Regression] |[3.4 Regression] Segfault in |Segfault in |convert_nontype_argument |convert_nontype_argument |with invalid pointer to |with invalid pointer to |member |member | Target Milestone|--- |3.4.0 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13929
next prev parent reply other threads:[~2004-01-30 12:32 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-30 11:16 [Bug c++/13929] New: [3.4/3.5 " giovannibajo at libero dot it 2004-01-30 11:16 ` [Bug c++/13929] " giovannibajo at libero dot it 2004-01-30 12:32 ` pinskia at gcc dot gnu dot org [this message] 2004-01-30 14:45 ` [Bug c++/13929] [3.4 " bangerth at dealii 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=20040130123249.10226.qmail@sources.redhat.com \ --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).