public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "meadori at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/57287] GCC 4.9.0 fails to build GDB on Ubuntu 12.04
Date: Mon, 19 Aug 2013 21:54:00 -0000	[thread overview]
Message-ID: <bug-57287-4-axboUG0NDo@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57287-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57287

meadori at gcc dot gnu.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |meadori at gcc dot gnu.org

--- Comment #14 from meadori at gcc dot gnu.org ---
(In reply to hmb from comment #13)
> Created attachment 30201 [details]
> preprocessed source code
> 
> Attaching the preprocessed source code

Here is a reduction (as of trunk today):

$ cat test.c
#include <setjmp.h>
#include <stdio.h>

struct node
{
  struct node *next;
  char *name;
} *list;

struct node *list;
struct node *head (void);

sigjmp_buf *bar (void);

int baz (void)
{
  struct node *n;
  int varseen = 0;

  list = head ();
  for (n = list; n; n = n->next)
    {
      if (!varseen)
          varseen = 1;

      sigjmp_buf *buf = bar ();
      __sigsetjmp (*buf, 1);
    }

  if (!varseen)
    return 0;
  return 1;
}
$ i686-pc-linux-gnu-gcc --version
i686-pc-linux-gnu-gcc (GCC) 4.9.0 20130819 (experimental)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ i686-pc-linux-gnu-gcc -Wall -O2 -c test.c
test.c: In function 'baz':
test.c:26:19: warning: 'buf' may be used uninitialized in this function
[-Wmaybe-uninitialized]
       sigjmp_buf *buf = bar ();
                   ^


  parent reply	other threads:[~2013-08-19 21:54 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-15 12:11 [Bug c/57287] New: " muhammad_bilal at mentor dot com
2013-05-15 12:43 ` [Bug c/57287] " palves at redhat dot com
2013-05-15 13:00 ` rguenth at gcc dot gnu.org
2013-05-22 17:10 ` [Bug middle-end/57287] " palves at redhat dot com
2013-05-23 10:57 ` muhammad_bilal at mentor dot com
2013-05-23 11:02 ` rguenth at gcc dot gnu.org
2013-05-23 11:03 ` rguenth at gcc dot gnu.org
2013-05-23 14:34 ` rguenth at gcc dot gnu.org
2013-05-23 14:42 ` rguenth at gcc dot gnu.org
2013-05-24 11:01 ` rguenth at gcc dot gnu.org
2013-05-24 12:45 ` rguenth at gcc dot gnu.org
2013-08-19 21:54 ` meadori at gcc dot gnu.org [this message]
2013-08-28  8:37 ` [Bug middle-end/57287] [4.9 Regression] Bogous uninitialized warning with abnormal control flow rguenth at gcc dot gnu.org
2013-08-28 16:58 ` xinliangli at gmail dot com
2013-08-29  8:18 ` [Bug middle-end/57287] [4.9 Regression] Bogus " rguenth at gcc dot gnu.org
2013-08-29 11:20 ` rguenth at gcc dot gnu.org
2013-08-29 11:20 ` rguenth at gcc dot gnu.org
2013-08-29 16:33 ` meadori at gcc dot gnu.org
2013-09-03  0:51 ` amylaar at gcc dot gnu.org
2013-09-03  7:49 ` rguenther at suse dot de
2013-09-03  7:53 ` rguenth at gcc dot gnu.org

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=bug-57287-4-axboUG0NDo@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).