From: Jeff Law <law@redhat.com>
To: Martin Sebor <msebor@gmail.com>, gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] document -Wuninitialized for allocated objects
Date: Wed, 16 Sep 2020 21:44:41 -0600 [thread overview]
Message-ID: <9cf77b01-3de7-2616-d07c-15ae5cd257e8@redhat.com> (raw)
In-Reply-To: <99fca194-7f87-eb59-8418-2f0a41f0fff3@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
On 9/15/20 11:06 AM, Martin Sebor via Gcc-patches wrote:
> The attached patch updates the manual to mention that Wuninitialized
> and -Wmaybe-uninitialized are issued for both auto and allocated
> objects, as well as for passing pointers to uninitialized objects
> to const-qualified parameters. Both of these features are GCC 11
> enhancements.
>
> Martin
>
> patches-gcc-wuninit-allocated.diff
>
> Document -Wuninitialized for allocated objects.
>
> gcc/ChangeLog:
>
> * doc/invoke.texi (-Wuninitialized): Document -Wuninitialized for
> allocated objects.
> (-Wmaybe-uninitialized): Same.
OK
jeff
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 1763 bytes --]
prev parent reply other threads:[~2020-09-17 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-15 17:06 Martin Sebor
2020-09-17 3:44 ` Jeff Law [this message]
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=9cf77b01-3de7-2616-d07c-15ae5cd257e8@redhat.com \
--to=law@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=msebor@gmail.com \
/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: link
Be 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).