public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Gerald Pfeifer <gerald@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 8614af6cc6f3cfbc588d17e7dabbfde4ed73c6a1 Date: Thu, 8 Feb 2024 06:58:20 +0000 (GMT) [thread overview] Message-ID: <20240208065820.633443858C5F@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 8614af6cc6f3cfbc588d17e7dabbfde4ed73c6a1 (commit) from 3d0f4b4b7c389f0c9454ad71dd061b1bd8c68238 (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 8614af6cc6f3cfbc588d17e7dabbfde4ed73c6a1 Author: Gerald Pfeifer <gerald@pfeifer.com> Date: Thu Feb 8 07:57:55 2024 +0100 gcc-14: Tweak MCore entry diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 6d917535..dbc77493 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -504,7 +504,7 @@ a work-in-progress.</p> <!-- <h3 id="mcore">MCore</h3> --> <ul> <li>Bitfields are now signed by default per GCC policy. If you need bitfields - to be unsigned, then use <code>-funsigned-bitfields</code> + to be unsigned, use <code>-funsigned-bitfields</code>. </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-02-08 6:58 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=20240208065820.633443858C5F@sourceware.org \ --to=gerald@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).