From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Naveen N. Rao" <naveen.n.rao@linux.ibm.com>
Cc: linux-kernel@vger.kernel.org, Uros Bizjak <ubizjak@gmail.com>,
x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>,
linuxppc-dev@lists.ozlabs.org, sv@linux.ibm.com
Subject: Re: [PATCH] compiler-gcc.h: Remove ancient workaround for gcc PR 58670
Date: Thu, 25 Aug 2022 13:08:06 -0500 [thread overview]
Message-ID: <20220825180806.GG25951@gate.crashing.org> (raw)
In-Reply-To: <1661422971.cqtahfm22j.naveen@linux.ibm.com>
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.
> 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
next prev parent reply other threads:[~2022-08-25 18:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 14:14 [PATCH] compiler-gcc.h: Remove ancient workaround for gcc PR 58670 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 [this message]
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=20220825180806.GG25951@gate.crashing.org \
--to=segher@kernel.crashing.org \
--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