This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Re: _Static_warning?
- From: Eduardo Piombino <drakorg at gmail dot com>
- To: Prathamesh Kulkarni <prathamesh dot kulkarni at linaro dot org>
- Cc: gcc-help <gcc-help at gcc dot gnu dot org>
- Date: Sat, 16 May 2015 12:59:09 -0300
- Subject: Re: _Static_warning?
- Authentication-results: sourceware.org; auth=none
- References: <CAGHqW79SSbF1QEddCChJFfzvm6tk5XoMHfcM0jwdpUUzAUmokw at mail dot gmail dot com> <CAAgBjM==xEVL4LCHHmV8Ub3T9bCNGgKT9JgGt1ticXRocdnS4A at mail dot gmail dot com>
Hi, I believe that won't nail it.
#warning is managed by the preprocessor, not the compiler, so it
shouldn't understand anything about the underlaying c code condition
that should trigger it or not.
On 16 May 2015 at 12:31, Prathamesh Kulkarni
<prathamesh.kulkarni@linaro.org> wrote:
> On 16 May 2015 at 20:28, Eduardo Piombino <drakorg@gmail.com> wrote:
>> Hi,
>>
>> Is there any way to get gcc to generate a warning upon some
>> compile-time condition?
> Try using #warning
> (https://gcc.gnu.org/onlinedocs/gcc-4.5.0/cpp/Diagnostics.html)
>
> Regards,
> Prathamesh
>> I'd be aiming at something like _Static_assert, but raising a warning
>> instead of an error.
>>
>> Nowadays, to achieve something similar, I have to run 2 builds, one
>> with the assert enabled just to get notified of such conditions, and
>> then a another one, without the asserts, to actually compile them.
>>
>> Thank you,
>> Eduardo.