public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/5675] [4.0 regression] const variables wrongly considered part of constant expressions Date: Mon, 17 Jan 2005 18:54:00 -0000 [thread overview] Message-ID: <20050117185435.12231.qmail@sourceware.org> (raw) In-Reply-To: <20020212134602.5675.jsm28@gcc.gnu.org> ------- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-01-17 18:54 ------- Subject: Bug 5675 CVSROOT: /cvs/gcc Module name: gcc Changes by: ian@gcc.gnu.org 2005-01-17 18:54:21 Modified files: gcc : ChangeLog c-typeck.c Log message: PR c/5675 * c-typeck.c (build_c_cast): Revert patch of 2003-02-16: don't fold constant variables into initial values. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ChangeLog.diff?cvsroot=gcc&r1=2.7155&r2=2.7156 http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/c-typeck.c.diff?cvsroot=gcc&r1=1.407&r2=1.408 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=5675
next prev parent reply other threads:[~2005-01-17 18:54 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20020212134602.5675.jsm28@gcc.gnu.org> 2005-01-13 2:34 ` ian at airs dot com 2005-01-13 15:16 ` ian at airs dot com 2005-01-17 18:54 ` cvs-commit at gcc dot gnu dot org [this message] 2005-01-17 18:56 ` cvs-commit at gcc dot gnu dot org 2005-01-17 18:57 ` [Bug c/5675] " ian at airs dot com 2005-01-24 0:08 ` pinskia at gcc dot gnu dot org 2005-04-25 2:09 ` pinskia at gcc dot gnu dot org 2005-06-30 13:31 ` [Bug c/5675] const variables wrongly considered part of constant expressions (gcc.dg/c9[09]-const-expr-3.c) pinskia at gcc dot gnu dot org [not found] <20020212134602.5675.jsm-gccbugs@polyomino.org.uk> 2004-10-25 2:21 ` [Bug c/5675] [4.0 regression] const variables wrongly considered part of constant expressions geoffk at gcc dot gnu dot org 2004-10-25 2:34 ` 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=20050117185435.12231.qmail@sourceware.org \ --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: 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).