public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98744] [11 Regression] ICE in gimple_call_arg, at gimple.h:3246 since r11-6735-g424deca72b63e644
Date: Fri, 22 Jan 2021 17:00:48 +0000	[thread overview]
Message-ID: <bug-98744-4-OvqvwOw5al@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98744-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98744

--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #7)
> looks strange, isn't DECL_HAS_IN_CHARGE_PARM_P (fn) false on all
> base constructors (as those are the abstract ctors with the in_charge
> parameter removed and implied to be false)?
> I would have expected
>   if (!fn || DECL_HAS_VTT_PARM_P (fn))
> instead

Yes, that's the bug, thanks.

> But even elide4.C seems to suffer from this bug

With the bug fixed, elide4.C doesn't elide, and that's OK.

  parent reply	other threads:[~2021-01-22 17:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-19 10:38 [Bug ipa/98744] New: " marxin at gcc dot gnu.org
2021-01-19 10:39 ` [Bug ipa/98744] " marxin at gcc dot gnu.org
2021-01-19 10:42 ` rguenth at gcc dot gnu.org
2021-01-20 16:58 ` jamborm at gcc dot gnu.org
2021-01-20 17:25 ` [Bug c++/98744] " jamborm at gcc dot gnu.org
2021-01-20 20:24 ` msebor at gcc dot gnu.org
2021-01-21  8:32 ` marxin at gcc dot gnu.org
2021-01-21 10:45 ` jakub at gcc dot gnu.org
2021-01-22  9:41 ` jakub at gcc dot gnu.org
2021-01-22 16:48 ` jason at gcc dot gnu.org
2021-01-22 17:00 ` jason at gcc dot gnu.org [this message]
2021-01-22 18:09 ` cvs-commit at gcc dot gnu.org
2021-01-22 18:09 ` jason at gcc dot gnu.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=bug-98744-4-OvqvwOw5al@http.gcc.gnu.org/bugzilla/ \
    --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).