From: Paolo Carlini <paolo.carlini@oracle.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Jason Merrill <jason@redhat.com>
Subject: [C++ Patch] PR 64644 (""warning: anonymous union with no members" should be an error with -pedantic-errors")
Date: Fri, 16 Jun 2017 13:47:00 -0000 [thread overview]
Message-ID: <6eeb9ea6-4b55-99be-06d4-aa141df2f9f2@oracle.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 425 bytes --]
Hi,
submitter and Manuel analyzed this a while ago and came to the
conclusion - which I think is still valid vs the current working draft -
that strictly speaking this kind of code violates [dcl.dcl], thus a
pedwarn seems more suited than a plain warning. The below one-liner,
suggested by Manuel at the time, passes testing on x86_64-linux together
with my testsuite changes.
Thanks,
Paolo.
//////////////////////
[-- Attachment #2: CL_64644 --]
[-- Type: text/plain, Size: 465 bytes --]
/cp
2017-06-16 Manuel Lopez-Ibanez <manu@gcc.gnu.org>
Paolo Carlini <paolo.carlini@oracle.com>
PR c++/64644
* decl2.c (finish_anon_union): Complain about "anonymous union with
no members" with a pedwarn.
/testsuite
2017-06-16 Manuel Lopez-Ibanez <manu@gcc.gnu.org>
Paolo Carlini <paolo.carlini@oracle.com>
PR c++/64644
* g++.dg/other/anon-union4.C: New.
* g++.old-deja/g++.law/union4.C: Adjust.
* g++.old-deja/g++.other/anon1.C: Likewise.
[-- Attachment #3: patch_64644 --]
[-- Type: text/plain, Size: 1533 bytes --]
Index: cp/decl2.c
===================================================================
--- cp/decl2.c (revision 249233)
+++ cp/decl2.c (working copy)
@@ -1559,7 +1559,7 @@ finish_anon_union (tree anon_union_decl)
return;
if (main_decl == NULL_TREE)
{
- warning (0, "anonymous union with no members");
+ pedwarn (input_location, 0, "anonymous union with no members");
return;
}
Index: testsuite/g++.dg/other/anon-union4.C
===================================================================
--- testsuite/g++.dg/other/anon-union4.C (revision 0)
+++ testsuite/g++.dg/other/anon-union4.C (working copy)
@@ -0,0 +1,3 @@
+// PR c++/64644
+
+static union { }; // { dg-error "anonymous union with no members" }
Index: testsuite/g++.old-deja/g++.law/union4.C
===================================================================
--- testsuite/g++.old-deja/g++.law/union4.C (revision 249233)
+++ testsuite/g++.old-deja/g++.law/union4.C (working copy)
@@ -10,4 +10,4 @@ static union {
struct SS {
int ss;
};
-};// { dg-warning "no members" }
+};// { dg-error "no members" }
Index: testsuite/g++.old-deja/g++.other/anon1.C
===================================================================
--- testsuite/g++.old-deja/g++.other/anon1.C (revision 249233)
+++ testsuite/g++.old-deja/g++.other/anon1.C (working copy)
@@ -3,4 +3,4 @@
static union {
union {
};
-}; // { dg-warning "" } anonymous union with no members
+}; // { dg-error "" } anonymous union with no members
next reply other threads:[~2017-06-16 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 13:47 Paolo Carlini [this message]
2017-07-10 14:40 ` Paolo Carlini
2017-09-15 9:53 ` [C++ Patch Ping] " Paolo Carlini
2017-09-15 15:59 ` Nathan Sidwell
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=6eeb9ea6-4b55-99be-06d4-aa141df2f9f2@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
/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).