From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
Claudiu Zissulescu Ianculescu <claziss@gmail.com>
Cc: "linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Claudiu Zissulescu <Claudiu.Zissulescu@synopsys.com>
Subject: Re: [PATCH] [ARC] Allow more ABIs in GLIBC_DYNAMIC_LINKER
Date: Tue, 31 Mar 2020 17:57:43 +0000 [thread overview]
Message-ID: <73641424-e286-c4af-de31-4fd0c751804e@synopsys.com> (raw)
In-Reply-To: <CY4PR1201MB012004563CBA85075C153D99A1C80@CY4PR1201MB0120.namprd12.prod.outlook.com>
Well its a hard requirement considering glibc is still using gcc-9 !
Thx,
-Vineet
On 3/31/20 9:26 AM, Alexey Brodkin wrote:
> Hi Claus,
>
>> -----Original Message-----
>> From: linux-snps-arc <linux-snps-arc-bounces@lists.infradead.org> On Behalf Of Claudiu Zissulescu
>> Ianculescu
>> Sent: Tuesday, March 31, 2020 1:07 PM
>> To: Vineet Gupta <vgupta@synopsys.com>
>> Cc: linux-snps-arc@lists.infradead.org; gcc-patches@gcc.gnu.org; Claudiu Zissulescu
>> <claziss@synopsys.com>
>> Subject: Re: [PATCH] [ARC] Allow more ABIs in GLIBC_DYNAMIC_LINKER
>>
>> Pushed.
> Is this one eligible for being back-ported to older GCCs?
> At least GCC 9.x would be really good.
>
> -Alexey
>
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2020-03-31 17:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 0:05 [PATCH] [ARC] Allow more ABIs in GLIBC_DYNAMIC_LINKER Vineet Gupta
2020-03-31 10:06 ` Claudiu Zissulescu Ianculescu
2020-03-31 16:26 ` Alexey Brodkin
2020-03-31 17:57 ` Vineet Gupta [this message]
2020-04-01 0:52 ` Vineet Gupta
2020-04-08 23:37 ` Vineet Gupta
2020-04-10 12:25 ` Claudiu Zissulescu Ianculescu
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=73641424-e286-c4af-de31-4fd0c751804e@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Claudiu.Zissulescu@synopsys.com \
--cc=claziss@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=linux-snps-arc@lists.infradead.org \
/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