From: Martin Sebor <msebor@gmail.com>
To: Joseph Myers <joseph@codesourcery.com>,
James Greenhalgh <James.Greenhalgh@arm.com>
Cc: Jason Merrill <jason@redhat.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH] convert braced initializers to strings (PR 71625)
Date: Tue, 14 Aug 2018 22:18:00 -0000 [thread overview]
Message-ID: <04935db6-1c50-90c4-9b25-b6e5ce4f446b@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1808142112370.21830@digraph.polyomino.org.uk>
On 08/14/2018 03:14 PM, Joseph Myers wrote:
> On Tue, 14 Aug 2018, James Greenhalgh wrote:
>
>> Hi Martin,
>>
>> This causes issues for the AArch64 tests (full list below).
>
> This change (r263511) also breaks the glibc build for alpha-linux-gnu with
> build-many-glibcs.py (using mainline GCC and binutils). The error I see
> is:
>
> /scratch/jmyers/glibc-bot/install/compilers/alpha-linux-gnu/lib/gcc/alpha-glibc-linux-gnu/9.0.0/../../../../alpha-glibc-linux-gnu/bin/ld:
> /scratch/jmyers/glibc-bot/build/compilers/alpha-linux-gnu/glibc/alpha-linux-gnu/libc.a(plural.o):
> in function `__gettextparse':
> /scratch/jmyers/glibc-bot/build/compilers/alpha-linux-gnu/glibc/alpha-linux-gnu/intl/plural.c:1108:(.text+0x218):
> relocation truncated to fit: GPRELHIGH against `.sdata'
> /scratch/jmyers/glibc-bot/install/compilers/alpha-linux-gnu/lib/gcc/alpha-glibc-linux-gnu/9.0.0/../../../../alpha-glibc-linux-gnu/bin/ld:
> /scratch/jmyers/glibc-bot/build/compilers/alpha-linux-gnu/glibc/alpha-linux-gnu/intl/plural.c:1348:(.text+0x300):
> relocation truncated to fit: GPRELHIGH against `.sdata'
> collect2: error: ld returned 1 exit status
> ../Rules:224: recipe for target
> '/scratch/jmyers/glibc-bot/build/compilers/alpha-linux-gnu/glibc/alpha-linux-gnu/elf/sln'
> failed
> make[3]: ***
> [/scratch/jmyers/glibc-bot/build/compilers/alpha-linux-gnu/glibc/alpha-linux-gnu/elf/sln]
> Error 1
>
> This is with Bison 3.0.4, should the version used to produce intl/plural.c
> prove relevant.
Can you send me the translation unit and the options it was compiled
with that triggered the errors?
Thanks
Martin
next prev parent reply other threads:[~2018-08-14 22:18 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-30 23:51 Martin Sebor
2018-07-31 13:39 ` Jason Merrill
2018-07-31 14:49 ` Martin Sebor
2018-08-07 8:58 ` Jason Merrill
2018-08-07 23:04 ` Martin Sebor
2018-08-08 11:09 ` Jason Merrill
2018-08-09 0:17 ` Martin Sebor
2018-08-09 22:07 ` Joseph Myers
2018-08-13 10:36 ` Jason Merrill
2018-08-14 13:27 ` James Greenhalgh
2018-08-14 15:08 ` Martin Sebor
2018-08-14 15:24 ` Martin Sebor
2018-08-15 2:34 ` Martin Sebor
2018-08-15 10:29 ` James Greenhalgh
2018-08-15 15:04 ` Richard Biener
2018-08-15 15:51 ` Martin Sebor
2018-08-17 17:19 ` [PATCH] Fix poly types after PR tree-optimization/71625 strlen optimization Szabolcs Nagy
2018-08-17 17:22 ` Kyrill Tkachov
2018-08-14 21:14 ` [PATCH] convert braced initializers to strings (PR 71625) Joseph Myers
2018-08-14 22:18 ` Martin Sebor [this message]
2018-08-15 12:07 ` Joseph Myers
2018-08-15 21:02 ` Martin Sebor
2018-08-15 21:14 ` Jeff Law
2018-08-15 21:34 ` Jeff Law
2018-08-16 15:23 ` Martin Sebor
2018-08-16 15:32 ` Jeff Law
2018-08-06 16:41 ` Martin Sebor
2018-08-06 17:04 ` Joseph Myers
2018-08-07 2:02 ` Martin Sebor
2018-08-07 11:31 ` Joseph Myers
2018-08-07 23:05 ` Martin Sebor
2018-08-08 17:33 Bernd Edlinger
2018-08-08 18:34 ` Bernd Edlinger
2018-08-08 19:50 ` Martin Sebor
2018-08-08 20:35 ` Bernd Edlinger
2018-08-08 20:48 ` Joseph Myers
2018-08-09 0:23 ` Martin Sebor
2018-08-09 10:47 ` Joseph Myers
2018-08-16 6:37 Bernd Edlinger
2018-08-17 22:26 ` Bernd Edlinger
2018-08-18 4:13 ` Jeff Law
2018-08-18 10:40 ` Richard Sandiford
2018-08-18 14:25 ` Bernd Edlinger
2018-08-18 16:46 ` Richard Sandiford
2018-08-18 17:09 ` Bernd Edlinger
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=04935db6-1c50-90c4-9b25-b6e5ce4f446b@gmail.com \
--to=msebor@gmail.com \
--cc=James.Greenhalgh@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jason@redhat.com \
--cc=joseph@codesourcery.com \
--cc=nd@arm.com \
/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).