On 10/31/2012 06:06 AM, Borislav Petkov wrote:
>> Realistically, a single macro could be defined in compiler*.h that
>> encapsulates the entirety of this mechanism and only exposes a "black
>> box" macro, that will simply expand to something that breaks the build
>> in the most appropriate fashion
On 10/31/2012 06:06 AM, Borislav Petkov wrote:
Realistically, a single macro could be defined in compiler*.h that
encapsulates the entirety of this mechanism and only exposes a black
box macro, that will simply expand to something that breaks the build
in the most appropriate fashion based
On 10/31/2012 06:06 AM, Borislav Petkov wrote:
> On Wed, Oct 31, 2012 at 12:34:45AM -0500, Daniel Santos wrote:
>> Yes, the __build_bug_on_failed message is much more informative. This
>> will only increase with these patches. For example, the line
>>
>> BUILD_BUG_ON(sizeof(*c) != 4);
>>
>>
On Wed, Oct 31, 2012 at 12:34:45AM -0500, Daniel Santos wrote:
> Yes, the __build_bug_on_failed message is much more informative. This
> will only increase with these patches. For example, the line
>
> BUILD_BUG_ON(sizeof(*c) != 4);
>
> emits this error:
>
> arch/x86/kernel/cpu/amd.c: In
On Wed, Oct 31, 2012 at 12:34:45AM -0500, Daniel Santos wrote:
Yes, the __build_bug_on_failed message is much more informative. This
will only increase with these patches. For example, the line
BUILD_BUG_ON(sizeof(*c) != 4);
emits this error:
arch/x86/kernel/cpu/amd.c: In function
On 10/31/2012 06:06 AM, Borislav Petkov wrote:
On Wed, Oct 31, 2012 at 12:34:45AM -0500, Daniel Santos wrote:
Yes, the __build_bug_on_failed message is much more informative. This
will only increase with these patches. For example, the line
BUILD_BUG_ON(sizeof(*c) != 4);
emits this error:
On 10/30/2012 11:19 AM, Borislav Petkov wrote:
> On Sun, Oct 28, 2012 at 03:57:12PM -0500, danielfsan...@att.net wrote:
>> Prior to the introduction of __attribute__((error("msg"))) in gcc 4.3,
>> creating compile-time errors required a little trickery.
>> BUILD_BUG{,_ON} uses this attribute when
On Sun, Oct 28, 2012 at 03:57:12PM -0500, danielfsan...@att.net wrote:
> Prior to the introduction of __attribute__((error("msg"))) in gcc 4.3,
> creating compile-time errors required a little trickery.
> BUILD_BUG{,_ON} uses this attribute when available to generate
> compile-time errors, but
On Sun, Oct 28, 2012 at 03:57:12PM -0500, danielfsan...@att.net wrote:
Prior to the introduction of __attribute__((error(msg))) in gcc 4.3,
creating compile-time errors required a little trickery.
BUILD_BUG{,_ON} uses this attribute when available to generate
compile-time errors, but also uses
On 10/30/2012 11:19 AM, Borislav Petkov wrote:
On Sun, Oct 28, 2012 at 03:57:12PM -0500, danielfsan...@att.net wrote:
Prior to the introduction of __attribute__((error(msg))) in gcc 4.3,
creating compile-time errors required a little trickery.
BUILD_BUG{,_ON} uses this attribute when available
Prior to the introduction of __attribute__((error("msg"))) in gcc 4.3,
creating compile-time errors required a little trickery.
BUILD_BUG{,_ON} uses this attribute when available to generate
compile-time errors, but also uses the negative-sized array trick for
older compilers, resulting in two
Prior to the introduction of __attribute__((error(msg))) in gcc 4.3,
creating compile-time errors required a little trickery.
BUILD_BUG{,_ON} uses this attribute when available to generate
compile-time errors, but also uses the negative-sized array trick for
older compilers, resulting in two error
12 matches
Mail list logo
