On 09/30/2013 12:03 PM, Geert Uytterhoeven wrote:
On Mon, Sep 30, 2013 at 7:45 PM, David Daney wrote:
What about using __builtin_unreachable when we can but turn off warnings
and use do{}while(0) when __builtin_unreachable does not exist? This seems
the both worlds. Newer compilers produce
On Mon, Sep 30, 2013 at 7:45 PM, David Daney wrote:
>> What about using __builtin_unreachable when we can but turn off warnings
>> and use do{}while(0) when __builtin_unreachable does not exist? This seems
>> the both worlds. Newer compilers produce better code with unreachable
>> anyways.
>>
>
On 09/30/2013 10:15 AM, Pinski, Andrew wrote:
On Sep 30, 2013, at 9:20 AM, "David Daney" wrote:
On 09/30/2013 07:56 AM, Ralf Baechle wrote:
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled. Here's a test case extracted from one of them:
/*
*
> On Sep 30, 2013, at 9:20 AM, "David Daney" wrote:
>
>> On 09/30/2013 07:56 AM, Ralf Baechle wrote:
>> Lately I received several patches for build issues that only strike if
>> CONFIG_BUG is disabled. Here's a test case extracted from one of them:
>>
>> /*
>> * Definition of BUG taken from
On 09/30/2013 07:56 AM, Ralf Baechle wrote:
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled. Here's a test case extracted from one of them:
/*
* Definition of BUG taken from asm-generic/bug.h for the CONFIG_BUG=n case
*/
#define BUG() do {}
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled. Here's a test case extracted from one of them:
/*
* Definition of BUG taken from asm-generic/bug.h for the CONFIG_BUG=n case
*/
#define BUG() do {} while(0)
int foo(int arg)
{
int res;
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled. Here's a test case extracted from one of them:
/*
* Definition of BUG taken from asm-generic/bug.h for the CONFIG_BUG=n case
*/
#define BUG() do {} while(0)
int foo(int arg)
{
int res;
On 09/30/2013 07:56 AM, Ralf Baechle wrote:
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled. Here's a test case extracted from one of them:
/*
* Definition of BUG taken from asm-generic/bug.h for the CONFIG_BUG=n case
*/
#define BUG() do {}
On Sep 30, 2013, at 9:20 AM, David Daney ddaney.c...@gmail.com wrote:
On 09/30/2013 07:56 AM, Ralf Baechle wrote:
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled. Here's a test case extracted from one of them:
/*
* Definition of BUG taken
On 09/30/2013 10:15 AM, Pinski, Andrew wrote:
On Sep 30, 2013, at 9:20 AM, David Daney ddaney.c...@gmail.com wrote:
On 09/30/2013 07:56 AM, Ralf Baechle wrote:
Lately I received several patches for build issues that only strike if
CONFIG_BUG is disabled. Here's a test case extracted from
On Mon, Sep 30, 2013 at 7:45 PM, David Daney ddaney.c...@gmail.com wrote:
What about using __builtin_unreachable when we can but turn off warnings
and use do{}while(0) when __builtin_unreachable does not exist? This seems
the both worlds. Newer compilers produce better code with unreachable
On 09/30/2013 12:03 PM, Geert Uytterhoeven wrote:
On Mon, Sep 30, 2013 at 7:45 PM, David Daney ddaney.c...@gmail.com wrote:
What about using __builtin_unreachable when we can but turn off warnings
and use do{}while(0) when __builtin_unreachable does not exist? This seems
the both worlds.
12 matches
Mail list logo
