From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Uros Bizjak <ubizjak@gmail.com>,
"x86@kernel.org" <x86@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"sv@linux.ibm.com" <sv@linux.ibm.com>
Subject: Re: [PATCH] compiler-gcc.h: Remove ancient workaround for gcc PR 58670
Date: Thu, 25 Aug 2022 11:19:06 +0000 [thread overview]
Message-ID: <fd71c136-4c1c-5c4d-003f-20cb8c7cf17f@csgroup.eu> (raw)
In-Reply-To: <1661422971.cqtahfm22j.naveen@linux.ibm.com>
Le 25/08/2022 à 12:30, Naveen N. Rao a écrit :
> Uros Bizjak wrote:
>> The workaround for 'asm goto' miscompilation introduces a compiler
>> barrier quirk that inhibits many useful compiler optimizations. For
>> example, __try_cmpxchg_user compiles to:
>>
>> 11375: 41 8b 4d 00 mov 0x0(%r13),%ecx
>> 11379: 41 8b 02 mov (%r10),%eax
>> 1137c: f0 0f b1 0a lock cmpxchg %ecx,(%rdx)
>> 11380: 0f 94 c2 sete %dl
>> 11383: 84 d2 test %dl,%dl
>> 11385: 75 c4 jne 1134b <...>
>> 11387: 41 89 02 mov %eax,(%r10)
>>
>> where the barrier inhibits flags propagation from asm when
>> compiled with gcc-12.
>>
>> When the mentioned quirk is removed, the following code is generated:
>>
>> 11553: 41 8b 4d 00 mov 0x0(%r13),%ecx
>> 11557: 41 8b 02 mov (%r10),%eax
>> 1155a: f0 0f b1 0a lock cmpxchg %ecx,(%rdx)
>> 1155e: 74 c9 je 11529 <...>
>> 11560: 41 89 02 mov %eax,(%r10)
>>
>> The refered compiler bug:
>>
>> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58670
>>
>> was fixed for gcc-4.8.2.
>>
>> Current minimum required version of GCC is version 5.1 which has
>> the above 'asm goto' miscompilation fixed, so remove the workaround.
>>
>> Signed-off-by: Uros Bizjak <ubizjak@gmail.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
It's unlikely that asm goto bug was completely fixed in 4.8 because it's
been encountered with gcc 4.9.3 and 4.9.4, see commit 1344a232016d
("powerpc: Use asm_goto_volatile for put_user()")
Christophe
next prev parent reply other threads:[~2022-08-25 11:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:14 Uros Bizjak
2022-08-25 10:30 ` Naveen N. Rao
2022-08-25 11:19 ` Christophe Leroy [this message]
2022-08-25 11:34 ` Uros Bizjak
2022-08-25 18:08 ` Segher Boessenkool
2022-08-26 7:02 ` Christophe Leroy
2022-08-26 7:38 ` Christophe Leroy
2022-08-26 10:12 ` Christophe Leroy
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=fd71c136-4c1c-5c4d-003f-20cb8c7cf17f@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=sv@linux.ibm.com \
--cc=ubizjak@gmail.com \
--cc=x86@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®