From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Yufeng Zhang <Yufeng.Zhang@arm.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PING] [PATCH, libstdc++-v3] Add newlib specific ctype_members.cc
Date: Mon, 22 Oct 2012 03:05:00 -0000 [thread overview]
Message-ID: <CAH6eHdS=jSOVOMGs0saNUawAJtRhZ=Yq9hvmEx0=nXdPxf89OQ@mail.gmail.com> (raw)
In-Reply-To: <50818828.7050803@arm.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On 19 October 2012 18:04, Yufeng Zhang wrote:
>
> Please find the attached patch which documents the 'newlib' option for the
> configuration option '--enable-clocale'.
>
> Feel free to improve it.
Thanks for the description. I changed it slightly as I realised the
'darwin' option was also undocumented, so I committed the attached
patch to the trunk.
I haven't regenerated the HTML pages, I plan to do that soon after a
few more doc updates.
[-- Attachment #2: patch.txt --]
[-- Type: text/plain, Size: 5044 bytes --]
commit 7e0b461312a4304d8f84602732aa19cb718af32c
Author: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Mon Oct 22 00:40:07 2012 +0100
2012-10-22 Yufeng Zhang <yufeng.zhang@arm.com>
Jonathan Wakely <jwakely.gcc@gmail.com>
* doc/xml/manual/configure.xml (--enable-clocale): Document the
'newlib' and 'darwin' options. Minor stylistic improvements.
diff --git a/libstdc++-v3/doc/xml/manual/configure.xml b/libstdc++-v3/doc/xml/manual/configure.xml
index bc98d7a..827b232 100644
--- a/libstdc++-v3/doc/xml/manual/configure.xml
+++ b/libstdc++-v3/doc/xml/manual/configure.xml
@@ -38,7 +38,7 @@
</para>
<para>The canonical way to find out the configure options that are
available for a given set of libstdc++ sources is to go to the
- source directory and then type:<command>./configure --help</command>.
+ source directory and then type: <command>./configure --help</command>.
</para>
<variablelist>
@@ -107,15 +107,20 @@
(IEEE Std. 1003.1-2001) model based on langinfo/iconv/catgets,
'gnu' to specify a model based on functionality from the GNU C
library (langinfo/iconv/gettext) (from <link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="http://sources.redhat.com/glibc/">glibc</link>, the GNU C
- library), or 'generic' to use a generic "C"
- abstraction which consists of "C" locale info.
+ library), 'generic' to use a generic "C" abstraction which consists
+ of "C" locale info, 'newlib' to specify the Newlib C library model
+ which only differs from the 'generic' model in the handling of
+ ctype, or 'darwin' which omits the <type>wchar_t</type> specializations
+ needed by the 'generic' model.
</para>
- <para>If not explicitly specified, the configure proccess tries
+ <para>If not explicitly specified, the configure process tries
to guess the most suitable package from the choices above. The
default is 'generic'. On glibc-based systems of sufficient
- vintage (2.3 and newer), 'gnu' is automatically selected. This option
- can change the library ABI.
+ vintage (2.3 and newer), 'gnu' is automatically selected. On newlib-based
+ systems (<code>'--with_newlib=yes'</code>) and OpenBSD, 'newlib' is
+ automatically selected. On Mac OS X 'darwin' is automatically selected.
+ This option can change the library ABI.
</para>
</listitem></varlistentry>
@@ -181,9 +186,9 @@
and of the nanosleep and sched_yield functions, used in the
implementation of [thread.thread.this] of the 2011 ISO C++ standard.
The choice OPTION=yes checks for the availability of the facilities
- in libc and libposix4. In case of need the latter is also linked
+ in libc and libposix4. In case it's needed the latter is also linked
to libstdc++ as part of the build process. OPTION=rt also searches
- (and, in case, links) librt. Note that the latter is not always
+ (and, if needed, links) librt. Note that the latter is not always
desirable because, in glibc, for example, in turn it triggers the
linking of libpthread too, which activates locking, a large overhead
for single-thread programs. OPTION=no skips the tests completely.
@@ -249,7 +254,7 @@
</listitem></varlistentry>
<varlistentry><term><code>--enable-c99</code></term>
- <listitem><para>The "long long" type was introduced in C99, along
+ <listitem><para>The <type>long long</type> type was introduced in C99, along
with many other functions for wide characters, and math
classification macros, etc. If enabled, all C99 functions not
specified by the C++ standard will be put into <code>namespace
@@ -264,7 +269,7 @@
</listitem></varlistentry>
<varlistentry><term><code>--enable-wchar_t</code>[default]</term>
- <listitem><para>Template specializations for the "wchar_t" type are
+ <listitem><para>Template specializations for the <type>wchar_t</type> type are
required for wide character conversion support. Disabling
wide character specializations may be expedient for initial
porting efforts, but builds only a subset of what is required by
@@ -274,7 +279,7 @@
</listitem></varlistentry>
<varlistentry><term><code>--enable-long-long </code></term>
- <listitem><para>The "long long" type was introduced in C99. It is
+ <listitem><para>The <type>long long</type> type was introduced in C99. It is
provided as a GNU extension to C++98 in g++. This flag builds
support for "long long" into the library (specialized
templates and the like for iostreams). This option is on by default:
@@ -351,7 +356,7 @@
<listitem><para>Use extern template to pre-instantiate all required
specializations for certain types defined in the standard libraries.
These types include <classname>string</classname> and dependents like
- <classname>char_traits</classname>, the templateized io classes,
+ <classname>char_traits</classname>, the templatized IO classes,
<classname>allocator</classname>, and others.
Disabling means that implicit
template generation will be used when compiling these types. By
prev parent reply other threads:[~2012-10-21 23:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-06 17:30 Yufeng Zhang
2011-06-23 16:46 ` [PING] " Yufeng Zhang
2011-06-27 17:19 ` Paolo Carlini
2011-07-01 17:00 ` Yufeng Zhang
2011-07-15 17:59 ` Yufeng Zhang
2011-07-15 18:16 ` Paolo Carlini
[not found] ` <CAH6eHdQFDzZsjVTYxVV8HD92GUMxcfCsrOG-B8m2Uf_UA4YDCw@mail.gmail.com>
[not found] ` <CAH6eHdQXAsk+F0mzQT4A170mYJvK7XddfCPEV857UZX=c1+8ig@mail.gmail.com>
[not found] ` <50818828.7050803@arm.com>
2012-10-22 3:05 ` Jonathan Wakely [this message]
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='CAH6eHdS=jSOVOMGs0saNUawAJtRhZ=Yq9hvmEx0=nXdPxf89OQ@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=Yufeng.Zhang@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=libstdc++@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).