public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: hongtao Liu <liuhongt@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. e5f9b13eaca1baf31abcbdc9422a7ac23cf16155 Date: Fri, 9 Feb 2024 02:49:50 +0000 (GMT) [thread overview] Message-ID: <20240209024950.84E2E3858C60@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 e5f9b13eaca1baf31abcbdc9422a7ac23cf16155 (commit) from 8614af6cc6f3cfbc588d17e7dabbfde4ed73c6a1 (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 e5f9b13eaca1baf31abcbdc9422a7ac23cf16155 Author: liuhongt <hongtao.liu@intel.com> Date: Thu Feb 8 16:38:01 2024 +0800 Hardware-assisted AddressSanitizer now works for x86_64 with LAM_U57 diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index dbc77493..6be7457b 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html @@ -499,6 +499,11 @@ a work-in-progress.</p> <code>-march=knm</code>, <code>-mtune=knl</code> or <code>-mtune=knm</code> compiler switches. Support will be removed in GCC 15. </li> + <li><a href="https://gcc.gnu.org/gcc-11/changes.html">Hardware-assisted + AddressSanitizer</a> now works for the x86-64 target with LAM_U57. + <code>-fsanitize=hwaddress</code> will enable <code>-mlam=u57</code> + by default. + </li> </ul> <!-- <h3 id="mcore">MCore</h3> --> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-14/changes.html | 5 +++++ 1 file changed, 5 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2024-02-09 2:49 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=20240209024950.84E2E3858C60@sourceware.org \ --to=liuhongt@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).