From: Jeff Law via Libc-alpha <libc-alpha@sourceware.org>
To: Lukasz Majewski <lukma@denx.de>,
GNU C Library <libc-alpha@sourceware.org>,
"libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: Question regarding m68k GCC compiler error
Date: Wed, 12 Aug 2020 08:48:48 -0600 [thread overview]
Message-ID: <51b1a36c80d6c7f75c0ebca13f50b01535ead17c.camel@redhat.com> (raw)
In-Reply-To: <20200812154353.6ec24f81@jawa>
On Wed, 2020-08-12 at 15:43 +0200, Lukasz Majewski wrote:
> Dear Community,
>
> During development of following patch [1]
> I've triggered some interesting error on m68k port:
>
> pthread_cond_wait.c: In function
> \342\200\230__pthread_cond_wait_common\342\200\231:
> pthread_cond_wait.c:629:1: error: unable to find a register to spill in
> class \342\200\230DATA_REGS\342\200\231
> 629 | }
> | ^
> pthread_cond_wait.c:629:1: error: this is the insn:
> (jump_insn 485 484 486 27 (parallel [
> (set (pc)
> (if_then_else (eq (reg:DI 80 [ _123 ])
> (reg:DI 142 [ s+-4 ]))
> (label_ref 530)
> (pc)))
> (clobber (scratch:DI))
> (clobber (scratch:SI))
> ]) "../sysdeps/nptl/futex-internal.h":552:10 5 {cbranchdi4_insn}
> (expr_list:REG_DEAD (reg:DI 142 [ s+-4 ])
> (int_list:REG_BR_PROB 536870916 (nil)))
> -> 530)
> pthread_cond_wait.c:629: confused by earlier errors, bailing out
>
>
> This error only happens on:
>
> glibcs-m68k-linux-gnu
> glibcs-m68k-linux-gnu-coldfire
> glibcs-m68k-linux-gnu-coldfire-soft
>
> Used gcc:
> gcc version 10.2.1 20200810 [releases/gcc-10 revision
> f098bc87dca:780e3a9fbae:b5cc5c95664347082100a504710f5ca0467306a5] (GCC)
>
> After poking around it looks like this may be an internal gcc error.
>
> How to reproduce:
> 1. Please use branch [2]
> 2. ../src/scripts/build-many-glibcs.py
> /home/lukma/work/glibc/glibc-many-build --keep failed glibcs
> m68k-linux-gnu m68k-linux-gnu-coldfire
>
>
>
> Before I submit a GCC bug - has anybody encountered any similar issue
> recently for this port?
Nope, haven't seen this.
As Florian noted, this could be a problem with simply using too many registers,
but we can't know without a self-contained testcase.
jeff
>
next prev parent reply other threads:[~2020-08-12 14:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 13:43 Question regarding m68k GCC compiler error Lukasz Majewski
2020-08-12 14:15 ` Florian Weimer
2020-08-13 8:02 ` Lukasz Majewski
2020-08-13 15:27 ` Jeff Law via Libc-alpha
2020-08-12 14:48 ` Jeff Law via Libc-alpha [this message]
2020-08-13 8:04 ` Lukasz Majewski
2020-08-13 15:28 ` Jeff Law via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51b1a36c80d6c7f75c0ebca13f50b01535ead17c.camel@redhat.com \
--to=libc-alpha@sourceware.org \
--cc=law@redhat.com \
--cc=libc-help@sourceware.org \
--cc=lukma@denx.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).