From: Sandra Loosemore <sandra@codesourcery.com>
To: Jonathan Wakely <jwakely@redhat.com>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [wwwdocs] Document -fcommon default change
Date: Mon, 06 Jan 2020 16:25:00 -0000 [thread overview]
Message-ID: <3d0548fd-b5ab-d04a-4efc-cb221b6a4b1d@codesourcery.com> (raw)
In-Reply-To: <20200106141002.GA586949@redhat.com>
On 1/6/20 7:10 AM, Jonathan Wakely wrote:
> How about:
>
> GCC now defaults to <code>-fno-common</code>. As a result, global
> variable accesses are more efficient on various targets. In C, global
> variables with multiple tentative definitions will result in linker
> errors.
This is better. I'd also s/will/now/, since we're talking about the
present behavior of GCC 10, not some future behavior.
-Sandra
next prev parent reply other threads:[~2020-01-06 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 13:14 Wilco Dijkstra
2020-01-06 14:10 ` Jonathan Wakely
2020-01-06 16:25 ` Sandra Loosemore [this message]
2020-01-07 15:15 ` Wilco Dijkstra
2020-01-11 10:27 ` Gerald Pfeifer
2020-02-06 20:07 ` [wwwdocs] Mention common attribute in gcc-10/porting_to.html Jakub Jelinek
2020-02-06 22:18 ` Gerald Pfeifer
2020-02-07 1:34 ` Sandra Loosemore
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=3d0548fd-b5ab-d04a-4efc-cb221b6a4b1d@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=jwakely@redhat.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).