public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/53091] Const assignment fails in GCC 4.2, 4.4, 4.6, 4.7 - works fine in clang
Date: Tue, 24 Apr 2012 14:25:00 -0000	[thread overview]
Message-ID: <bug-53091-4-qw75cgPIzW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53091-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53091

--- Comment #12 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2012-04-24 14:25:06 UTC ---
There is no requirement to accept this static initializer, but the code 
does try to be lax about constants in initializers (there is no 
requirement to reject it either) and fold them with c_fully_fold (see 
c-typeck.c:digest_init).  So it may make sense to look at why this laxity 
isn't causing this code to be accepted.


  parent reply	other threads:[~2012-04-24 14:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 18:24 [Bug c/53091] New: " bugs at m8y dot org
2012-04-23 18:25 ` [Bug c/53091] " bugs at m8y dot org
2012-04-23 18:39 ` redi at gcc dot gnu.org
2012-04-23 19:00 ` bugs at m8y dot org
2012-04-23 19:20 ` schwab@linux-m68k.org
2012-04-23 19:25 ` manu at gcc dot gnu.org
2012-04-23 19:35 ` bugs at m8y dot org
2012-04-23 19:43 ` pinskia at gcc dot gnu.org
2012-04-23 19:57 ` bugs at m8y dot org
2012-04-23 20:37 ` schwab@linux-m68k.org
2012-04-23 20:50 ` redi at gcc dot gnu.org
2012-04-23 21:01 ` bugs at m8y dot org
2012-04-24 14:25 ` joseph at codesourcery dot com [this message]
2012-04-24 14:38 ` [Bug c/53091] static initializer accepted by clang but not by gcc manu at gcc dot gnu.org
2012-04-24 15:01 ` bugs at m8y dot org
2012-05-30 16:23 ` schwab@linux-m68k.org
2021-09-12 21:28 ` pinskia 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-53091-4-qw75cgPIzW@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: 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).