public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/66066] [6 Regression] r222889 causes bogus error: initializer element is not constant Date: Thu, 14 May 2015 11:43:00 -0000 [thread overview] Message-ID: <bug-66066-4-skHfKWgFTH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66066-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66066 --- Comment #18 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Author: mpolacek Date: Thu May 14 11:42:53 2015 New Revision: 223193 URL: https://gcc.gnu.org/viewcvs?rev=223193&root=gcc&view=rev Log: PR c/66066 PR c/66127 * c-common.c (c_fully_fold): Pass false down to c_fully_fold_internal. (c_fully_fold_internal): Fold C_MAYBE_CONST_EXPRs with C_MAYBE_CONST_EXPR_INT_OPERANDS set. Add FOR_INT_CONST argument and use it. If FOR_INT_CONST, require that all evaluated operands be INTEGER_CSTs. * c-typeck.c (digest_init): Call pedwarn_init with OPT_Wpedantic rather than with 0. * gcc.dg/pr14649-1.c: Add -Wpedantic. * gcc.dg/pr19984.c: Likewise. * gcc.dg/pr66066-1.c: New test. * gcc.dg/pr66066-2.c: New test. * gcc.dg/pr66066-3.c: New test. Added: trunk/gcc/testsuite/gcc.dg/pr66066-1.c trunk/gcc/testsuite/gcc.dg/pr66066-2.c trunk/gcc/testsuite/gcc.dg/pr66066-3.c Modified: trunk/gcc/c-family/ChangeLog trunk/gcc/c-family/c-common.c trunk/gcc/c/ChangeLog trunk/gcc/c/c-typeck.c trunk/gcc/testsuite/ChangeLog trunk/gcc/testsuite/gcc.dg/pr14649-1.c trunk/gcc/testsuite/gcc.dg/pr19984.c
next prev parent reply other threads:[~2015-05-14 11:43 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-08 6:04 [Bug c/66066] New: " trippels at gcc dot gnu.org 2015-05-08 7:37 ` [Bug c/66066] " mpolacek at gcc dot gnu.org 2015-05-08 8:11 ` mpolacek at gcc dot gnu.org 2015-05-08 10:49 ` rguenth at gcc dot gnu.org 2015-05-08 10:50 ` rguenth at gcc dot gnu.org 2015-05-09 12:20 ` kugan at gcc dot gnu.org 2015-05-11 13:09 ` vp at gcc dot gnu.org 2015-05-12 9:47 ` rohitarulraj at gmail dot com 2015-05-12 10:22 ` clyon at gcc dot gnu.org 2015-05-12 15:56 ` mpolacek at gcc dot gnu.org 2015-05-12 16:07 ` manu at gcc dot gnu.org 2015-05-12 16:24 ` mpolacek at gcc dot gnu.org 2015-05-12 16:30 ` manu at gcc dot gnu.org 2015-05-12 19:09 ` mpolacek at gcc dot gnu.org 2015-05-13 15:22 ` sje at gcc dot gnu.org 2015-05-13 15:27 ` mpolacek at gcc dot gnu.org 2015-05-14 11:43 ` mpolacek at gcc dot gnu.org [this message] 2015-05-14 11:44 ` mpolacek at gcc dot gnu.org 2015-05-14 11:44 ` mpolacek at gcc dot gnu.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=bug-66066-4-skHfKWgFTH@http.gcc.gnu.org/bugzilla/ \ --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).