From: Joseph Myers <joseph@codesourcery.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>, Pedro Alves <pedro@palves.net>
Subject: Re: [PATCH v3] c: Implement new -Wenum-int-mismatch warning [PR105131]
Date: Wed, 18 May 2022 22:25:49 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2205182225220.10499@digraph.polyomino.org.uk> (raw)
In-Reply-To: <YoVqYULniXPTRxO5@redhat.com>
On Wed, 18 May 2022, Marek Polacek via Gcc-patches wrote:
> I've extended the tests to use an enum with __attribute__ ((__packed__)) to
> test the case when the underlying type is (un)signed char. But it seems like
> we can't have underlying types wider than int. I've also included two tests
> which #include the two main tests. Seems like Dejagnu doesn't expect the
> diagnostics as per the dg directives in the main tests, which is good.
>
> Is the following ok?
OK.
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2022-05-18 22:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 23:56 [PATCH] " Marek Polacek
2022-05-18 10:14 ` Pedro Alves
2022-05-18 14:48 ` [PATCH v2] " Marek Polacek
2022-05-18 20:58 ` Joseph Myers
2022-05-18 21:51 ` [PATCH v3] " Marek Polacek
2022-05-18 22:25 ` Joseph Myers [this message]
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=alpine.DEB.2.22.394.2205182225220.10499@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pedro@palves.net \
--cc=polacek@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).