This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/72865] Adding __may_alias__ attribute triggers a compilation error
- From: "root at zta dot lk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 10 Aug 2016 15:05:14 +0000
- Subject: [Bug c++/72865] Adding __may_alias__ attribute triggers a compilation error
- Auto-submitted: auto-generated
- References: <bug-72865-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72865
--- Comment #2 from Aleksej Lebedev <root at zta dot lk> ---
Just tried it with gcc-6.0.0 under DragonflyBSD. It seems that the bug is
fixed.
$ uname -a
DragonFly kl.zta.lk 4.4-RELEASE DragonFly v4.4.3.1.gf6df7-RELEASE #8: Thu Apr
21 17:59:21 CEST 2016 root@kl.zta.lk:/usr/obj/usr/src/sys/X86_64_GENERIC
x86_64
$ g++6 --version
g++6 (FreeBSD Ports Collection) 6.0.0 20160410 (experimental)
Copyright (C) 2016 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ $ g++6 sf.cpp -c
$ echo $?
0
Not sure what's your policy in this case. You decide if you want to close this
as "Won't fix", but this bug prevents us from using boost::move for classes
with move constructors (in some cases).