Ping - this is still present in 2021a-1+deb11u10 (bullseye).
Also, would it be possible for the "version 2021a" string in
/usr/share/zoneinfo/tzdata.zi to be updated when you backport changes
to that file?
The 2021a-1+deb11u10 version of that file contains a number of
backported changes from 202
Package: tzdata
Version: 2021a-1+deb11u10
Severity: important
Tags: patch
X-Debbugs-Cc: deb...@kayari.org
Dear Maintainer,
* What led up to the situation?
GCC 13 uses the /usr/share/zoneinfo/tzdata.zi file to implement support for
the C++20 time zone library.
* What exactly did you do (or
This is https://sourceforge.net/p/mingw-w64/bugs/778/
A minimal reproducer:
#ifdef STDDEF_FIRST
# include
#endif
#include
static_assert( alignof(max_align_t) == 16 );
$ x86_64-w64-mingw32-g++ -c max.cc -m32 && echo ok
ok
$ x86_64-w64-mingw32-g++ -c max.cc -m32 -DSTDDEF_FIRST && echo ok
max.cc:6:37: error: static assertion failed
6 | static
On 23/04/20 09:23 +0100, Jonathan Wakely wrote:
On 23/04/20 06:32 +0200, Helmut Grohne wrote:
Hi,
On Mon, Apr 20, 2020 at 10:12:37AM +0100, Jonathan Wakely wrote:
Now you are probably going to say that "-isystem /usr/include" is a bad
idea and that you shouldn't do that.
On 23/04/20 06:32 +0200, Helmut Grohne wrote:
Hi,
On Mon, Apr 20, 2020 at 10:12:37AM +0100, Jonathan Wakely wrote:
> Now you are probably going to say that "-isystem /usr/include" is a bad
> idea and that you shouldn't do that.
Right.
> I'm inclined to agree. Th
On 20/04/20 07:01 +0200, Helmut Grohne wrote:
The and headers need their counter parts and
from the libc respectively, but libstdc++ wraps these
headers. Now and include these headers using
$ echo '#include ' | g++ -x c++ -E - -isystem /usr/include >/dev/null
In file included from :1:
/usr
On 30 November 2016 at 08:04, Eugene Seliverstov wrote:
> Just a note that initial ubsan error cannot be reproduced for 0.8.0 and 0.8.1
> with the latest sid compiler (6.2), jessie compiler (4.8) and clang (3.8).
> Seems like the bug #65049 exists only for gcc 5.3 and 6.0.
No, as it says there, t
Fixed in the pstreams git repo, I'm going to make a 1.0.0 release soon.
I'll fix char_traits in libstdc++ soon too.
On 23 August 2015 at 19:06, Jakub Wilk wrote:
> Apparently Pstreams calls std::char_traits::move() with destination buffer
> set to NULL, which is undefined behavior even when length is 0.
No it isn't, the C++ standard places no requirements on the arguments
to char_traits::move.
The fact that ch
10 matches
Mail list logo