This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH][4.8][4.7][4.6] Make -shared-libgcc the default on Cygwin.
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Dave Korn <dave dot korn dot cygwin at gmail dot com>
- Cc: Richard Biener <richard dot guenther at gmail dot com>, gcc-patches at gcc dot gnu dot org, Jakub Jelinek <jakub at redhat dot com>
- Date: Sun, 18 Aug 2013 14:01:16 +0200 (CEST)
- Subject: Re: [PATCH][4.8][4.7][4.6] Make -shared-libgcc the default on Cygwin.
- References: <513E8877 dot 7070606 at gmail dot com> <CAFiYyc3MeOpkhwNZoLouny6qbW9PVaTkn6-u-o1PuTKpKkvc=A at mail dot gmail dot com> <51409B61 dot 8000704 at gmail dot com>
On Wed, 13 Mar 2013, Dave Korn wrote:
> Committed revision 196634, with the attached documentation update and cvs
> log entry:
>
> * htdocs/gcc-4.8/changes.html: Add OS-specific section and entry
> for Windows (Cygwin).
I applied this small editorial patch.
Gerald
Index: changes.html
===================================================================
RCS file: /cvs/gcc/wwwdocs/htdocs/gcc-4.8/changes.html,v
retrieving revision 1.119
diff -u -3 -p -r1.119 changes.html
--- changes.html 31 May 2013 08:49:25 -0000 1.119
+++ changes.html 18 Aug 2013 11:56:32 -0000
@@ -143,7 +143,7 @@ by this change.</p>
<code>-fsanitize=thread</code>. Instructions will be instrumented to
detect data races. The ThreadSanitizer is available on x86-64
GNU/Linux.</li>
- <li>A new local register allocator has been implemented, which
+ <li>A new local register allocator (LRA) has been implemented, which
replaces the 26 year old reload pass and improves generated
code quality. For now it is active on the ia32 and x86-64
targets.</li>
@@ -858,11 +858,12 @@ int i = A().f(); // error, f() requires
<ul>
<li>Executables are now linked against shared libgcc by default.
The previous default was to link statically, which can still be
- done by explicitly specifying -static or -static-libgcc on the
+ done by explicitly specifying <code>-static</code> or
+ <code>static-libgcc</code> on the
command line. However it is strongly advised against, as it
will cause problems for any application that makes use of DLLs
compiled by GCC. It should be alright for a monolithic stand-alone
- application that only links against the Windows OS DLLs, but
+ application that only links against the Windows DLLs, but
offers little or no benefit.</li>
</ul>