https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #14
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #13 from Jonathan Wakely ---
(In reply to Patrick Pelissier from comment #12)
> Is the status really "wontfix"?
>
> This makes any C library which uses stdatomic.h incompatible with g++ (and
is not part of the C++ standard.
> more
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
Patrick Pelissier changed:
What|Removed |Added
CC||patrick.pelissier at gmail dot
com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
Sebastian Huber changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #10 from Jonathan Wakely ---
(In reply to Sebastian Huber from comment #9)
> Who guarantees that this definition is binary compatible in C and C++?
The compiler/stdlib implementors.
The same people who you want to guarantee that if y
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #9 from Sebastian Huber ---
(In reply to Jonathan Wakely from comment #5)
> (In reply to Sebastian Huber from comment #4)
> > It is clear that you cannot use C++ header files from C. So if you want to
> > provide a library intended fo
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #8 from Jonathan Wakely ---
(In reply to Sebastian Huber from comment #4)
> I don't think this is the spirit of the atomics provided
> by the recent C/C++ standards.
The atomics are supposed to be roughly source-compatible, in that th
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #7 from Jonathan Wakely ---
(In reply to Sebastian Huber from comment #2)
> With FreeBSD and clang this works fine.
Not on my freebsd host:
$ clang++ -std=c++11 a.cc
In file included from a.cc:5:
/usr/include/stdatomic.h:187:17: erro
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #6 from Jonathan Wakely ---
(In reply to Jonathan Wakely from comment #5)
> #ifdef __cplusplus
> #include
> using namespace std;
> #else
> #include
> #endif
>
> atomic i;
Doh, sorry, that should say atomic_int not atomic
(I changed
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #5 from Jonathan Wakely ---
(In reply to Sebastian Huber from comment #4)
> It is clear that you cannot use C++ header files from C. So if you want to
> provide a library intended for C and C++ applications you must use C as the
> bas
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #4 from Sebastian Huber ---
It is surely not the fault of GCC developers that C and C++ diverge more and
more, but for embedded systems developers this is quite painful.
It is clear that you cannot use C++ header files from C. So if
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #3 from Andrew Pinski ---
(In reply to Sebastian Huber from comment #2)
> So I cannot use C libraries using atomics with C++ on GCC targets? With
> FreeBSD and clang this works fine.
Until the c++ front-end implements _Atomic keyword
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
--- Comment #2 from Sebastian Huber ---
So I cannot use C libraries using atomics with C++ on GCC targets? With
FreeBSD and clang this works fine.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60932
Andrew Pinski changed:
What|Removed |Added
Component|c |c++
Summary| is not C++|ma
14 matches
Mail list logo
