linux-kernel - Re: __STRICT_ANSI_

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <1158302578.4312.166.camel@pmac.infradead.org>
Date:	Fri, 15 Sep 2006 07:42:58 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Ismail Donmez <ismail@...dus.org.tr>
Cc:	LKML <linux-kernel@...r.kernel.org>, mchehab@...radead.org
Subject: Re: __STRICT_ANSI__ checks in headers

On Fri, 2006-09-15 at 09:01 +0300, Ismail Donmez wrote:
> Kernel headers currently uses __STRICT_ANSI__ check before defining a long 
> long variable because ANSI-C doesn't allow long long variables. But this 
> seems to harsh because any project including linux/videodev2.h ( and similar 
> ones ) and using -ansi flag will not compile because some types like __s64 
> will not be defined.

One possible fix is to let videodev2.h use int64_t, and in userspace
they can include <stdint.h>

Another is just to declare videodev2.h incompatible with -ansi, or maybe
just omit 'value64' from the union if __STRICT_ANSI__ is defined, and
replace it with an array of two __s32s.

-- 
dwmw2

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/