From: Andreas Schwab <schwab@linux-m68k.org>
To: Pedro Alves <palves@redhat.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] Sync libiberty/ & include/ with GCC
Date: Sat, 16 Sep 2017 18:47:00 -0000 [thread overview]
Message-ID: <87a81u5vl6.fsf@linux-m68k.org> (raw)
In-Reply-To: <1505493997-31716-1-git-send-email-palves@redhat.com> (Pedro Alves's message of "Fri, 15 Sep 2017 17:46:37 +0100")
On Sep 15 2017, Pedro Alves <palves@redhat.com> wrote:
> 2017-09-12 Jiong Wang <jiong.wang@arm.com>
>
> * dwarf2.def (DW_CFA_AARCH64_negate_ra_state): New DW_CFA_DUP.
> * dwarf2.h (DW_CFA_DUP): New define.
That breaks gold:
g++ -DHAVE_CONFIG_H -I. -I../../binutils/gold -I../../binutils/gold -I../../binutils/gold/../include -I../../binutils/gold/../elfcpp -DLOCALEDIR="\"/usr/share/locale\"" -DBINDIR="\"/usr/bin\"" -DTOOLBINDIR="\"/usr/x86_64-linux/bin\"" -DTOOLLIBDIR="\"/usr/x86_64-linux/lib\"" -W -Wall -Werror -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -frandom-seed=dwarf_reader.o -O2 -g -MT dwarf_reader.o -MD -MP -MF .deps/dwarf_reader.Tpo -c -o dwarf_reader.o ../../binutils/gold/dwarf_reader.cc
In file included from ../../binutils/gold/../elfcpp/dwarf.h:83:0,
from ../../binutils/gold/dwarf_reader.cc:30:
../../binutils/gold/../include/dwarf2.def:781:1: error: expected ‘}’ before ‘DW_CFA_DUP’
DW_CFA_DUP (DW_CFA_AARCH64_negate_ra_state, 0x2d)
^
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-09-16 18:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 16:46 Pedro Alves
2017-09-15 16:50 ` Pedro Alves
2017-09-16 18:47 ` Andreas Schwab [this message]
2017-09-17 7:12 ` Markus Trippelsdorf
2017-09-18 8:25 ` Nick Clifton
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=87a81u5vl6.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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