public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: optimization/8913: [3.3 regression] ICE in simplify_gen_subreg, at simplify-rtx.c Date: Thu, 12 Dec 2002 17:06:00 -0000 [thread overview] Message-ID: <20021213010600.19050.qmail@sources.redhat.com> (raw) The following reply was made to PR optimization/8913; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: rassahah@cs.tu-berlin.de, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: optimization/8913: [3.3 regression] ICE in simplify_gen_subreg, at simplify-rtx.c Date: Thu, 12 Dec 2002 17:03:09 -0800 The regression reported in PR c++/8913 showed up starting with this patch, which might merely uncover an existing problem: gcc: >2002-12-04 Jason Merrill <jason@redhat.com> > > PR c++/8461, c++/8625 > * integrate.c (copy_decl_for_inlining): Handle explicit invisible > references. > * tree-inline.c (initialize_inlined_parameters): Likewise. > > * tree.c (variably_modified_type_p): Just return an error_mark_node. gcc/cp: >2002-12-03 Jason Merrill <jason@redhat.com> > > PR c++/8461, c++/8625 > * call.c (convert_for_arg_passing): Don't mess with error_mark_node. > (cp_convert_parm_for_inlining): Remove. > * cp-lang.c (LANG_HOOKS_TREE_INLINING_CONVERT_PARM_FOR_INLINING): > Remove. > * cp-tree.h (ADDR_IS_INVISIREF): Remove. > * except.c (stabilize_throw_expr): Remove ADDR_IS_INVISIREF code. Wolfgang narrowed the window to a two-week period, and I'm working on a script to automate the search for a regression down to the hour when it was introduced. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=8913
next reply other threads:[~2002-12-13 1:06 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-12 17:06 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-24 20:04 steven 2003-01-11 16:46 Craig Rodrigues 2002-12-12 7:09 bangerth
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=20021213010600.19050.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).