public inbox for
help / color / mirror / Atom feed
From: Jozef Lawrynowicz <>
Subject: gcc-wwwdocs branch master updated. fb048b7d45422cd869772462cba591a46f1b3b2f
Date: Tue, 15 Dec 2020 11:23:30 +0000 (GMT)	[thread overview]
Message-ID: <> (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  fb048b7d45422cd869772462cba591a46f1b3b2f (commit)
      from  969d5dfca2da12ef16144c76b96620b2c9b29d66 (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 fb048b7d45422cd869772462cba591a46f1b3b2f
Author: Jozef Lawrynowicz <>
Date:   Tue Dec 15 11:19:41 2020 +0000

    gcc-11/changes: Use <p> instead of <br> for "used" attribute description

diff --git a/htdocs/gcc-11/changes.html b/htdocs/gcc-11/changes.html
index ea9fe93c..1a9e72c1 100644
--- a/htdocs/gcc-11/changes.html
+++ b/htdocs/gcc-11/changes.html
@@ -159,16 +159,20 @@ a work-in-progress.</p>
+    <p>
     For ELF targets that support the GNU or FreeBSD OSABIs, the
     <code>used</code> attribute will now save the symbol declaration it is
     applied to from linker garbage collection.
-    <br>
+    </p>
+    <p>
     To support this behavior, <code>used</code> symbols that have not
     been placed in specific sections (e.g. with the <code>section</code>
     attribute, or the <code>-f{function,data}-sections</code> options) will
     be placed in new, unique sections.
-    <br>
+    </p>
+    <p>
     This functionality requires Binutils version 2.36 or later.
+    </p>


Summary of changes:
 htdocs/gcc-11/changes.html | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)


                 reply	other threads:[~2020-12-15 11:23 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).