public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: jakub@gcc.gnu.org To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. e37f2d6af29c52a51cb36058e3a7a2b79469f045 Date: Fri, 14 Feb 2020 08:10:00 -0000 [thread overview] Message-ID: <20200214081009.81623.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "gcc-wwwdocs". The branch, master has been updated via e37f2d6af29c52a51cb36058e3a7a2b79469f045 (commit) from 223de66470c17e210f7e7ecceb054c7bb29d49d5 (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit e37f2d6af29c52a51cb36058e3a7a2b79469f045 Author: Jakub Jelinek <jakub@redhat.com> Date: Fri Feb 14 09:09:44 2020 +0100 wwwdocs: Mention common attribute diff --git a/htdocs/gcc-10/porting_to.html b/htdocs/gcc-10/porting_to.html index 980d3af1..9574aacc 100644 --- a/htdocs/gcc-10/porting_to.html +++ b/htdocs/gcc-10/porting_to.html @@ -41,7 +41,12 @@ and provide solutions. Let us know if you have suggestions for improvements! which means a linker error will now be reported. To fix this, use <code>extern</code> in header files when declaring global variables, and ensure each global is defined in exactly one C file. - As a workaround, legacy C code can be compiled with <code>-fcommon</code>. + If tentative definitions of particular variables need to be + placed in a common block, <code>__attribute__((__common__))</code> can be + used to force that behavior even in code compiled without + <code>-fcommon</code>. + As a workaround, legacy C code where all tentative definitions should + be placed into a common block can be compiled with <code>-fcommon</code>. </p> <pre><code> int x; // tentative definition - avoid in header files ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-10/porting_to.html | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2020-02-14 8:10 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=20200214081009.81623.qmail@sourceware.org \ --to=jakub@gcc.gnu.org \ --cc=gcc-cvs-wwwdocs@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: linkBe 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).