From: "Arnd Bergmann" <arnd@arndb.de>
To: "Tejun Heo" <tj@kernel.org>
Cc: "Arnd Bergmann" <arnd@kernel.org>,
"Lai Jiangshan" <jiangshanlai@gmail.com>,
"Richard Clark" <richard.xnu.clark@gmail.com>,
"Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Andrey Grodzovsky" <andrey.grodzovsky@amd.com>,
"Tetsuo Handa" <penguin-kernel@i-love.sakura.ne.jp>,
"linux-kernel@vger.kernel.org," <linux-kernel@vger.kernel.org>,
"David Laight" <David.Laight@aculab.com>
Subject: Re: [PATCH] workqueue: fix enum type for gcc-13
Date: Wed, 18 Jan 2023 21:32:45 +0100 [thread overview]
Message-ID: <a1d48420-862e-47e6-9435-462e23bb6be3@app.fastmail.com> (raw)
In-Reply-To: <Y8ggiF+7k0rViXcY@slm.duckdns.org>
On Wed, Jan 18, 2023, at 17:38, Tejun Heo wrote:
>> From: Arnd Bergmann
>> > Sent: 17 January 2023 16:41
>> >
>> > In gcc-13, the WORK_STRUCT_WQ_DATA_MASK constant is a signed 64-bit
>> > type on 32-bit architectures because the enum definition has both
>> > negative numbers and numbers above LONG_MAX in it:
>> >
>> ...
>> > /* convenience constants */
>> > WORK_STRUCT_FLAG_MASK = (1UL << WORK_STRUCT_FLAG_BITS) - 1,
>> > - WORK_STRUCT_WQ_DATA_MASK = ~WORK_STRUCT_FLAG_MASK,
>> > + WORK_STRUCT_WQ_DATA_MASK = (unsigned long)~WORK_STRUCT_FLAG_MASK,
>> > WORK_STRUCT_NO_POOL = (unsigned long)WORK_OFFQ_POOL_NONE << WORK_OFFQ_POOL_SHIFT,
>
> I have a hard time understanding why gcc would change its behavior so that
> there's no way to compile the same code in a consistent manner across two
> adjacent compiler versions. The new behavior is fine but it makes no sense
> to introduce it like this. If at all possible, marking gcc13 broken sounds
> about right to me.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107405 has some more
information on the change. In short, the old behavior was a gcc
extension that was somewhat surprising and not well documented,
while the new behavior is consistent with C23 and C++ as well
as easier to understand: Any constant that is defined as part of
an enum now has the same type as the enum itself, even if it fits
within a shorter type. In a definition like
enum e {
A = -1,
B = -1u,
};
the enum type has to be compatible with 'long long' because
anything shorter would not fit both -1 and -1u (UINT_MAX).
A and B were both signed types to match the signedness of the
enum type, but A was actually a 32-bit integer since that is
sufficient, while B was also a 64-bit type since it exceeds
INT_MAX. Now they are both the same type.
I don't think there is a chance they will revert to the old behavior,
though we could try asking for an command line flag to warn about
cases where this changes code generation.
Arnd
next prev parent reply other threads:[~2023-01-18 20:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 16:40 Arnd Bergmann
2023-01-18 9:31 ` David Laight
2023-01-18 16:38 ` Tejun Heo
2023-01-18 20:32 ` Arnd Bergmann [this message]
2023-01-19 1:41 ` Tejun Heo
2023-01-19 9:21 ` David Laight
2023-05-08 15:23 ` Thierry Reding
2023-05-09 3:26 ` Lai Jiangshan
2023-05-21 2:40 ` Tejun Heo
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=a1d48420-862e-47e6-9435-462e23bb6be3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=David.Laight@aculab.com \
--cc=andrey.grodzovsky@amd.com \
--cc=arnd@kernel.org \
--cc=j.neuschaefer@gmx.net \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=richard.xnu.clark@gmail.com \
--cc=tj@kernel.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
all inboxes | Powered by JetHome®