This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/53091] Const assignment fails in GCC 4.2, 4.4, 4.6, 4.7 - works fine in clang
- From: "manu at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 23 Apr 2012 19:25:26 +0000
- Subject: [Bug c/53091] Const assignment fails in GCC 4.2, 4.4, 4.6, 4.7 - works fine in clang
- Auto-submitted: auto-generated
- References: <bug-53091-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53091
Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
URL|http://m8y.org/tmp/gcc_bug. |
|c |
CC| |jsm28 at gcc dot gnu.org,
| |manu at gcc dot gnu.org
Resolution|INVALID |
--- Comment #5 from Manuel LÃpez-IbÃÃez <manu at gcc dot gnu.org> 2012-04-23 19:25:26 UTC ---
(In reply to comment #3)
> Anyway, I take it this is a "Won't Fix" ?
Not sure why. If Clang is allowed by the C standard, then surely GCC is allowed
as well. If the C++ FE has code to enable this, probably it can be reused in
the C FE. GCC could accept it with a -Wpedantic warning.
In any case, like everything, it boils down to having someone make it happen,
that is, providing a patch. I don't think any existing GCC developer will
tackle this in the near future, otherwise it would have been done already.
But let's wait for Joseph opinion to confirm this.