public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mbuilov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/46045] New: incorrect code generated if redecalring local variable in do-while(0)
Date: Sat, 16 Oct 2010 13:26:00 -0000	[thread overview]
Message-ID: <bug-46045-4@http.gcc.gnu.org/bugzilla/> (raw)

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

           Summary: incorrect code generated if redecalring local variable
                    in do-while(0)
           Product: gcc
           Version: 4.5.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: mbuilov@gmail.com


following program gives incorrect results if compiled with -O0 and crashes if
compiled with -O2

$cat test.c

struct A
{
        int k;
};

static int *foo(struct A *a)
{
        do {
                struct A *a = a;
                return &a->k;
        } while (0);
}

int main(int argc, char *argv[])
{
        struct A a = {1};
        return *foo(&a);
}

$gcc -O0 test.c && ./a.out ; echo $?
72

$gcc -O2 test.c && ./a.out ; echo $?
Segmentation fault
139

Renaming local variable in do-while fixes the problem:
<                struct A *a = a;
<                return &a->k;
---
>                struct A *b = a;
>                return &b->k;

$gcc -O0 test.c && ./a.out ; echo $?
1

$gcc -O2 test.c && ./a.out ; echo $?
1


             reply	other threads:[~2010-10-16 13:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-16 13:26 mbuilov at gmail dot com [this message]
2010-10-16 13:32 ` [Bug c/46045] " zsojka at seznam dot cz
2010-10-16 18:44 ` rguenth at gcc dot gnu.org
2010-10-17 15:51 ` mbuilov at gmail dot com
2010-10-17 16:19 ` mbuilov at gmail dot com

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-46045-4@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).