This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/62024] __atomic_always_lock_free is not a constant expression
- From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 13 Aug 2014 05:21:58 +0000
- Subject: [Bug c/62024] __atomic_always_lock_free is not a constant expression
- Auto-submitted: auto-generated
- References: <bug-62024-4 at http dot gcc dot gnu dot org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62024
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2014-08-13
CC| |mpolacek at gcc dot gnu.org
Target Milestone|--- |4.10.0
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed even for C++. The issue is the same: fold folds
__atomic_always_lock_free to 1, but that 1 is wrapped in NOP_EXPR - and static
assert code is unhappy. I think we can just STRIP_TYPE_NOPS - we don't expect
an lvalue in the static assert code. I'm testing a patch for that.
Not a regression.