Hello,
On Tue, 9 Feb 2016 19:55:50 +0100, Max Kellermann wrote:
> On 2016/02/07 22:11, Thomas Petazzoni
> wrote:
> > The mpd source code uses the C++11 functionality, which
> > internally is implemented using the __atomic_*() gcc built-ins. On
> > certain architectures, the __atomic_*() built-i
On 2016/02/09 21:03, François Revol wrote:
> Why that, it's always been so for libstdc++, libsupc++, libgcc... ok
> maybe not libgcc.
I have never used "-lstdc++ -lsupc++ -lgcc" - gcc/g++ will
automatically link those libraries. These APIs are part of the
language standard, so I expect them to b
On 09/02/2016 19:55, Max Kellermann wrote:
> On 2016/02/07 22:11, Thomas Petazzoni
> wrote:
>> The mpd source code uses the C++11 functionality, which
>> internally is implemented using the __atomic_*() gcc built-ins. On
>> certain architectures, the __atomic_*() built-ins are implemented in
>>
On 2016/02/07 22:11, Thomas Petazzoni
wrote:
> The mpd source code uses the C++11 functionality, which
> internally is implemented using the __atomic_*() gcc built-ins. On
> certain architectures, the __atomic_*() built-ins are implemented in
> the libatomic library that comes with the rest of t
The mpd source code uses the C++11 functionality, which
internally is implemented using the __atomic_*() gcc built-ins. On
certain architectures, the __atomic_*() built-ins are implemented in
the libatomic library that comes with the rest of the gcc runtime. Due
to this, code using might need to
