public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Joseph Myers <jsm28@cam.ac.uk>
To: gcc-gnats@gcc.gnu.org
Cc: jsm28@cam.ac.uk
Subject: c/5675: const variables wrongly considered part of constant expressions
Date: Tue, 12 Feb 2002 13:46:00 -0000	[thread overview]
Message-ID: <E16akg9-0007cw-00@jsm28.trin.cam.ac.uk> (raw)


>Number:         5675
>Category:       c
>Synopsis:       const variables wrongly considered part of constant expressions
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Tue Feb 12 13:46:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Joseph S. Myers
>Release:        3.1 20020212 (experimental)
>Organization:
none
>Environment:
System: Linux digraph 2.2.20 #2 Sat Nov 10 16:44:22 UTC 2001 i686 unknown
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ../gcc-cvs/configure --prefix=/opt/gcc/mainline --disable-shared --enable-threads=posix --with-system-zlib
>Description:

In some circumstances, GCC wrongly accepts const variables as part of
constant expressions when compiling C.

>How-To-Repeat:

The XFAILing tests in gcc.dg/c9[09]-const-expr-3.c.

>Fix:

Fixing the underlying problems associated with
decl_constant_value_for_broken_optimization, moving such optimizations
until after all constraint checking, might help.  Or keep proper track
for every subexpression of whether it is a constant expression (see
also c/456).
>Release-Note:
>Audit-Trail:
>Unformatted:


                 reply	other threads:[~2002-02-12 21:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=E16akg9-0007cw-00@jsm28.trin.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --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).