unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Matt Sicker <boards@gmail.com>
Cc: 15739@debbugs.gnu.org
Subject: bug#15739: Doesn't support clang as well as it could.
Date: Thu, 28 Nov 2013 20:35:37 +0100	[thread overview]
Message-ID: <877gbs1fqu.fsf@gnu.org> (raw)
In-Reply-To: <CACmp6kp4juJOybWR9Arn4o_7H-u7BOc6gMHVchcaJafTzP16mQ@mail.gmail.com> (Matt Sicker's message of "Sun, 27 Oct 2013 14:53:20 -0500")

Hi,

Matt Sicker <boards@gmail.com> skribis:

> There are plenty of macros that only check for GNU GCC and don't bother
> checking support from other popular compilers. For example, in
> libguile/__scm.h, the macros SCM_NORETURN, SCM_UNUSED, SCM_EXPECT, and many
> more, all only check for GCC support. Most (if not all) of these language
> extensions are supported by Clang, and usually using the same exact syntax!

Doesn’t Clang still define __GNUC__?  If it does, then it has to behave
like GCC, and thus nothing Clang-specific needs to be added.

Ludo’.





  reply	other threads:[~2013-11-28 19:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-27 19:53 bug#15739: Doesn't support clang as well as it could Matt Sicker
2013-11-28 19:35 ` Ludovic Courtès [this message]
2013-12-01  1:30   ` Matt Sicker
2013-12-01 22:09     ` Ludovic Courtès
  -- strict thread matches above, loose matches on Subject: below --
2013-10-27 22:10 bug#15741: Patch for bug #15739 Matt Sicker
2013-11-01 22:00 ` bug#15739: Doesn't support clang as well as it could 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=877gbs1fqu.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=15739@debbugs.gnu.org \
    --cc=boards@gmail.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).