All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Tardieu <sam@rfc1149.net>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
	"Hanna Czenczek" <hreitz@redhat.com>,
	"Markus Armbruster" <armbru@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Richard Henderson" <richard.henderson@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH] docs/style: allow C99 mixed declarations
Date: Mon, 05 Feb 2024 19:12:21 +0100	[thread overview]
Message-ID: <877cjiaibh.fsf@rfc1149.net> (raw)
In-Reply-To: <ZcEdrp-y5YFsfir4@redhat.com>


Daniel P. Berrangé <berrange@redhat.com> writes:

> $ gcc -Wall -Wuninitialized -o jump jump.c

Note that many GCC warnings don't trigger if you don't enable 
optimizations. In the case you exhibit, adding -O is enough to get 
a sensible warning:

$ gcc -Wall -O -o jump jump.c
jump.c: In function ‘main’:
jump.c:11:3: warning: ‘foo’ may be used uninitialized 
[-Wmaybe-uninitialized]
   11 |   free(foo);
      |   ^~~~~~~~~
jump.c:8:9: note: ‘foo’ was declared here
    8 |   char *foo = malloc(30);
      |         ^~~

Best.

  Sam
-- 
Samuel Tardieu


  parent reply	other threads:[~2024-02-05 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 17:18 [PATCH] docs/style: allow C99 mixed declarations Stefan Hajnoczi
2024-02-05 17:41 ` Daniel P. Berrangé
2024-02-05 17:55   ` Peter Maydell
2024-02-05 18:12   ` Samuel Tardieu [this message]
2024-02-05 19:06     ` Stefan Hajnoczi
2024-02-05 19:17       ` Daniel P. Berrangé
2024-02-06  5:53   ` Markus Armbruster
2024-02-07  5:28     ` Philippe Mathieu-Daudé
2024-02-07  7:37       ` Markus Armbruster
2024-02-05 23:17 ` Alex Bennée
2024-02-06 13:48 ` Stefan Hajnoczi

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=877cjiaibh.fsf@rfc1149.net \
    --to=sam@rfc1149.net \
    --cc=alex.bennee@linaro.org \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.