I can't take this compiler braindamage any more, so I just decided to
remove the ilog2_NaN checks, and return 0 for any constant value <
2.
It's commit 474c90156c8d ("give up on gcc ilog2() constant
optimizations") in my tree. I'll push it out later after my usual
build tests (and I have a few
On 2017.03.01 at 17:39 +, Ard Biesheuvel wrote:
> On 1 March 2017 at 00:00, Laura Abbott wrote:
> > On 02/25/2017 03:50 AM, Ard Biesheuvel wrote:
> >>
> >>
> >>> On 25 Feb 2017, at 11:23, Ard Biesheuvel
> >>> wrote:
> >>>
> >>> On 25 February 2017 at 11:09, Markus Trippelsdorf
> >>> wrote:
On 2 March 2017 at 10:11, Markus Trippelsdorf wrote:
> On 2017.03.01 at 17:39 +, Ard Biesheuvel wrote:
>> On 1 March 2017 at 00:00, Laura Abbott wrote:
>> > On 02/25/2017 03:50 AM, Ard Biesheuvel wrote:
>> >>
>> >>
>> >>> On 25 Feb 2017, at 11:23, Ard Biesheuvel
>> >>> wrote:
>> >>>
>> >>>
On 1 March 2017 at 00:00, Laura Abbott wrote:
> On 02/25/2017 03:50 AM, Ard Biesheuvel wrote:
>>
>>
>>> On 25 Feb 2017, at 11:23, Ard Biesheuvel wrote:
>>>
>>> On 25 February 2017 at 11:09, Markus Trippelsdorf
>>> wrote:
On 2017.02.25 at 09:11 +, Ard Biesheuvel wrote:
>> On 25 Febru
On 02/25/2017 03:50 AM, Ard Biesheuvel wrote:
>
>
>> On 25 Feb 2017, at 11:23, Ard Biesheuvel wrote:
>>
>> On 25 February 2017 at 11:09, Markus Trippelsdorf
>> wrote:
>>> On 2017.02.25 at 09:11 +, Ard Biesheuvel wrote:
> On 25 February 2017 at 08:18, Markus Trippelsdorf
> wrote:
>
> On 25 Feb 2017, at 11:23, Ard Biesheuvel wrote:
>
> On 25 February 2017 at 11:09, Markus Trippelsdorf
> wrote:
>> On 2017.02.25 at 09:11 +, Ard Biesheuvel wrote:
On 25 February 2017 at 08:18, Markus Trippelsdorf
wrote:
Why not simply get rid of the ilog2_NaN th
On 25 February 2017 at 11:09, Markus Trippelsdorf
wrote:
> On 2017.02.25 at 09:11 +, Ard Biesheuvel wrote:
>> On 25 February 2017 at 08:18, Markus Trippelsdorf
>> wrote:
>> >
>> > Why not simply get rid of the ilog2_NaN thing altogether?
>> >
>>
>> That would remove the issue, sure. But
On 2017.02.25 at 09:11 +, Ard Biesheuvel wrote:
> On 25 February 2017 at 08:18, Markus Trippelsdorf
> wrote:
> >
> > Why not simply get rid of the ilog2_NaN thing altogether?
> >
>
> That would remove the issue, sure. But we lose an opportunity to spot
> incorrect code at compile time.
On 25 February 2017 at 08:18, Markus Trippelsdorf
wrote:
> On 2017.02.24 at 15:33 -0800, Laura Abbott wrote:
>> On 02/24/2017 01:45 PM, Ard Biesheuvel wrote:
>> > On 24 February 2017 at 21:25, John Stultz wrote:
>> >> On Thu, Feb 23, 2017 at 10:43 AM, Laura Abbott wrote:
>> >>> Hi,
>> >>>
>> >>>
On 2017.02.24 at 15:33 -0800, Laura Abbott wrote:
> On 02/24/2017 01:45 PM, Ard Biesheuvel wrote:
> > On 24 February 2017 at 21:25, John Stultz wrote:
> >> On Thu, Feb 23, 2017 at 10:43 AM, Laura Abbott wrote:
> >>> Hi,
> >>>
> >>> Fedora was previously carrying a workaround for a gcc7 issue repo
On 02/24/2017 01:45 PM, Ard Biesheuvel wrote:
> On 24 February 2017 at 21:25, John Stultz wrote:
>> On Thu, Feb 23, 2017 at 10:43 AM, Laura Abbott wrote:
>>> Hi,
>>>
>>> Fedora was previously carrying a workaround for a gcc7 issue reported
>>> on arm64
>>> http://lists.infradead.org/pipermail/li
On 24 February 2017 at 21:25, John Stultz wrote:
> On Thu, Feb 23, 2017 at 10:43 AM, Laura Abbott wrote:
>> Hi,
>>
>> Fedora was previously carrying a workaround for a gcc7 issue reported
>> on arm64
>> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-October/461597.html.
>> The workar
On Thu, Feb 23, 2017 at 10:43 AM, Laura Abbott wrote:
> Hi,
>
> Fedora was previously carrying a workaround for a gcc7 issue reported
> on arm64
> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-October/461597.html.
> The workaround got rid of __ilog2_NaN. I dropped the patch this morn
13 matches
Mail list logo
