public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: RDahlsted@aol.com
To: gcc-gnats@gcc.gnu.org
Subject: c/4142: gcc compiles C code with assignments to const variables
Date: Mon, 27 Aug 2001 11:06:00 -0000	[thread overview]
Message-ID: <20010827175823.4551.qmail@sourceware.cygnus.com> (raw)

>Number:         4142
>Category:       c
>Synopsis:       gcc compiles C code with assignments to const variables
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Aug 27 11:06:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Richard Dahlstedt
>Release:        gcc-2.7.2, gcc-2.95.2
>Organization:
>Environment:
Solaris 2.5 (gcc-2.7.2), Solaris 5.7 (gcc-2.95.2)
>Description:
    When compiling C code, this apparently is resolved when using g++ instead of gcc or when compiling C++ code through gcc (as it presumably will call g++), gcc will issue a warning about assignment to a const variable but will allow this to occur any way and create the executable.  Even when using the -ansi and -pedantic flags gcc will still create the executable with assignments being made to the const variable.  Unless I am missing something about the C standard and other C/C++ compiler vendors apparently agree with me, in that there products do not allow such to occur, I would like to know why gcc allows this C-specific issue to occur.
>How-To-Repeat:
#include <stdio.h>

void main(void)
{
  const int i = 0;

  i = 1;

  printf("i = %i\n", i);

  i = 2;

  printf("i = %i\n", i);
}
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2001-08-27 11:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-27 11:06 RDahlsted [this message]
2002-02-24  9:34 rodrigc

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=20010827175823.4551.qmail@sourceware.cygnus.com \
    --to=rdahlsted@aol.com \
    --cc=gcc-gnats@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).