Posix Tests Compiler Warnings

[Joel Sherrill]

On 8/21/2013 8:05 AM, Sebastian Huber wrote:
> Hello,
>
> before we start here we should first fix the <inttypes.h> provided by Newlib:
>
> http://www.rtems.org/pipermail/rtems-devel/2013-August/004055.html
And the Single UNIX Specification for inttypes.h:

http://pubs.opengroup.org/onlinepubs/009604599/basedefs/inttypes.h.html

RTEMS should have these and whatever extras we have defined in a way that
eliminates the warnings.

This is actually a tedious issue since you have to define them in a way that
generates no warnings on any architecture. I think there is a test for these
now in the suite. Perhaps it is missing some of these cases.

But fixing inttypes.h is the answer. It moves us more to POSIX
> On 2013-08-21 06:33, Rempel, Cynthia wrote:
>> Hi,
>>
>> Reducing the number of unnecessary compiler warnings makes it easier to find (and fix) real compiler warnings...
>>
>> The fix is in accordance with:
>>
>> https://www.kernel.org/doc/Documentation/printk-formats.txt
>> If <type> is dependent on a config option for its size (e.g., sector_t,
>> blkcnt_t) or is architecture-dependent for its size (e.g., tcflag_t), use a
>> format specifier of its largest possible type and explicitly cast to it.
>>
>> This patch reduces the number of posix tests compiler warnings, by recasting arguments in printf statements...
>>
>> Thanks,
>> Cynthia Rempel
>>
>>
>>
>> _______________________________________________
>> rtems-devel mailing list
>> rtems-devel at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-devel
>>
>


-- 
Joel Sherrill, Ph.D.              Director of Research & Development
joel.sherrill at OARcorp.com         On-Line Applications Research
Ask me about RTEMS: a free RTOS   Huntsville AL 35805
Support Available                 (256) 722-9985