From: Nick Clifton <nickc@redhat.com>
To: Palmer Dabbelt <palmer@dabbelt.com>, binutils@sourceware.org
Cc: Kuan-Lin Chen <rufus@andestech.com>
Subject: Re: [PATCH 2/3] Fix DW_CFA_advance_loc relocation.
Date: Wed, 15 Mar 2017 09:27:00 -0000 [thread overview]
Message-ID: <2da70383-547e-d176-3c19-b9e33301b587@redhat.com> (raw)
In-Reply-To: <20170313214753.4477-3-palmer@dabbelt.com>
Hi Palmer,
> 2017-03-02 Kuan-Lin Chen <rufus@andestech.com>
>
> * config/tc-riscv.c (md_apply_fix): Set fx_frag and
> fx_next->fx_frag for CFA_advance_loc relocations.
Approved - please apply.
Cheers
Nick
next prev parent reply other threads:[~2017-03-15 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 21:48 Fix RISC-V CFA relocations Palmer Dabbelt
2017-03-13 21:48 ` [PATCH 3/3] Define DWARF2_USE_FIXED_ADVANCE_PC Palmer Dabbelt
2017-03-15 9:28 ` Nick Clifton
2017-03-13 21:48 ` [PATCH 2/3] Fix DW_CFA_advance_loc relocation Palmer Dabbelt
2017-03-14 10:55 ` Jan Beulich
2017-03-14 16:18 ` Palmer Dabbelt
2017-03-15 9:27 ` Nick Clifton [this message]
2017-03-13 21:48 ` [PATCH 1/3] Fix the offset of CFA relocation Palmer Dabbelt
2017-03-15 9:27 ` Nick Clifton
2017-03-14 17:01 ` Fix RISC-V CFA relocations Palmer Dabbelt
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=2da70383-547e-d176-3c19-b9e33301b587@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.org \
--cc=palmer@dabbelt.com \
--cc=rufus@andestech.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).