public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: dima@cc.hut.fi To: gcc-gnats@gcc.gnu.org Subject: c/5336: initializer element is not constant Date: Wed, 09 Jan 2002 08:36:00 -0000 [thread overview] Message-ID: <20020109163325.27629.qmail@sources.redhat.com> (raw) >Number: 5336 >Category: c >Synopsis: initializer element is not constant >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: rejects-legal >Submitter-Id: net >Arrival-Date: Wed Jan 09 08:36:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: dima@cc.hut.fi >Release: 2.96 (*g*), 3.0.1 >Organization: >Environment: >Description: compiler exits with error on code which is legal at least in common sense. when comiling something like: int * const ptr1 = (int *) 0xf0f0f0f0; int * const ptr2 = ptr1; compiler exits with error "initializer element is not constant", although it sorta is. it's not "a constant", but it sure is "constant". I'll go dig C docs, if it is indeed so that init element must be "a constant expression" then a change of error message would be good. >How-To-Repeat: int * const ptr1 = (int *) 0xf0f0f0f0; int * const ptr2 = ptr1; >Fix: >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2002-01-09 16:36 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-01-09 8:36 dima [this message] 2002-04-29 13:46 Luben Tuikov 2002-04-29 18:25 rth
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=20020109163325.27629.qmail@sources.redhat.com \ --to=dima@cc.hut.fi \ --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: linkBe 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).