public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98355] [9/10/11 Regression] ICE in has_attribute, at c-family/c-attribs.c:5628
Date: Tue, 19 Jan 2021 16:33:11 +0000	[thread overview]
Message-ID: <bug-98355-4-QAwAWDdUu5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98355-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
I had stated my intent in the initial submission to complete the C++ support in
a followup patch:
https://gcc.gnu.org/pipermail/gcc-patches/2018-November/510455.html

Jason approved the initial patch with an encouragement to do so:
https://gcc.gnu.org/legacy-ml/gcc-patches/2018-10/msg01528.html

I might have gotten around to it if you and Jeff hadn't blocked for four months
(!) my fixes for a few simple ICEs in the code.  Here's the first submission of
a patch for the first ICE I found in December 2018:
https://gcc.gnu.org/pipermail/gcc-patches/2018-December/512645.html

The fixes didn't get approved and committed in r270326 until April 2019, and
many rounds of back and forth bickering over whether the built-in should accept
expressions or error out on them.

  parent reply	other threads:[~2021-01-19 16:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17 16:51 [Bug c++/98355] New: " gscfq@t-online.de
2020-12-17 17:25 ` [Bug c++/98355] " msebor at gcc dot gnu.org
2021-01-05  8:34 ` rguenth at gcc dot gnu.org
2021-01-14 11:13 ` rguenth at gcc dot gnu.org
2021-01-19 14:59 ` jakub at gcc dot gnu.org
2021-01-19 16:33 ` msebor at gcc dot gnu.org [this message]
2021-01-29  4:41 ` mpolacek at gcc dot gnu.org
2021-01-29 16:34 ` mpolacek at gcc dot gnu.org
2021-02-01 15:21 ` cvs-commit at gcc dot gnu.org
2021-02-01 15:22 ` [Bug c++/98355] [9/10 " mpolacek at gcc dot gnu.org
2021-02-01 15:23 ` cvs-commit at gcc dot gnu.org
2021-02-01 15:23 ` [Bug c++/98355] [9 " mpolacek 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-98355-4-QAwAWDdUu5@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).