From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: Mass-building defconfigs: many fail with assembler errors
Date: Thu, 15 Dec 2022 09:47:48 +0100 [thread overview]
Message-ID: <20221215084748.zkfb7h6uhfzx7dp5@lug-owl.de> (raw)
In-Reply-To: <20221214090025.f3k3juinxfhhnr6u@lug-owl.de>
[-- Attachment #1: Type: text/plain, Size: 821 bytes --]
On Wed, 2022-12-14 10:00:25 +0100, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> On Tue, 2022-12-13 11:00:45 +0100, Jan-Benedict Glaw <jbglaw@lug-owl.de> wrote:
> > On Mon, 2022-12-12 18:26:13 -0600, Segher Boessenkool <segher@kernel.crashing.org> wrote:
> > > On Mon, Dec 12, 2022 at 10:51:17PM +0100, Jan-Benedict Glaw wrote:
> > > > Compiler ICEs (during GIMPLE pass: ccp) in align.c:
> Submitted as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108095:
...and already fixed upstream by Jakub Jelinek:
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=bf3ce6f84a7a994a0fc87419b383b9ce4efed442
That's the second asm goto related bug I submitted (initially found
while looking at powerpc builds) and I'm actually surprised about the
speed both of them got fixed. That's phantastic work!
MfG, JBG
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-12-15 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 21:51 Mass-building defconfigs: many fail with assembler errors Jan-Benedict Glaw
2022-12-13 0:26 ` Segher Boessenkool
2022-12-13 10:00 ` Jan-Benedict Glaw
2022-12-14 9:00 ` Jan-Benedict Glaw
2022-12-14 18:36 ` Jan-Benedict Glaw
2022-12-14 20:08 ` Segher Boessenkool
2022-12-15 8:47 ` Jan-Benedict Glaw [this message]
2022-12-13 3:49 ` Michael Ellerman
2022-12-13 8:41 ` Jan-Benedict Glaw
2022-12-13 12:23 ` Segher Boessenkool
2022-12-14 14:45 ` Jan-Benedict Glaw
2022-12-15 6:49 ` Christophe Leroy
2022-12-15 6:55 ` Christophe Leroy
2022-12-15 12:47 ` Michael Ellerman
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=20221215084748.zkfb7h6uhfzx7dp5@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=segher@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.