public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "s dot bosscher at student dot tudelft dot nl" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/11503] [3.3/3.4 Regression] segfault when instantiating template with ADDR_EXPR Date: Sat, 12 Jul 2003 14:12:00 -0000 [thread overview] Message-ID: <20030712141226.32552.qmail@sources.redhat.com> (raw) In-Reply-To: <20030711191311.11503.zlomek@gcc.gnu.org> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11503 ------- Additional Comments From s dot bosscher at student dot tudelft dot nl 2003-07-12 14:12 ------- Subject: [3.3/3.4 regression] segfault when instantiating template with ADDR_EXPR The only patches that went onto both the branch and the trunk between 2003-06-25 and 2003-06-26 are: 2003-06-26 Mark Mitchell <mark@codesourcery.com> PR c++/11332 * typeck.c (build_static_cast): Avoid returning expressions with reference type. and 2003-06-25 Mark Mitchell <mark@codesourcery.com> PR c++/10990 * search.c (lookup_base_r): Rely on accessible_p, rather than trying to emulate that logic here. PR c++/10931 * call.c (convert_like): Pass issue_conversion_warnings. (convert_like_with_context): Likewise. (convert_like_real): Add issue_conversion_warnings parameter. (perform_direct_initialization_if_possible): New function. * cp-tree.h (perform_direct_initialization_if_possible): Declare it. * typeck.c (check_for_casting_away_constness): New function. (build_static_cast): Rewrite. Looking at the backtrace, the patch most likely causing this problem is the search.c change. Mark, OK to assign this one to you?
next prev parent reply other threads:[~2003-07-12 14:12 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-11 19:13 [Bug c++/11503] New: " zlomek at gcc dot gnu dot org 2003-07-11 19:14 ` [Bug c++/11503] " zlomek at gcc dot gnu dot org 2003-07-11 19:19 ` [Bug c++/11503] [3.3/3.4 Regression] " pinskia at physics dot uc dot edu 2003-07-11 19:23 ` pinskia at physics dot uc dot edu 2003-07-11 19:24 ` pinskia at physics dot uc dot edu 2003-07-11 20:44 ` bangerth at dealii dot org 2003-07-12 14:12 ` s dot bosscher at student dot tudelft dot nl [this message] 2003-07-14 5:13 ` cvs-commit at gcc dot gnu dot org 2003-07-14 5:18 ` cvs-commit at gcc dot gnu dot org 2003-07-14 5:20 ` cvs-commit at gcc dot gnu dot org 2003-07-14 5:21 ` 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=20030712141226.32552.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).