On 3.3.2016 08:59, Lukas Slebodnik wrote:
> On (01/03/16 14:35), Petr Spacek wrote:
>> On 1.3.2016 12:06, Lukas Slebodnik wrote:
>>> On (25/02/16 15:57), Petr Spacek wrote:
On 19.2.2016 13:55, Petr Spacek wrote:
> Hello,
>
> Fix build with GCC 4.9+.
>
> GCC 4.9+ is too aggr
On (01/03/16 14:35), Petr Spacek wrote:
>On 1.3.2016 12:06, Lukas Slebodnik wrote:
>> On (25/02/16 15:57), Petr Spacek wrote:
>>> On 19.2.2016 13:55, Petr Spacek wrote:
Hello,
Fix build with GCC 4.9+.
GCC 4.9+ is too aggressive when optimizing functions with nonnull
at
On 1.3.2016 12:06, Lukas Slebodnik wrote:
> On (25/02/16 15:57), Petr Spacek wrote:
>> On 19.2.2016 13:55, Petr Spacek wrote:
>>> Hello,
>>>
>>> Fix build with GCC 4.9+.
>>>
>>> GCC 4.9+ is too aggressive when optimizing functions with nonnull
>>> attributes. This removes most of asserts() in the p
On (25/02/16 15:57), Petr Spacek wrote:
>On 19.2.2016 13:55, Petr Spacek wrote:
>> Hello,
>>
>> Fix build with GCC 4.9+.
>>
>> GCC 4.9+ is too aggressive when optimizing functions with nonnull
>> attributes. This removes most of asserts() in the plugin.
>> GCC 6 adds warnings for these cases.
>>
On 19.2.2016 13:55, Petr Spacek wrote:
> Hello,
>
> Fix build with GCC 4.9+.
>
> GCC 4.9+ is too aggressive when optimizing functions with nonnull
> attributes. This removes most of asserts() in the plugin.
> GCC 6 adds warnings for these cases.
>
> We are disabling the unwanted condition prunin
Hello,
Fix build with GCC 4.9+.
GCC 4.9+ is too aggressive when optimizing functions with nonnull
attributes. This removes most of asserts() in the plugin.
GCC 6 adds warnings for these cases.
We are disabling the unwanted condition pruning by adding
-fno-delete-null-pointer-checks argument.
BIN