From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: lint kills _Noreturn
Date: Sun, 29 May 2016 19:09:00 -0000 [thread overview]
Message-ID: <cf76b629-b04c-5e3f-2a68-a1681d8730f9@cornell.edu> (raw)
In-Reply-To: <6fef0097-c076-2691-c4f9-2af5a050a17e@cornell.edu>
On 5/29/2016 9:42 AM, Ken Brown wrote:
> If lint is defined, then /usr/include/sys/cdefs.h defines _Noreturn as a
> macro that expands to nothing. Is this intentional?
>
> Simple test case:
>
> $ cat test.h
> #define lint 1
> #include <sys/cdefs.h>
> _Noreturn void foo (void);
>
> $ gcc -E test.h | grep foo
> void foo (void);
I would think the following is the right thing here:
--- cdefs.h~ 2016-04-21 16:14:57.000000000 -0400
+++ cdefs.h 2016-05-29 11:12:09.326695700 -0400
@@ -277,7 +277,7 @@
* Keywords added in C11.
*/
-#if !defined(__STDC_VERSION__) || __STDC_VERSION__ < 201112L || defined(lint)
+#if !defined(__STDC_VERSION__) || __STDC_VERSION__ < 201112L
#if !__has_extension(c_alignas)
#if (defined(__cplusplus) && __cplusplus >= 201103L) || \
I don't see why defining lint should cause C11 keywords to be redefined, but maybe I'm missing something.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-05-29 15:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-29 17:21 Ken Brown
2016-05-29 19:09 ` Ken Brown [this message]
2016-05-29 19:28 ` Andy Moreton
2016-05-29 22:24 ` Ken Brown
2016-05-29 22:51 ` Ken Brown
2016-05-30 7:19 ` Andy Moreton
2016-05-30 8:25 ` Ken Brown
2016-05-30 10:35 ` Corinna Vinschen
2016-05-30 21:57 ` Hans-Bernhard Bröker
2016-05-31 9:35 ` Ken Brown
2016-05-31 9:41 ` Ken Brown
2016-05-31 17:03 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cf76b629-b04c-5e3f-2a68-a1681d8730f9@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).