From: Andreas Schwab <schwab@linux-m68k.org>
To: Kuan-Lin Chen <kuanlinchentw@gmail.com>
Cc: "binutils\@sourceware.org Development" <binutils@sourceware.org>
Subject: Re: [PATCH] [RISCV] Support subtraction of .uleb128.
Date: Wed, 27 Nov 2019 10:36:00 -0000 [thread overview]
Message-ID: <87sgm9vc5m.fsf@igel.home> (raw)
In-Reply-To: <CAJr6u0h3bsoK+-WXzs+ZHUi-GNb06MY8nDKD9=1JRFEGRp5r=A@mail.gmail.com> (Kuan-Lin Chen's message of "Wed, 27 Nov 2019 16:11:50 +0800")
On Nov 27 2019, Kuan-Lin Chen wrote:
> diff --git a/include/ChangeLog b/include/ChangeLog
> index 47bb86cf71..c290b245c6 100644
> --- a/include/ChangeLog
> +++ b/include/ChangeLog
> @@ -1,3 +1,7 @@
> +2019-11-27 Kuan-Lin Chen <kuanlinchentw@gmail.com>
> +
> + * elf/riscv.h ((R_RISCV_SET_ULEB128, (R_RISCV_SUB_ULEB128): Define.
There are too many open parens here.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2019-11-27 10:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 8:12 Kuan-Lin Chen
2019-11-27 10:36 ` Andreas Schwab [this message]
2019-12-02 1:18 ` Kuan-Lin Chen
2019-12-02 22:27 ` Jim Wilson
2019-12-06 23:48 ` Palmer Dabbelt via binutils
2019-12-10 5:43 ` Kuan-Lin Chen
2019-12-17 23:59 ` Jim Wilson
2019-12-18 1:50 ` Nelson Chu
2020-01-06 8:18 ` Kuan-Lin Chen
2020-01-06 8:37 ` Kito Cheng
2020-01-06 8:44 ` Kuan-Lin Chen
2020-01-09 23:20 ` Palmer Dabbelt via binutils
2020-01-22 7:26 ` Kuan-Lin Chen
2020-09-25 7:14 ` Kito Cheng
2020-09-25 15:55 ` Jozef Lawrynowicz
2020-09-01 12:56 Jozef Lawrynowicz
2020-09-02 1:29 ` Kuan-Lin Chen
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=87sgm9vc5m.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=binutils@sourceware.org \
--cc=kuanlinchentw@gmail.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).