public inbox for gcc-cvs-wwwdocs@sourceware.org
help / color / mirror / Atom feed
From: Georg-Johann Lay <gjl@sourceware.org>
To: gcc-cvs-wwwdocs@gcc.gnu.org
Subject: gcc-wwwdocs branch master updated. d7a5aa5196fc8c8e5722122704e056e86b6f7923
Date: Wed, 14 Feb 2024 10:05:47 +0000 (GMT) [thread overview]
Message-ID: <20240214100547.1963D385C6DD@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 d7a5aa5196fc8c8e5722122704e056e86b6f7923 (commit)
from 474f08c3aea933850b8314dd655815e9482e43af (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 d7a5aa5196fc8c8e5722122704e056e86b6f7923
Author: Georg-Johann Lay <avr@gjlay.de>
Date: Wed Feb 14 11:04:54 2024 +0100
gcc-14: AVR. Fix typos.
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 92bd0a7b..4d8c3dd6 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -369,7 +369,7 @@ a work-in-progress.</p>
by symbol <code>__RODATA_FLASH_START__</code> which takes
precedence over <code>__flmap</code>.
For example, linking with
- <nobr><code>-Wl,--defsym,__RODATA_FLASH_START__=32k</code></nobr>
+ <code>-Wl,--defsym,__RODATA_FLASH_START__=32k</code>
chooses the second 32 KiB block.</li>
<li>The default uses the last 32 KiB block, which is also the
hardware default for bit-field <code>NVMCTRL_CTRLB.FLMAP</code>.</li>
@@ -391,8 +391,8 @@ a work-in-progress.</p>
__asm (".global __flmap_lock" "\n\t"
"__flmap_lock = 1");</pre></li>
<li>When you do not want the code from #931, then define global
- symbol <code>__do_flmap_init</code> and the linker will no more drag
- that code from <code>lib<var>mcu</var>.a</code>.</li>
+ symbol <code>__do_flmap_init</code> and the linker will not pull in
+ that code from <code>lib<var>mcu</var>.a</code> any more.</li>
<li>In order to return to the old placement of read-only data in RAM,
the new compiler option <code>-mrodata-in-ram</code> can be used.</li>
<li>Read-only data is located in output section <code>.rodata</code>,
-----------------------------------------------------------------------
Summary of changes:
htdocs/gcc-14/changes.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
hooks/post-receive
--
gcc-wwwdocs
reply other threads:[~2024-02-14 10:05 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=20240214100547.1963D385C6DD@sourceware.org \
--to=gjl@sourceware.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: 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).