public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/99363] [10,11 regression] gcc.dg/attr-flatten-1.c fails starting with r11-7469
Date: Thu, 18 Mar 2021 11:14:42 +0000 [thread overview]
Message-ID: <bug-99363-4-kHJtc6l0kJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99363-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99363
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Eric Botcazou
<ebotcazou@gcc.gnu.org>:
https://gcc.gnu.org/g:a98cb0f1065de3227a91b6597d62d157f8640323
commit r10-9454-ga98cb0f1065de3227a91b6597d62d157f8640323
Author: Jason Merrill <jason@redhat.com>
Date: Fri Mar 5 17:07:25 2021 -0500
testsuite: Update testcase for PR96078 fix [PR99363]
My fix for PR96078 made us stop warning about flatten on an alias if the
target has the alias, which is exactly the case tested here. So let's
remove the expected warning and add a similar case which does warn.
gcc/testsuite/ChangeLog:
PR c/99363
* gcc.dg/attr-flatten-1.c: Adjust.
next prev parent reply other threads:[~2021-03-18 11:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 16:40 [Bug other/99363] New: [11 " seurer at gcc dot gnu.org
2021-03-03 17:15 ` [Bug other/99363] " hp at gcc dot gnu.org
2021-03-04 8:27 ` [Bug c/99363] " rguenth at gcc dot gnu.org
2021-03-05 22:16 ` cvs-commit at gcc dot gnu.org
2021-03-05 23:12 ` jakub at gcc dot gnu.org
2021-03-15 23:01 ` [Bug c/99363] [10,11 " aoliva at gcc dot gnu.org
2021-03-18 11:14 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-04-27 14:57 ` hp at gcc dot gnu.org
2021-04-27 15:18 ` 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-99363-4-kHJtc6l0kJ@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).