From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: "libstdc++" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: libstdc++/44268 document libgcc version for hppa-linux
Date: Fri, 11 Jun 2010 15:51:00 -0000 [thread overview]
Message-ID: <AANLkTikEGxGDvJU4n4kekXHQ4lkAi46u74NuLCnPvMJN@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 170 bytes --]
2010-06-11 Jonathan Wakely <jwakely.gcc@gmail.com>
PR libstdc++/44268
* doc/xml/manual/abi.xml: Fix libgcc version for hppa-linux.
committed to trunk
[-- Attachment #2: abi.patch --]
[-- Type: text/x-patch, Size: 1497 bytes --]
Index: doc/xml/manual/abi.xml
===================================================================
--- doc/xml/manual/abi.xml (revision 160340)
+++ doc/xml/manual/abi.xml (working copy)
@@ -179,11 +179,26 @@ compatible.
<listitem><para>gcc-3.3.1: libgcc_s.so.1</para></listitem>
<listitem><para>gcc-3.3.2: libgcc_s.so.1</para></listitem>
<listitem><para>gcc-3.3.3: libgcc_s.so.1</para></listitem>
- <listitem><para>gcc-3.4.x, gcc-4.[0-5].x: on m68k-linux and
- hppa-linux this is either libgcc_s.so.1 (when configuring
- <code>--with-sjlj-exceptions</code>) or libgcc_s.so.2. For all
- others, this is libgcc_s.so.1. </para>
- </listitem>
+ <listitem><para>gcc-3.4.x, gcc-4.[0-5].x: libgcc_s.so.1</para></listitem>
+ </itemizedlist>
+
+ <para>For m68k-linux the versions differ as follows: </para>
+
+ <itemizedlist>
+ <listitem><para>gcc-3.4.x, gcc-4.[0-5].x: libgcc_s.so.1
+ when configuring <code>--with-sjlj-exceptions</code>, or
+ libgcc_s.so.2 </para> </listitem>
+ </itemizedlist>
+
+ <para>For hppa-linux the versions differ as follows: </para>
+
+ <itemizedlist>
+ <listitem><para>gcc-3.4.x, gcc-4.[0-1].x: either libgcc_s.so.1
+ when configuring <code>--with-sjlj-exceptions</code>, or
+ libgcc_s.so.2 </para> </listitem>
+ <listitem><para>gcc-4.[2-5].x: either libgcc_s.so.3 when configuring
+ <code>--with-sjlj-exceptions</code>) or libgcc_s.so.4
+ </para> </listitem>
</itemizedlist>
</listitem>
reply other threads:[~2010-06-11 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=AANLkTikEGxGDvJU4n4kekXHQ4lkAi46u74NuLCnPvMJN@mail.gmail.com \
--to=jwakely.gcc@gmail.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).