Author: pfg
Date: Tue Jan 10 20:44:31 2017
New Revision: 311896
URL: https://svnweb.freebsd.org/changeset/base/311896

Log:
  Remove unused __gnu_inline() attribute.
  
  This was meant to be used by a future FORTIFY_SOURCE implementation.
  Probably for good, FORTIFY_SOURCE and this particular GCCism were never
  well supported by clang or other compilers. Furthermore, the technology
  has long since been replaced by either static checkers, sanitizers, or
  even just the strong stack protector that was enabled by default.
  
  Drop __gnu_inline to avoid cluttering the headers.
  
  MFC after:    5 days

Modified:
  head/sys/sys/cdefs.h

Modified: head/sys/sys/cdefs.h
==============================================================================
--- head/sys/sys/cdefs.h        Tue Jan 10 20:43:32 2017        (r311895)
+++ head/sys/sys/cdefs.h        Tue Jan 10 20:44:31 2017        (r311896)
@@ -543,22 +543,6 @@
            __attribute__((__format__ (__strftime__, fmtarg, firstvararg)))
 #endif
 
-/*
- * FORTIFY_SOURCE, and perhaps other compiler-specific features, require
- * the use of non-standard inlining.  In general we should try to avoid
- * using these but GCC-compatible compilers tend to support the extensions
- * well enough to use them in limited cases.
- */ 
-#if defined(__GNUC_GNU_INLINE__) || defined(__GNUC_STDC_INLINE__)
-#if __GNUC_PREREQ__(4, 3) || __has_attribute(__artificial__)
-#define        __gnu_inline    __attribute__((__gnu_inline__, __artificial__))
-#else
-#define        __gnu_inline    __attribute__((__gnu_inline__))
-#endif /* artificial */
-#else
-#define        __gnu_inline
-#endif
-
 /* Compiler-dependent macros that rely on FreeBSD-specific extensions. */
 #if defined(__FreeBSD_cc_version) && __FreeBSD_cc_version >= 300001 && \
     defined(__GNUC__) && !defined(__INTEL_COMPILER)
_______________________________________________
svn-src-all@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/svn-src-all
To unsubscribe, send any mail to "svn-src-all-unsubscr...@freebsd.org"

Reply via email to