From: Gerald Pfeifer <gerald@pfeifer.com>
To: Dave Korn <dave.korn.cygwin@gmail.com>
Cc: Richard Biener <richard.guenther@gmail.com>,
gcc-patches@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH][4.8][4.7][4.6] Make -shared-libgcc the default on Cygwin.
Date: Sun, 18 Aug 2013 12:14:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.00.1308181356390.2133@trevally.site> (raw)
In-Reply-To: <51409B61.8000704@gmail.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>
prev parent reply other threads:[~2013-08-18 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 1:42 Dave Korn
2013-03-12 8:59 ` Richard Biener
2013-03-13 15:27 ` Dave Korn
2013-08-18 12:14 ` Gerald Pfeifer [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=alpine.LNX.2.00.1308181356390.2133@trevally.site \
--to=gerald@pfeifer.com \
--cc=dave.korn.cygwin@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=richard.guenther@gmail.com \
/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).