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. 6a2dd6fe9cd4d3e7fad28aa937bb25870d9bd882 Date: Fri, 19 Jan 2024 15:33:44 +0000 (GMT) [thread overview] Message-ID: <20240119153344.3A3CE3858C33@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 6a2dd6fe9cd4d3e7fad28aa937bb25870d9bd882 (commit) from dda91b53cc53b0b42fbf47f06e9e44a8e2a2c1c5 (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 6a2dd6fe9cd4d3e7fad28aa937bb25870d9bd882 Author: Georg-Johann Lay <avr@gjlay.de> Date: Fri Jan 19 16:33:10 2024 +0100 gcc-14/changes: More details on AVR changes. diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 951d005b..a04b62ff 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -364,8 +364,8 @@ a work-in-progress.</p> by symbol <code>__RODATA_FLASH_START__</code> which takes precedence over <code>__flmap</code>.</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> - <li>When a block other than the last 32 KiB block is used to store + hardware default for bit-field <code>NVMCTRL_CTRLB.FLMAP</code>.</li> + <li>When a block other than the last 32 KiB block is used to store .rodata, then <code>NVMCTRL_CTRLB.FLMAP</code> must be initialized accordingly by hand, or a version of AVR-LibC that implements <a @@ -387,6 +387,24 @@ a work-in-progress.</p> with a version of Binutils that implements <a href="https://sourceware.org/PR31124">PR31124</a>, which is the case for Binutils v2.42 and up.</li> + <li>The implementation consists of two parts: + <ol> + <li>Binutils support new emulations <code>avrxmega2_flmap</code> and + <code>avrxmega4_flmap</code>. The sole purpose of these emulations + is to provide adjusted default linker description files. + Apart from that, these emulations behave exactly the same like + <code>avrxmega2</code> resp. <code>avrxmega4</code>.</li> + <li>The compiler uses a + <a href="https://gcc.gnu.org/wiki/avr-gcc#spec-files">device-specs</a> + file which links the program + with <code>-mavrxmega2_flmap</code> or <code>-mavrxmega2</code> + depending on <code>-m[no-]rodata-in-ram</code>; and similar + for <code>-mavrxmega4[_flmap]</code>.</li> + </ol> + This means the feature can be used with older compiler or Binutils + versions; all what's needed is an adjusted linker script and + a custom device-specs file. + </li> </ul> </li> <li>A new compiler option <code>-m[no]-rodata-in-ram</code> has been added. ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 22 ++++++++++++++++++++-- 1 file changed, 20 insertions(+), 2 deletions(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-01-19 15:33 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=20240119153344.3A3CE3858C33@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).