On 19-06-2015 12:00, Maxim Kuvyrkov wrote:
>> On Jun 18, 2015, at 6:41 PM, Nicolas Pitre wrote:
>>
>> On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>>
>>>
>>>
>>> On 18-06-2015 11:26, Nicolas Pitre wrote:
On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>
> On 18-06-2015 0
> On Jun 18, 2015, at 6:41 PM, Nicolas Pitre wrote:
>
> On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>>
>>
>> On 18-06-2015 11:26, Nicolas Pitre wrote:
>>> On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>>>
On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
>> On Jun 17, 2015
On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>
> On 18-06-2015 11:26, Nicolas Pitre wrote:
> > On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
> >
> >>
> >>
> >> On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre
> wrote:
>
> On Thu,
On 18-06-2015 11:26, Nicolas Pitre wrote:
> On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>>
>>
>> On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
On Jun 17, 2015, at 3:15 AM, Nicolas Pitre
wrote:
On Thu, 4 Jun 2015, Jim Wilson wrote:
> The normal toolchain process i
On Thu, 18 Jun 2015, Adhemerval Zanella wrote:
>
>
> On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
> >> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre
> >> wrote:
> >>
> >> On Thu, 4 Jun 2015, Jim Wilson wrote:
> >>
> >>> The normal toolchain process is that patches get added to our releases
> >>> on
On 18-06-2015 05:44, Maxim Kuvyrkov wrote:
>> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre wrote:
>>
>> On Thu, 4 Jun 2015, Jim Wilson wrote:
>>
>>> The normal toolchain process is that patches get added to our releases
>>> only if they are already upstream. Our releases are FSF releases plus
>>>
> On Jun 17, 2015, at 3:15 AM, Nicolas Pitre wrote:
>
> On Thu, 4 Jun 2015, Jim Wilson wrote:
>
>> The normal toolchain process is that patches get added to our releases
>> only if they are already upstream. Our releases are FSF releases plus
>> patches backported from mainline, with no local c
On Thu, 4 Jun 2015, Jim Wilson wrote:
> The normal toolchain process is that patches get added to our releases
> only if they are already upstream. Our releases are FSF releases plus
> patches backported from mainline, with no local changes except when
> absolutely unavoidable.
It is commit 4511
On Mon, 8 Jun 2015, Jim Wilson wrote:
> On Mon, Jun 8, 2015 at 11:36 AM, Nicolas Pitre
> wrote:
> > Unless I'm missing something obvious, I can't find any section where all
> > options are documented together. There is the "Invoking" section but it
> > contains very few options and only the most
On Mon, Jun 8, 2015 at 11:36 AM, Nicolas Pitre wrote:
> Unless I'm missing something obvious, I can't find any section where all
> options are documented together. There is the "Invoking" section but it
> contains very few options and only the most generic ones. All the
> others are documented he
On Thu, 4 Jun 2015, Jim Wilson wrote:
> On Wed, Jun 3, 2015 at 4:15 PM, Nicolas Pitre
> wrote:
> > I created a patch on top of upstream binutils for a feature I need which
> > should be universally useful as well. Now I have 3 questions for you:
> >
> > 1) Does it look sane enough?
>
> You adde
On Fri, 5 Jun 2015, Pinski, Andrew wrote:
> I am just going to say, I don't like this extension at all. It allows for
> abuse than it is good.
What abuses do you forsee? Could you elaborate please?
> Oh and why can't you use the C preprocessor to do this section
> renaming? I know for a fact
om: linaro-toolchain on behalf of
Pinski, Andrew
Sent: Friday, June 5, 2015 3:05 AM
To: Maxim Kuvyrkov; Jim Wilson
Cc: Nicolas Pitre; Linaro Toolchain Mailman List
Subject: RE: new gas feature: section name substitution sequence
I am just going to say, I don't like this extension at all. It al
: Jim Wilson
Cc: Nicolas Pitre; Linaro Toolchain Mailman List
Subject: Re: new gas feature: section name substitution sequence
> On Jun 4, 2015, at 9:33 PM, Jim Wilson wrote:
>
> On Wed, Jun 3, 2015 at 4:15 PM, Nicolas Pitre
> wrote:
>> I created a patch on top of upstream binuti
> On Jun 4, 2015, at 9:33 PM, Jim Wilson wrote:
>
> On Wed, Jun 3, 2015 at 4:15 PM, Nicolas Pitre
> wrote:
>> I created a patch on top of upstream binutils for a feature I need which
>> should be universally useful as well. Now I have 3 questions for you:
>>
>> 1) Does it look sane enough?
>
On Thu, 4 Jun 2015, Jim Wilson wrote:
> On Wed, Jun 3, 2015 at 4:15 PM, Nicolas Pitre
> wrote:
> > I created a patch on top of upstream binutils for a feature I need which
> > should be universally useful as well. Now I have 3 questions for you:
> >
> > 1) Does it look sane enough?
>
> You adde
On Wed, Jun 3, 2015 at 4:15 PM, Nicolas Pitre wrote:
> I created a patch on top of upstream binutils for a feature I need which
> should be universally useful as well. Now I have 3 questions for you:
>
> 1) Does it look sane enough?
You added the option docs into the .section docs. It is certain
Hello toolchain people,
I created a patch on top of upstream binutils for a feature I need which
should be universally useful as well. Now I have 3 questions for you:
1) Does it look sane enough?
2) If so, could you integrate it in the Linaro release?
3) Would you be willing to promote it upst
18 matches
Mail list logo
