From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/gcc: arc-2019.03/9.1.0: Fix compilation of glibc
Date: Thu, 18 Jul 2019 22:34:19 +0200 [thread overview]
Message-ID: <20190718223419.58050ad3@windsurf> (raw)
In-Reply-To: <20190716215001.9181-1-abrodkin@synopsys.com>
On Wed, 17 Jul 2019 00:50:01 +0300
Alexey Brodkin <Alexey.Brodkin@synopsys.com> wrote:
> When storing a TLS symbol to memory, always use an intermediate register
> to load it. Otherwise compiler generates instruction which couldn't be
> encoded and we see:
> ----------------------------->8---------------------------
> In file included from gethstent_r.c:34:
> ../nss/getXXent_r.c: In function '__gethostent_r':
> ../nss/getXXent_r.c:168:1: error: unrecognizable insn:
> }
> ^
> (insn 25 24 26 5 (set (mem:SI (plus:SI (reg/f:SI 149 virtual-outgoing-args)
> (const_int 16 [0x10])) [0 S4 A32])
> (plus:SI (reg:SI 25 r25)
> (reg:SI 174))) "../nss/getXXent_r.c":160 -1
> (nil))
> during RTL pass: vregs
> ../nss/getXXent_r.c:168:1: internal compiler error: in extract_insn, at recog.c:2304
> In file included from getnetent_r.c:34:
> ../nss/getXXent_r.c: In function '__getnetent_r':
> ../nss/getXXent_r.c:168:1: error: unrecognizable insn:
> }
> ^
> (insn 25 24 26 5 (set (mem:SI (plus:SI (reg/f:SI 149 virtual-outgoing-args)
> (const_int 16 [0x10])) [0 S4 A32])
> (plus:SI (reg:SI 25 r25)
> (reg:SI 174))) "../nss/getXXent_r.c":160 -1
> (nil))
> during RTL pass: vregs
> ../nss/getXXent_r.c:168:1: internal compiler error: in extract_insn, at recog.c:2304
> ----------------------------->8---------------------------
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-07-18 20:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 21:50 [Buildroot] [PATCH] package/gcc: arc-2019.03/9.1.0: Fix compilation of glibc Alexey Brodkin
2019-07-18 20:34 ` Thomas Petazzoni [this message]
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=20190718223419.58050ad3@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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