public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94346] New: [9/10 Regression] ICE due to handle_copy_attribute since r9-3982
Date: Thu, 26 Mar 2020 19:02:41 +0000	[thread overview]
Message-ID: <bug-94346-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 94346
           Summary: [9/10 Regression] ICE due to handle_copy_attribute
                    since r9-3982
           Product: gcc
           Version: 10.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: jakub at gcc dot gnu.org
  Target Milestone: ---

#define ATTR(...) __attribute__ ((__VA_ARGS__))

typedef struct ATTR (packed) A { ATTR (packed) unsigned bf: 1; } A;
int bar (void);

struct C
{
  ATTR (copy ((bar (), ((struct A *)(0))[0]))) int m;
};

ICEs since r9-3982-g79a2c4281c7dcaa6a138d24fd037c62453a12bde (before that it
has been accepted with a warning).

             reply	other threads:[~2020-03-26 19:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-26 19:02 jakub at gcc dot gnu.org [this message]
2020-03-26 19:03 ` [Bug c++/94346] " jakub at gcc dot gnu.org
2020-03-26 20:13 ` msebor at gcc dot gnu.org
2020-03-26 20:17 ` msebor at gcc dot gnu.org
2020-03-26 20:25 ` jakub at gcc dot gnu.org
2020-03-27  1:56 ` msebor at gcc dot gnu.org
2020-03-27 20:35 ` cvs-commit at gcc dot gnu.org
2020-03-27 20:42 ` [Bug c++/94346] [9 " msebor at gcc dot gnu.org
2021-06-01  8:17 ` rguenth at gcc dot gnu.org
2022-03-17 19:54 ` msebor at gcc dot gnu.org
2022-05-27  8:49 ` rguenth 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-94346-4@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).