On 04/19/2016 12:47 PM, Emil Velikov wrote:
> On 19 April 2016 at 20:35, Ian Romanick wrote:
>> On 04/19/2016 12:32 PM, Chad Versace wrote:
>>> On Tue 19 Apr 2016, Ian Romanick wrote:
On 04/19/2016 12:15 PM, Chad Versace wrote:
> On Tue 19 Apr 2016, Emil Velikov wrote:
>> On 19 April
On 19 April 2016 at 20:35, Ian Romanick wrote:
> On 04/19/2016 12:32 PM, Chad Versace wrote:
>> On Tue 19 Apr 2016, Ian Romanick wrote:
>>> On 04/19/2016 12:15 PM, Chad Versace wrote:
On Tue 19 Apr 2016, Emil Velikov wrote:
> On 19 April 2016 at 19:38, Ian Romanick wrote:
>> On 04/19
On 04/19/2016 12:32 PM, Chad Versace wrote:
> On Tue 19 Apr 2016, Ian Romanick wrote:
>> On 04/19/2016 12:15 PM, Chad Versace wrote:
>>> On Tue 19 Apr 2016, Emil Velikov wrote:
On 19 April 2016 at 19:38, Ian Romanick wrote:
> On 04/19/2016 07:48 AM, Emil Velikov wrote:
>> On 18 April
On Tue 19 Apr 2016, Ian Romanick wrote:
> On 04/19/2016 12:15 PM, Chad Versace wrote:
> > On Tue 19 Apr 2016, Emil Velikov wrote:
> >> On 19 April 2016 at 19:38, Ian Romanick wrote:
> >>> On 04/19/2016 07:48 AM, Emil Velikov wrote:
> On 18 April 2016 at 19:01, Ian Romanick wrote:
> > On
On 04/19/2016 12:15 PM, Chad Versace wrote:
> On Tue 19 Apr 2016, Emil Velikov wrote:
>> On 19 April 2016 at 19:38, Ian Romanick wrote:
>>> On 04/19/2016 07:48 AM, Emil Velikov wrote:
On 18 April 2016 at 19:01, Ian Romanick wrote:
> On 04/18/2016 08:06 AM, Emil Velikov wrote:
>> On 1
On 04/19/2016 11:47 AM, Emil Velikov wrote:
> On 19 April 2016 at 19:38, Ian Romanick wrote:
>> The only things in macros.h that are related and use lower case are
>> likely, unlikely, unreachable, and assume. All four of those are lower
>> case because they mimic keywords in some compiler. We d
On Tue 19 Apr 2016, Emil Velikov wrote:
> On 19 April 2016 at 19:38, Ian Romanick wrote:
> > On 04/19/2016 07:48 AM, Emil Velikov wrote:
> >> On 18 April 2016 at 19:01, Ian Romanick wrote:
> >>> On 04/18/2016 08:06 AM, Emil Velikov wrote:
> On 18 April 2016 at 04:43, Francisco Jerez wrote:
On 19 April 2016 at 19:38, Ian Romanick wrote:
> On 04/19/2016 07:48 AM, Emil Velikov wrote:
>> On 18 April 2016 at 19:01, Ian Romanick wrote:
>>> On 04/18/2016 08:06 AM, Emil Velikov wrote:
On 18 April 2016 at 04:43, Francisco Jerez wrote:
> Grazvydas Ignotas writes:
>
>> On S
On 04/19/2016 07:48 AM, Emil Velikov wrote:
> On 18 April 2016 at 19:01, Ian Romanick wrote:
>> On 04/18/2016 08:06 AM, Emil Velikov wrote:
>>> On 18 April 2016 at 04:43, Francisco Jerez wrote:
Grazvydas Ignotas writes:
> On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov
> wrote:
On 04/15/2016 06:00 PM, Grazvydas Ignotas wrote:
> This is mostly for variables that are only used in asserts and cause
> unused-but-set-variable warnings in release builds. Could just use
> UNUSED directly, but MAYBE_UNUSED should be less confusing and is
> similar to what the Linux kernel has.
>
On 18 April 2016 at 19:01, Ian Romanick wrote:
> On 04/18/2016 08:06 AM, Emil Velikov wrote:
>> On 18 April 2016 at 04:43, Francisco Jerez wrote:
>>> Grazvydas Ignotas writes:
>>>
On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov
wrote:
> On 16 April 2016 at 02:00, Grazvydas Ignotas
On 18 April 2016 at 18:53, Francisco Jerez wrote:
> Emil Velikov writes:
>
>> On 18 April 2016 at 04:43, Francisco Jerez wrote:
>>> Grazvydas Ignotas writes:
>>>
On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov
wrote:
> On 16 April 2016 at 02:00, Grazvydas Ignotas wrote:
>> Th
On 04/18/2016 08:06 AM, Emil Velikov wrote:
> On 18 April 2016 at 04:43, Francisco Jerez wrote:
>> Grazvydas Ignotas writes:
>>
>>> On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov
>>> wrote:
On 16 April 2016 at 02:00, Grazvydas Ignotas wrote:
> This is mostly for variables that are only
Emil Velikov writes:
> On 18 April 2016 at 04:43, Francisco Jerez wrote:
>> Grazvydas Ignotas writes:
>>
>>> On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov
>>> wrote:
On 16 April 2016 at 02:00, Grazvydas Ignotas wrote:
> This is mostly for variables that are only used in asserts and
On 18 April 2016 at 04:43, Francisco Jerez wrote:
> Grazvydas Ignotas writes:
>
>> On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov
>> wrote:
>>> On 16 April 2016 at 02:00, Grazvydas Ignotas wrote:
This is mostly for variables that are only used in asserts and cause
unused-but-set-varia
Grazvydas Ignotas writes:
> On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov
> wrote:
>> On 16 April 2016 at 02:00, Grazvydas Ignotas wrote:
>>> This is mostly for variables that are only used in asserts and cause
>>> unused-but-set-variable warnings in release builds. Could just use
>>> UNUSED d
On Sun, Apr 17, 2016 at 2:50 AM, Emil Velikov wrote:
> On 16 April 2016 at 02:00, Grazvydas Ignotas wrote:
>> This is mostly for variables that are only used in asserts and cause
>> unused-but-set-variable warnings in release builds. Could just use
>> UNUSED directly, but MAYBE_UNUSED should be l
On 16 April 2016 at 02:00, Grazvydas Ignotas wrote:
> This is mostly for variables that are only used in asserts and cause
> unused-but-set-variable warnings in release builds. Could just use
> UNUSED directly, but MAYBE_UNUSED should be less confusing and is
> similar to what the Linux kernel has
This is mostly for variables that are only used in asserts and cause
unused-but-set-variable warnings in release builds. Could just use
UNUSED directly, but MAYBE_UNUSED should be less confusing and is
similar to what the Linux kernel has.
And yes __attribute__((unused)) can be used on variables o
19 matches
Mail list logo
