[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHmME9o3BDe+s2QaT4X8jg+9cc9A-3iHWnL0WnFyqKcGuhahXQ@mail.gmail.com>
Date: Thu, 3 Nov 2022 13:47:14 +0100
From: "Jason A. Donenfeld" <Jason@...c4.com>
To: Julia Lawall <julia.lawall@...ia.fr>
Cc: Kees Cook <keescook@...omium.org>, cocci@...ia.fr,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexey Dobriyan <adobriyan@...il.com>,
akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
mm-commits@...r.kernel.org, masahiroy@...nel.org,
gregkh@...uxfoundation.org, andriy.shevchenko@...ux.intel.com,
Stephen Rothwell <sfr@...b.auug.org.au>
Subject: Re: [cocci] [PATCH -mm] -funsigned-char, x86: make struct
p4_event_bind::cntr signed array
Hi Julia,
On Thu, Nov 3, 2022 at 1:45 PM Julia Lawall <julia.lawall@...ia.fr> wrote:
> It should work now.
Thanks!
> However, without disable optional_qualifier, char is
> still matching signed char. If you think that should be changed, I can do
> that.
Does `optional_qualifier` disable other things that might be
interesting to have? If so, maybe this is less than ideal? If not,
maybe it doesn't matter?
Though, for what it's worth, gcc treats `char` as a separate type,
even when using `-funsigned-char` or `-fsigned-char`.
Jason
Powered by blists - more mailing lists