From: John Rocha <jrr@cisco.com>
To: gcc-help@gcc.gnu.org
Subject: Which standard is the default for -std?
Date: Tue, 09 Mar 2010 17:11:00 -0000 [thread overview]
Message-ID: <4B96812C.8030307@cisco.com> (raw)
Hello All,
I was reading and found the '-std' flag for C++ compilation using the
[gcc] compiler.
My man page for [gcc] indicates:
1. gnu89
is the default value "Default, ISO C90 plus GNU extension
(including some C(features)".
2. gnu99
"ISO C99 plus GNU extension. When IOS C99 is fully implemented in
GCC this will become the default."
The version of [g++/gcc] I am using is as 4.1.2 20070115 (detailed
listing shown at end) for Linux on a SUSE 10 SP1 machine.
I went to gnu.org, navigated to the latest documentation for [g++/gcc]
and found 4.4.3 20100121. The PDF documentation for 4.4.3 describes the
'-std' options the same way: gnu89 is the current default, gnu99 is the
planned to be the future default.
Is this still true? Is gnu89 still the default, or is this a case where
the compiler was updated but the documentation wasn't? [Three years
seems a long time to implement a standard -- but I'm being a demanding
customer, eh? :)]
So, is gnu89 still the default for the '-std' flag?
Secondly, is there some flag or option that displays the settings, even
the default settings that are in use? I know, RTFM and trust in it, but
I've been burned by outdated documentation a few times. Hence my
apprehension.
Thanks in advance for your time,
-=John
Detailed listing for my version of g++/gcc.
--------------------------------------------------------------------------------
g++ -v
Using built-in specs.
Target: i586-suse-linux
Configured with: ../configure --enable-threads=posix --prefix=/usr
--with-local-prefix=/usr/local --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.2
--enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib
--with-system-zlib --enable-shared --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --program-suffix=
--enable-version-specific-runtime-libs --without-system-libunwind
--with-cpu=generic --host=i586-suse-linux
Thread model: posix
gcc version 4.1.2 20070115 (prerelease) (SUSE Linux)
--------------------------------------------------------------------------------
--
Thought for the day: "2 much txting mks u 1 bad splr!!!!"
next reply other threads:[~2010-03-09 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 17:11 John Rocha [this message]
2010-03-10 16:07 ` 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=4B96812C.8030307@cisco.com \
--to=jrr@cisco.com \
--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).