public inbox for gcc-cvs-wwwdocs@sourceware.org help / color / mirror / Atom feed
From: Qing Zhao <qinzhao@sourceware.org> To: gcc-cvs-wwwdocs@gcc.gnu.org Subject: gcc-wwwdocs branch master updated. 6fce58b02b953ddcadf9d2f18aa35d8bef69fce5 Date: Wed, 29 Sep 2021 14:40:36 +0000 (GMT) [thread overview] Message-ID: <20210929144036.23B8E3858C60@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 6fce58b02b953ddcadf9d2f18aa35d8bef69fce5 (commit) from e25fd8a37b818ee090f739fddd3e5df025f1e2f6 (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 6fce58b02b953ddcadf9d2f18aa35d8bef69fce5 Author: qing zhao <qing.zhao@oracle.com> Date: Wed Sep 29 07:39:31 2021 -0700 gcc-12/changes.html: Uninitialized stack variables initialization update * htdocs/gcc-12/changes.html (Eliminating uninitialized variables): Item about the support for automatic static variable initialization. diff --git a/htdocs/gcc-12/changes.html b/htdocs/gcc-12/changes.html index 31307107..0e2962ee 100644 --- a/htdocs/gcc-12/changes.html +++ b/htdocs/gcc-12/changes.html @@ -247,6 +247,25 @@ a work-in-progress.</p> <!-- .................................................................. --> <h2>Other significant improvements</h2> +<h3 id="uninitialized">Eliminating uninitialized variables</h3> + +<ul> + <li>GCC can now initialize all stack variables implicitly, including + padding. This is intended to eliminate all classes of uninitialized + stack variable flaws. Lack of explicit initialization will still + warn when <code>-Wuninitialized</code> is active. For best + debugging, use of the new command-line option + <code>-ftrivial-auto-var-init=pattern</code> can be used to fill + variables with a repeated <code>0xFE</code> pattern, which tends to + illuminate many bugs (e.g. pointers receive invalid addresses, sizes + and indices are very large). For best production results, the new + command-line option <code>-ftrivial-auto-var-init=zero</code> can be + used to fill variables with <code>0x00</code>, which tends to provide + a safer state for bugs (e.g. pointers are <code>NULL</code>, strings + are <code>NUL</code> filled, and sizes and indices are <code>0</code>). + </li> +</ul> + <h3 id="debug">Debugging formats</h3> <ul> ----------------------------------------------------------------------- Summary of changes: htdocs/gcc-12/changes.html | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) hooks/post-receive -- gcc-wwwdocs
reply other threads:[~2021-09-29 14:40 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=20210929144036.23B8E3858C60@sourceware.org \ --to=qinzhao@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).