what's the rationale for checking for "__STDC__"?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  more pedantry here -- can someone clarify what the point is of
checking for "__STDC__" being defined, and adding that macro to the
definition of CHECKFLAGS in the top-level Makefile?

  Makefile:CHECKFLAGS     := -D__linux__ -Dlinux -D__STDC__ -Dunix \
	-D__unix__ -Wbitwise $(CF)

  as i understand it, the kernel source has the freedom to use
whatever gcc extensions it wants, but "checking" the source tree
(with, for example "sparse") first defines "__STDC__".  why?  what's
the point in checking for STDC compatibility here?  or am i misreading
this?

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux