public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Martin Liska <marxin@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. e8bdc4b83257648e9197e649ea240ffbf5fbe7e1 Date: Tue, 24 May 2022 18:55:20 +0000 (GMT) [thread overview] Message-ID: <20220524185520.9B9AB3BF90F8@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 e8bdc4b83257648e9197e649ea240ffbf5fbe7e1 (commit) from f55f35c86c68143a2b148c66e4b0b560c852ce6f (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 e8bdc4b83257648e9197e649ea240ffbf5fbe7e1 Author: Martin Liska <mliska@suse.cz> Date: Tue May 24 14:39:49 2022 +0200 Document ASAN changes for GCC 13. diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 6c5b2a37..4aba9917 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -47,6 +47,10 @@ a work-in-progress.</p> non-rectangular loop nests, which were added for C/C++ in GCC 11.</li> </ul> </li> + <li> + AddressSanitizer defaults to <code>detect_stack_use_after_return=1</code> on GNU/Linux target. + For compatibility, it can be disabled with <code>env ASAN_OPTIONS=detect_stack_use_after_return=0</code>. + </li> </ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-13/changes.html | 4 ++++ 1 file changed, 4 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2022-05-24 18:55 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=20220524185520.9B9AB3BF90F8@sourceware.org \ --to=marxin@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).