public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sorie at sorie dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/18935] New: Error on reference of 'extern' variable in block scope.
Date: Sat, 11 Dec 2004 00:03:00 -0000	[thread overview]
Message-ID: <20041211000348.18935.sorie@sorie.net> (raw)

This problem occurs in both mode c89 and c99.

I will try to describe it with a simple example.

----- code.c ------------------------------

#include <stdio.h>

int main(void)
{
        extern int a;

        printf("a: %d\n", a);

        int a = 20; /* internal compiler error */

        return 0;
}

-----------------------------------------

If you compile this code, you'll get follwing error message.

$ gcc -Wall -std=c89 code.c
code.c: In function `main':
code.c:7: internal compiler error: in make_decl_rtl, at varasm.c:752

Inside a block scope, the codes are executed sequently.
So I think, when there is a variable declaration with 'extern', that the
compiler should either let occur an error of double variable-declaration or show
warning only and just give the local variable priority.

Thank you for reading.

-- 
           Summary: Error on reference of 'extern' variable in block scope.
           Product: gcc
           Version: 3.4.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: sorie at sorie dot net
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-12-11  0:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-11  0:03 sorie at sorie dot net [this message]
2004-12-11  1:21 ` [Bug c/18935] [3.4 Regression] " pinskia at gcc dot gnu dot 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=20041211000348.18935.sorie@sorie.net \
    --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).