mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Segher Boessenkool <segher@kernel.crashing.org>,
	"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
	Uros Bizjak <ubizjak@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"sv@linux.ibm.com" <sv@linux.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH] compiler-gcc.h: Remove ancient workaround for gcc PR 58670
Date: Fri, 26 Aug 2022 07:38:41 +0000	[thread overview]
Message-ID: <a5f0e388-0de4-be04-43eb-5df5108ee984@csgroup.eu> (raw)
In-Reply-To: <807f6788-436f-33d5-0c60-cc9aa9b42a0c@csgroup.eu>



Le 26/08/2022 à 09:02, Christophe Leroy a écrit :
> 
> 
> Le 25/08/2022 à 20:08, Segher Boessenkool a écrit :
>> Hi!
>>
>> On Thu, Aug 25, 2022 at 04:00:52PM +0530, Naveen N. Rao wrote:
>>> This is causing a build issue on ppc64le with a new patch replacing use
>>> of unreachable() with __builtin_unreachable() in __WARN_FLAGS():
>>> https://lore.kernel.org/linuxppc-dev/20220808114908.240813-2-sv@linux.ibm.com/
>>
>> What is the compiler version?  If this is a GCC version that is still
>> supported, could you please open a PR?  <https://gcc.gnu.org/bugs.html>
>>
>>> during RTL pass: combine
>>> In file included from /linux/kernel/locking/rtmutex_api.c:9:
>>> /linux/kernel/locking/rtmutex.c: In function
>>> '__rt_mutex_slowlock.constprop':
>>> /linux/kernel/locking/rtmutex.c:1612:1: internal compiler error: in
>>> purge_dead_edges, at cfgrtl.c:3369
>>> 1612 | }
>>>        | ^
>>> 0x142817c internal_error(char const*, ...)
>>> 	???:0
>>> 0x5c8a1b fancy_abort(char const*, int, char const*)
>>> 	???:0
>>> 0x72017f purge_all_dead_edges()
>>> 	???:0
>>> Please submit a full bug report,
>>> with preprocessed source if appropriate.
>>> Please include the complete backtrace with any bug report.
>>> See <file:///usr/share/doc/gcc-11/README.Bugs> for instructions.
>>
>> (For some reason your compiler does not show compiler source code file
>> names or line numbers.)
>>
>> So it is GCC 11...  is it 11.3?  If not, please try with that.
> 
> With gcc 11.3 I get:
> 
>     CC      kernel/locking/rtmutex_api.o
> during RTL pass: combine
> In file included from kernel/locking/rtmutex_api.c:9:
> kernel/locking/rtmutex.c: In function '__rt_mutex_slowlock.constprop':
> kernel/locking/rtmutex.c:1612:1: internal compiler error: in
> purge_dead_edges, at cfgrtl.c:3369
>    1612 | }
>         | ^
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <https://gcc.gnu.org/bugs/> for instructions.
> make[2]: *** [scripts/Makefile.build:249 : kernel/locking/rtmutex_api.o]
> Erreur 1
> make[1]: *** [scripts/Makefile.build:465 : kernel/locking] Erreur 2
> make: *** [Makefile:1857 : kernel] Erreur 2
> 
> 
> With gcc 12.2 I get:
> 
>     CC      kernel/locking/rtmutex_api.o
> during RTL pass: combine
> In file included from kernel/locking/rtmutex_api.c:9:
> kernel/locking/rtmutex.c: In function '__rt_mutex_slowlock.constprop':
> kernel/locking/rtmutex.c:1612:1: internal compiler error: in
> purge_dead_edges, at cfgrtl.cc:3347
>    1612 | }
>         | ^
> Please submit a full bug report, with preprocessed source (by using
> -freport-bug).
> See <https://gcc.gnu.org/bugs/> for instructions.
> make[2]: *** [scripts/Makefile.build:249 : kernel/locking/rtmutex_api.o]
> Erreur 1
> make[1]: *** [scripts/Makefile.build:465 : kernel/locking] Erreur 2
> make: *** [Makefile:1857 : kernel] Erreur 2
> 


Same problem with 10.3, 9.5, 8.5 and 5.5

> 
>>
>>> So, it looks like gcc still has issues with certain uses of asm goto.
>>
>> Could be.  Please attach preprocessed code (or reduced code that shows
>> the same problem if you have that / can make that).  Thanks!
>>
>>
>> Segher

  reply	other threads:[~2022-08-26  7:38 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
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 [this message]
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=a5f0e388-0de4-be04-43eb-5df5108ee984@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=segher@kernel.crashing.org \
    --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®