This is the mail archive of the
mailing list for the binutils project.
RE: [PATCH] [ARC] GAS: allow CFI pseudo-ops.
- From: Claudiu Zissulescu <Claudiu dot Zissulescu at synopsys dot com>
- To: Nick Clifton <nickc at redhat dot com>, "binutils at sourceware dot org" <binutils at sourceware dot org>
- Cc: "Francois dot Bedard at synopsys dot com" <Francois dot Bedard at synopsys dot com>
- Date: Tue, 16 Feb 2016 15:02:18 +0000
- Subject: RE: [PATCH] [ARC] GAS: allow CFI pseudo-ops.
- Authentication-results: sourceware.org; auth=none
- References: <1455188463-1738-1-git-send-email-claziss at synopsys dot com> <56C1D54C dot 3030300 at redhat dot com> <098ECE41A0A6114BB2A07F1EC238DE8966178179 at DE02WEMBXB dot internal dot synopsys dot com> <56C1DACC dot 3070506 at redhat dot com>
Thank you Nick.
> -----Original Message-----
> From: Nick Clifton [mailto:email@example.com]
> Sent: Monday, February 15, 2016 3:04 PM
> To: Claudiu Zissulescu; firstname.lastname@example.org
> Cc: Francois.Bedard@synopsys.com
> Subject: Re: [PATCH] [ARC] GAS: allow CFI pseudo-ops.
> Hi Claudiu,
> > I have the write access now, thank you. Any advice on how to apply it?
> Yes. With the commit message I suggest that you do something like this:
> <one, possibly long, line describing the change>
> <blank line>
> <the changelog entry(s)>
> > Or anything else which I should take care of when submitting a patch to
> binutils repository?
> Testing is always a good idea. If there is any possibility that the patch might
> affect other ports then try to run some generic tests as well. A binutils
> toolchain configured as "--enable-targets=all --enable-64-bit-bfd"
> is a good start, as is a Linux native toolchain.