From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: 15807@debbugs.gnu.org
Subject: bug#15807: guile-2.0.9 doesn't handle Apple clang < 5 or llvm.org clang < 3.3 properly
Date: Thu, 28 Nov 2013 20:38:39 +0100 [thread overview]
Message-ID: <87y548z58g.fsf@gnu.org> (raw)
In-Reply-To: <87iow7mu23.fsf@netris.org> (Mark H. Weaver's message of "Mon, 04 Nov 2013 22:00:36 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> So clang is pretending to be GCC (by defining __GNUC__), and then breaks
> if we use the noreturn attribute which has been supported in GCC since
> version 2.5 (released in 1993) ? If so, I consider that a bug in clang.
Agreed. As long as Clang defines __GNUC__, we should ignore any such problem.
Ludo’.
next prev parent reply other threads:[~2013-11-28 19:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 0:51 bug#15807: guile-2.0.9 doesn't handle Apple clang < 5 or llvm.org clang < 3.3 properly Jack Howarth
2013-11-05 3:00 ` Mark H Weaver
2013-11-28 19:38 ` Ludovic Courtès [this message]
2014-01-15 20:12 ` Mark H Weaver
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y548z58g.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=15807@debbugs.gnu.org \
--cc=mhw@netris.org \
/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).