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. b167175442edcd30e2944ae6a88b4391bf7c86fd Date: Tue, 13 Feb 2024 13:31:56 +0000 (GMT) [thread overview] Message-ID: <20240213133156.B95E03858C52@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 b167175442edcd30e2944ae6a88b4391bf7c86fd (commit) from 2aad86e498b9ce0dd512bd42d35a2d380c53db18 (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 b167175442edcd30e2944ae6a88b4391bf7c86fd Author: Georg-Johann Lay <avr@gjlay.de> Date: Tue Feb 13 14:31:24 2024 +0100 gcc-14: AVR: Explain __do_flmap_init. diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 713f5139..cd5f5157 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -390,6 +390,9 @@ a work-in-progress.</p> can be used:<pre> __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> <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 | 3 +++ 1 file changed, 3 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-02-13 13:31 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=20240213133156.B95E03858C52@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).