public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: joris <joriswu@gmail.com>
To: overseers@gcc.gnu.org
Subject: GCC bugzilla
Date: Sun, 12 Mar 2017 09:46:00 -0000	[thread overview]
Message-ID: <7b76e9bc-5b62-ecc2-49cc-501c4740aada@gmail.com> (raw)

Hi,

I wanted to create a user account for GCC bugzilla in order to file a bug.

In case you have a place for such report, a summary is here :


The diagnostic -Wmaybe-uninitialized does not print the offending line 
if the offending code happens inside a function-like macro


GCC 7.0 snapshot 7.0.1 20170305 (experimental)


macros.h:

#define print_int(x) print_it("%d",(x))


code.c:

#include "macros.h"

extern void print_it(const char *fmt, int i);

void test(void)

{

   int unint;

   print_int(uninit);

}

gcc  -c -Wall test.c

In file included from test.c:1:0:
test.c: In function 'test':
macros.h:1:22: warning: 'uninit' is used uninitialized in this function 
[-Wuninitialized]
  #define print_int(x) print_it("%d",(x))
                       ^~~~~~~~
test.c:7:7: note: 'uninit' was declared here
    int uninit;
        ^~~~~~

so the offending line print_int() is not shown.

Regards,

Joris Wu


             reply	other threads:[~2017-03-12  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12  9:46 joris [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-11-30  5:14 gcc bugzilla Joern Rennecke
2017-03-30 10:20 GCC Bugzilla Alfred Agrell
2016-10-07 15:37 GCC bugzilla nicolas bouillot
2010-10-28 21:31 GCC Bugzilla Paul Koning
2010-10-28 21:38 ` Andrew Pinski
2010-10-29  0:31   ` Paul Koning

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=7b76e9bc-5b62-ecc2-49cc-501c4740aada@gmail.com \
    --to=joriswu@gmail.com \
    --cc=overseers@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: 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).