public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Alfred M. Szmidt" <ams@gnu.org>
To: dclarke@blastwave.org
Cc: aph@redhat.com, gcc-help@gcc.gnu.org, david.kirkby@onetel.net
Subject: Re: Why is gcc going to default to "GNU dialect of ISO C99?"
Date: Thu, 11 Feb 2010 09:43:00 -0000	[thread overview]
Message-ID: <E1NfUov-0006IO-9R@fencepost.gnu.org> (raw)
In-Reply-To: <35520.10.0.66.17.1265842168.squirrel@interact.purplecow.org> 	(message from Dennis Clarke on Wed, 10 Feb 2010 17:49:28 -0500 (EST))

If you wish to use a compiler that ad hers to ISO C99, then you should
use the c99 program as per POSIX 1003.1 2004; that is the proper and
standard compliant way to invoke a ISO C99 compiler.  What the gcc
program will do by default is set by the GNU project, the g after all
stands for GNU, not ISO or POSIX.

  reply	other threads:[~2010-02-11  8:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11  2:40 Dennis Clarke
2010-02-11  9:43 ` Alfred M. Szmidt [this message]
2010-02-11 12:00   ` Alexey Salmin
     [not found]     ` <C79952E6.1947E%eljay@adobe.com>
2010-02-11 13:48       ` Alexey Salmin
     [not found]         ` <C79973C1.194A3%eljay@adobe.com>
2010-02-11 14:58           ` Alexey Salmin
2010-02-11 15:11             ` John (Eljay) Love-Jensen
2010-02-12  5:32     ` Patrick Horgan
  -- strict thread matches above, loose matches on Subject: below --
2010-02-11 17:14 Dennis Clarke
2010-02-11 14:50 Dennis Clarke
2010-02-11 14:14 Dennis Clarke
2010-02-11 14:42 ` Alexey Salmin
2010-02-11 13:44 Dennis Clarke
2010-02-11 14:00 ` Alexey Salmin
2010-02-10 17:00 Dr. David Kirkby
2010-02-10 17:26 ` Andrew Haley
2010-02-10 17:45   ` Dr. David Kirkby
2010-02-10 18:07     ` Alfred M. Szmidt
2010-02-10 19:25       ` Dr. David Kirkby
2010-02-10 20:59         ` Kevin P. Fleming
2010-02-10 18:39     ` Andrew Haley
2010-02-11  2:46     ` Ian Lance Taylor

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=E1NfUov-0006IO-9R@fencepost.gnu.org \
    --to=ams@gnu.org \
    --cc=aph@redhat.com \
    --cc=david.kirkby@onetel.net \
    --cc=dclarke@blastwave.org \
    --cc=gcc-help@gcc.gnu.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).