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. 2bdfd673b266343e7988fe2cd2b44a02c94dce09 Date: Tue, 9 Apr 2024 09:56:00 +0000 (GMT) [thread overview] Message-ID: <20240409095601.25FB53858CDB@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 2bdfd673b266343e7988fe2cd2b44a02c94dce09 (commit) from 7cd7e13e443da8e2aae389fa30eb547530c6e2c8 (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 2bdfd673b266343e7988fe2cd2b44a02c94dce09 Author: Georg-Johann Lay <avr@gjlay.de> Date: Tue Apr 9 11:55:29 2024 +0200 gcc-14: AVR: Note on silicon bug. diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 1b345b32..ff69e859 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -584,7 +584,11 @@ __asm (".global __flmap_lock" "\n\t" 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> + the new compiler option <code>-mrodata-in-ram</code> can be used. + <b>This is required on devices where the hardware revision is + affected by a silicon bug concerning the <code>FLMAP</code> + functionality.</b> + </li> <li>Read-only data is located in output section <code>.rodata</code>, wheras it is part of <code>.text</code> when located in RAM.</li> <li>The feature is only available when the compiler is configured ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-04-09 9:56 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=20240409095601.25FB53858CDB@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: 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).