From: David Lamparter <equinox@diac24.net>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c: don't drop typedef information in casts
Date: Wed, 10 Mar 2021 02:46:19 +0100 [thread overview]
Message-ID: <YEgk6zSxrau9WZ6k@eidolon.nox.tf> (raw)
In-Reply-To: <20210310012815.3797974-1-equinox@diac24.net>
On Wed, Mar 10, 2021 at 02:28:15AM +0100, David Lamparter wrote:
> The TYPE_MAIN_VARIANT() here was, for casts to a typedef'd type name,
> resulting in all information about the typedef's involvement getting
> lost. This drops necessary information for warnings and can make them
> confusing or even misleading. It also makes specialized warnings for
> unspecified-size system types (pid_t, uid_t, ...) impossible.
I hope I didn't produce any glaring SNAFUs in submitting this patch, I
haven't previously contributed to GCC.
I've run the testsuite on x86_64 and seen no breakage from this. The
delta (compared to this run:
https://gcc.gnu.org/pipermail/gcc-testresults/2021-March/662078.html) is:
$ diff -U0 /tmp/before.sum /tmp/after.sum
--- /tmp/before.sum 2021-03-09 22:48:26.989146223 +0100
+++ /tmp/after.sum 2021-03-10 01:46:46.209935875 +0100
@@ -89 +89,2 @@
-FAIL: g++.old-deja/g++.other/virtual2.C -std=c++2a execution test
+FAIL: g++.dg/modules/xtreme-header-5_c.C -std=c++17 (internal compiler error)
+FAIL: g++.dg/modules/xtreme-header-5_c.C -std=c++17 (test for excess errors)
None of which seems to be related to the patch. (The 2 new fails are
"xtreme-header-5_c.C:3:30: internal compiler error: same canonical type node for different types 'void' and 'std::__void_t<typename _Func::is_transparent>'")
Cheers,
David
next prev parent reply other threads:[~2021-03-10 1:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 1:28 David Lamparter
2021-03-10 1:46 ` David Lamparter [this message]
2021-03-10 17:01 ` Martin Sebor
2021-03-10 19:02 ` David Lamparter
2021-03-10 19:06 ` David Lamparter
2021-03-12 3:08 ` [PATCH v2] " David Lamparter
2021-03-12 8:35 ` Jakub Jelinek
2021-03-15 18:14 ` David Lamparter
2021-03-15 18:16 ` [PATCH v3] " David Lamparter
2021-05-07 16:09 [PATCH] " David Lamparter
2021-05-18 11:13 ` David Lamparter
2021-05-18 20:32 ` Joseph Myers
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=YEgk6zSxrau9WZ6k@eidolon.nox.tf \
--to=equinox@diac24.net \
--cc=gcc-patches@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).