From: Lance Fredrickson <lancethepants@gmail.com>
To: Ramana Radhakrishnan <ramana.gcc@googlemail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <rearnsha@arm.com>
Subject: Re: [PATCH V2] arm: add -static-pie support
Date: Mon, 15 Aug 2022 21:05:50 -0600 [thread overview]
Message-ID: <cac02481-a757-cb51-142f-685e65fedeab@gmail.com> (raw)
In-Reply-To: <CAJA7tRZ+hviLM843UK3e0fhEW+YgdbncYhGmmEFK9Lm5deGSGA@mail.gmail.com>
Yes, this is a 1st submission.
Yes, I guess I was going for DCO rules.
I will look at running the test suite. Does this need to be done on the
target? because my arm target is a measly dual core 1ghz embedded chip
and low ram. Netgear R7000 router actually.
regards
Lance
On 8/10/2022 2:30 PM, Ramana Radhakrishnan wrote:
> Hi Lance,
>
> Thanks for your contribution - looks like your first one to GCC ?
>
> The patch looks good to me, though it should probably go through a
> full test suite run on arm-linux-gnueabihf and get a ChangeLog - see
> here for more https://gcc.gnu.org/contribute.html#patches.
>
> This is probably small enough to go under the 10 line rule but since
> you've used Signed-off-by in your patch, is that indicating you are
> contributing under DCO rules -
> https://gcc.gnu.org/contribute.html#legal ?
>
> regards
> Ramana
>
>
> On Thu, Aug 4, 2022 at 5:48 PM Lance Fredrickson via Gcc-patches
> <gcc-patches@gcc.gnu.org> wrote:
>> Just a follow up trying to get some eyes on my static-pie patch
>> submission for arm.
>> Feedback welcome.
>> https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598610.html
>>
>> thanks,
>> Lance Fredrickson
next prev parent reply other threads:[~2022-08-16 3:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 14:06 Lance Fredrickson
2022-08-04 16:47 ` Lance Fredrickson
2022-08-10 20:30 ` Ramana Radhakrishnan
2022-08-16 3:05 ` Lance Fredrickson [this message]
2022-09-05 13:13 ` Andrea Corallo
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=cac02481-a757-cb51-142f-685e65fedeab@gmail.com \
--to=lancethepants@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramana.gcc@googlemail.com \
--cc=rearnsha@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).