Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/bits/alloc_traits.h (allocate): Add [[maybe_unused]]
attribute.
* include/bits/regex_executor.tcc: Remove name of unused
parameter.
* include/bits/shared_ptr_atomic.h
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/std/format: Fix some warnings.
(__format::__write(Ctx&, basic_string_view)): Remove
unused function template.
---
libstdc++-v3/include/std/format | 28 +---
1 file
On Thu, 13 Jul 2023 at 03:41, Ken Matsui via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> This patch gets std::is_function to dispatch to new built-in trait
> __is_function.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_function): Use __is_function built-in
> trait.
On Tue, 18 Jul 2023 at 08:44, Ken Matsui via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> This patch optimizes the performance of the is_compound trait by
> dispatching to the new __is_arithmetic built-in trait.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_compound): Use
On Tue, 8 Aug 2023 at 21:09, Jonathan Wakely wrote:
>
>
> On Sat, 15 Jul 2023 at 05:57, Ken Matsui via Libstdc++ <
> libstd...@gcc.gnu.org> wrote:
>
>> This patch optimizes the performance of the is_arithmetic trait by
>> dispatching to the new __is_arithmetic b
On Wed, 19 Jul 2023 at 20:33, Ken Matsui via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> This patch defines _GLIBCXX_HAS_BUILTIN_TRAIT macro, which will be used
> as a flag to toggle the use of built-in traits in the type_traits header
> through _GLIBCXX_NO_BUILTIN_TRAITS macro, without needing
On Wed, 19 Jul 2023 at 19:48, Patrick Palka via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> On Tue, 18 Jul 2023, Ken Matsui via Libstdc++ wrote:
>
> > This patch defines _GLIBCXX_HAS_BUILTIN_TRAIT, which will be used as a
> > flag to toggle built-in traits in the type_traits header. Through this
On Tue, 18 Jul 2023 at 07:25, Ken Matsui via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> Hi,
>
> I took a benchmark for this.
>
>
> https://github.com/ken-matsui/gcc-benches/blob/main/is_fundamental-disjunction.md#mon-jul-17-105937-pm-pdt-2023
>
> template
> struct is_fundamental
> : public
On Tue, 18 Jul 2023 at 07:28, Ken Matsui via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> I will eventually work on disjunction to somehow optimize, but in the
> meantime, this might be a better implementation. Of course, my
> benchmark could be wrong.
>
You should use __or_ internally in
On Sat, 15 Jul 2023 at 05:57, Ken Matsui via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> This patch optimizes the performance of the is_arithmetic trait by
> dispatching to the new __is_arithmetic built-in trait.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_arithmetic):
On Sat, 15 Jul 2023 at 04:02, Ken Matsui via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> This patch uses __bool_constant entirely instead of integral_constant
> in the type_traits header, specifically for true_type, false_type,
> and bool_constant.
>
> libstdc++-v3/ChangeLog:
>
> *
On Sat, 22 Jul 2023 at 14:51, François Dumont via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
>
> On 18/07/2023 08:27, Ken Matsui via Libstdc++ wrote:
> > This patch implements built-in trait for std::is_arithmetic.
> >
> > gcc/cp/ChangeLog:
> >
> > * cp-trait.def: Define __is_arithmetic.
> >
Tested x86_64-linux. Pushed to trunk. gcc-13 backport to follow.
-- >8 --
We can't write to a span<_CharT> if the contiguous iterator has a value
type that isn't _CharT.
libstdc++-v3/ChangeLog:
PR libstdc++/110917
* include/std/format (__format::_Iter_sink):
Constrain
Tested x86_64-linux. Pushed to trunk. gcc-13 backport to follow.
-- >8 --
The std::formatter implementation for floating-point types uses
__builtin_abs and __builtin_log10 to avoid including all of , but
those functions are not generic. The result of abs(2e304) is -INT_MIN
which is undefined,
Committed as obvious.
Less obvious (to me) is whether it's correct to say "GCC V13" here. I
don't think we refer to a version that way anywhere else, do we?
Would "since GCC 13.1.0" be better?
-- >8 --
gcc/ChangeLog:
* config/i386/i386.cc (ix86_invalid_conversion): Fix grammar.
---
Tested x86_64-linux. Pushed to trunk. gcc-13 backport to follow.
-- >8 --
At the end of a replacement field we should check that the closing brace
is actually present before incrementing past it.
libstdc++-v3/ChangeLog:
PR libstdc++/110862
* include/std/format
On Sun, 30 Jul 2023 at 14:55, François Dumont via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> Committed as obvious.
>
> libstdc++: Fix several preprocessor directives
>
> A wrong usage of #define in place of a #error seems to have been
> replicated
> at different places in source
Tested x86_64-linux. Pushed to trunk. Backport to gcc-13 to follow.
-- >8 --
A decimal point was being added to the end of the string for {:#.0}
because the __expc character was not being set, for the _Pres_none
presentation type, so __s.find(__expc) didn't the 'e' in "1e+01" and so
we created
Pushed to trunk.
-- >8 --
This new test uses uniform initialization syntax, so requires C++11 or
later.
libstdc++-v3/ChangeLog:
PR libstdc++/110807
* testsuite/23_containers/vector/bool/110807.cc: Require c++11.
---
libstdc++-v3/testsuite/23_containers/vector/bool/110807.cc |
Tested x86_64-linux. Pushed to trunk. Backport to gcc-13 will come after
the 13.2 release.
-- >8 --
GCC thinks the allocation can alter the object being copied if it's
globally reachable, so doesn't realize that [x.begin(), x.end()) after
the allocation is the same as x.size() before it.
This
Tested x86_64-linux. Pushed to trunk.
Probably worth backporting to 12 and 13.
-- >8 --
We already have these attributes on the definitions in
but they don't work due to PR c++/84542. Add the attributes to the
declarations in as well, and add a test.
libstdc++-v3/ChangeLog:
*
On 23/07/23 20:28 -0700, Deev Patel wrote:
Hi,
A couple of virtual functions in the libstdc++ format header are marked
constexpr in the base class, but not in the derived class. This was causing
build failures when trying to compile latest gcc libstd with clang 16 using
c++20. Adding the
This seems like a worthwhile change. In theory we could make it even
smaller by using a symbol alias, but I'm not sure that's supported on
the targets where this will actually help.
Any objections?
-- >8 --
For targets where double and long double have the same representation we
can reuse the
Tested x86_64-linux, pushed to trunk.
I hope this bug can be closed now, ut will have to wait for Dave Angling
to post results.
-- >8 --
When I switched std::stold to depend on HAVE_STRTOLD that enabled it for
hppa-hpux which defines HAVE_BROKEN_STRTOLD. Add a check for that macro
so that we
Tested x86_64-linux and sparc-solaris. Pushed to trunk.
-- >8 --
I think r14-1431-g7037e7b6e4ac41 was wrong to try to define the
_Float128 overload unconditionally. Not all targets need it, so defining
the lossy fallback using long double is not useful (and caused an ABI
change on Solaris x86).
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The standard says that it should be ill-formed to use std::ratio_equal
etc. with types which are not specializations of std::ratio. This
implements that requirement.
We don't need to add assertions to every one of the class templates,
because many
I'm testing this patch for gcc-13 as a better fix for PR109921, without
the breakage that r14-1431-g7037e7b6e4ac41 caused on trunk.
If testing goes well I'll push this before the 13.2 release candidate.
-- >8 --
We use the from_chars_strtod function with __strtof128 to read a
_Float128 value,
Tested x86_64-linux. Pushed to trunk.
-- >8 --
When formatting with an empty chrono spec ("{}") two minus signs were
being added to hh_mm_ss values. This is because the __is_neg flag was
checked to add one explicitly, and then the ostream operator added
another one.
We should only check the
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The r14-2640-gf4bce119f617dc commit only removed fractional seconds for
time points, but it needs to be done for durations and hh_mm_ss types
too.
libstdc++-v3/ChangeLog:
PR libstdc++/110719
* include/bits/chrono_io.h
Tested x86_64-linux. Pushed to trunk.
-- >8 --
With -Wmaybe-uninitialized -Wsystem-headers there's a warning about
creating a string_view from an uninitalized array. Initializing the
first element of the array avoids the warning.
libstdc++-v3/ChangeLog:
* include/std/format
Tested x86_64-linux. Pushed to trunk.
I'll backport it to gcc-13 some time after the 13.2 release.
-- >8 --
This fixes some TODOs in the C++20 format support, where the
locale-specific output was incorrect or unimplemented. The approach
taken here is to either use the formatting locale's
Tested x86_64-linux. Pushed to trunk.
This should be backported to gcc-13 too, but it can wait until 13.3
(it's just an accepts-invalid and unlikely to affect anybody in
practice).
-- >8 --
The logic for handling modified chrono specs like %Ey was just
restarting the loop after each modifier,
Tested x86_64-linux. Pushed to trunk.
-- >8 --
For targets without std::strtof we can define std::stof by calling
std::stod and then checking if the result is out of range of float.
libstdc++-v3/ChangeLog:
PR libstdc++/110653
* include/bits/basic_string.h
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Since the narrow string versions of std::stoi, std::stol, std::stoul,
std::stof and std::stod are now always defined, we don't need to check
dg-require-string-conversions in the relevant tests.
libstdc++-v3/ChangeLog:
PR libstdc++/110653
Tested x86_64-linux. Pushed to trunk.
-- >8 --
As well as the _GLIBCXX_USE_C99_STDLIB check, we also have a separate
check in linkage.m4 for just strtof and strtold. We can use that to
declare std::strtof and std::strtold in for additional
targets. That allows us to enable std::stold on
On Fri, 14 Jul 2023 at 11:48, Jonathan Wakely wrote:
>
> On Thu, 13 Jul 2023 at 21:04, Ken Matsui wrote:
> >
> > On Thu, Jul 13, 2023 at 2:22 AM Jonathan Wakely wrote:
> > >
> > > On Wed, 12 Jul 2023 at 21:42, Ken Matsui
> > > wrote:
> > &
On Thu, 13 Jul 2023 at 21:04, Ken Matsui wrote:
>
> On Thu, Jul 13, 2023 at 2:22 AM Jonathan Wakely wrote:
> >
> > On Wed, 12 Jul 2023 at 21:42, Ken Matsui wrote:
> > >
> > > On Wed, Jul 12, 2023 at 3:01 AM Jonathan Wakely
> > > wrote:
> > &
Tested powerpc64le-linux. Pushed to trunk.
-- >8 --
std::stoi, std::stol, std::stoul, and std::stod only depend on C89
functions, so don't need to be guarded by _GLIBCXX_USE_C99_STDLIB
std::stoll and std::stoull don't need C99 strtoll and strtoull if
sizeof(long) == sizeof(long long).
On Wed, 12 Jul 2023 at 21:42, Ken Matsui wrote:
>
> On Wed, Jul 12, 2023 at 3:01 AM Jonathan Wakely wrote:
> >
> > On Mon, 10 Jul 2023 at 06:51, Ken Matsui via Libstdc++
> > wrote:
> > >
> > > Hi,
> > >
> > > Here is the benchmark resu
Tested powerp64le-linux. Pushed to trunk. This can be backported too.
-- >8 --
The testcase added for this bug only checks conversion from wide strings
on construction, but the fix also covered conversion to wide stings via
path::wstring(). Add checks for that, and u16string() and u32string().
On Wed, 12 Jul 2023, 19:33 Ken Matsui via Libstdc++,
wrote:
> On Wed, Jul 12, 2023 at 2:50 AM Jonathan Wakely
> wrote:
> >
> > On Sat, 8 Jul 2023 at 05:47, Ken Matsui via Libstdc++
> > wrote:
> > >
> > > This patch gets std::is_scalar to dispat
On Sat, 8 Jul 2023 at 06:31, Ken Matsui via Libstdc++
wrote:
>
> This patch lets libstdc++ use new built-in trait __remove_pointer.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (remove_pointer): Use __remove_pointer
> built-in trait.
>
> Signed-off-by: Ken Matsui
OK for
On Sun, 9 Jul 2023 at 09:50, Ken Matsui via Libstdc++
wrote:
>
> This patch implements built-in trait for std::is_signed.
>
> gcc/cp/ChangeLog:
>
> * cp-trait.def: Define __is_signed.
> * constraint.cc (diagnose_trait_expr): Handle CPTK_IS_SIGNED.
> * semantics.cc
On Sat, 8 Jul 2023 at 06:15, Ken Matsui via Libstdc++
wrote:
>
> This patch gets std::is_function to dispatch to new built-in trait
> __is_function.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_function): Use __is_function built-in
> trait.
>
On Sat, 8 Jul 2023 at 06:13, Ken Matsui via Libstdc++
wrote:
>
> This patch gets std::is_reference to dispatch to new built-in trait
> __is_reference.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_reference): Use __is_reference built-in
> trait.
>
On Sat, 8 Jul 2023 at 12:14, Ken Matsui via Libstdc++
wrote:
>
> This patch lets libstdc++ use new built-in trait __is_unsigned.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_unsigned): Use __is_unsigned built-in
> trait.
> (is_unsigned_v): Likewise.
>
>
On Sun, 9 Jul 2023 at 09:50, Ken Matsui via Libstdc++
wrote:
>
> This patch lets libstdc++ use new built-in trait __is_signed.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_signed): Use __is_signed built-in trait.
> (is_signed_v): Likewise.
>
> Signed-off-by: Ken
On Mon, 10 Jul 2023 at 06:51, Ken Matsui via Libstdc++
wrote:
>
> Hi,
>
> Here is the benchmark result for is_pointer:
>
> https://github.com/ken-matsui/gcc-benches/blob/main/is_pointer.md#sun-jul--9-103948-pm-pdt-2023
>
> Time: -62.1344%
> Peak Memory Usage: -52.4281%
> Total Memory Usage:
On Sat, 8 Jul 2023 at 05:50, Ken Matsui via Libstdc++
wrote:
>
> This patch replaces is_enum::value with __is_enum built-in trait in
> the type_traits header.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (__make_unsigned_selector): Use
> __is_enum built-in trait.
>
On Sat, 8 Jul 2023 at 05:47, Ken Matsui via Libstdc++
wrote:
>
> This patch gets std::is_scalar to dispatch to new built-in trait
> __is_scalar.
>
> libstdc++-v3/ChangeLog:
>
> * include/std/type_traits (is_scalar): Use __is_scalar built-in
> trait.
> (is_scalar_v):
On Mon, 10 Jul 2023 at 06:24, Ken Matsui via Libstdc++
wrote:
>
> This patch implements built-in trait for std::is_pointer.
>
> gcc/cp/ChangeLog:
>
> * cp-trait.def: Define __is_pointer.
> * constraint.cc (diagnose_trait_expr): Handle CPTK_IS_POINTER.
> * semantics.cc
On Wed, 12 Jul 2023 at 05:41, François Dumont via Libstdc++
wrote:
>
>
> On 10/07/2023 07:23, Ken Matsui via Libstdc++ wrote:
> > This patch implements built-in trait for std::is_pointer.
> >
> > gcc/cp/ChangeLog:
> >
> > * cp-trait.def: Define __is_pointer.
> > * constraint.cc
On Wed, 28 Jun 2023 at 08:56, Jan Hubicka wrote:
>
> > I think the __throw_bad_alloc() and __throw_bad_array_new_length()
> > functions should always be rare, so marking them cold seems fine (users who
> > define their own allocators that want to throw bad_alloc "often" will
> > probably throw it
Pushed as obvious.
-- >8 --
gcc/ChangeLog:
PR c++/110595
PR c++/110596
* doc/invoke.texi (Warning Options): Fix typos.
---
gcc/doc/invoke.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
index
When this code was written we didn't have the
header, so it conditionally used lseek64 etc.
Since this is compiled into the library, not inline code in headers, we
can just define the relevant macros to get a 64-bit off_t and then
simplify the code.
Tested x86_64-linux. I intend to commit this
Tested x86_64-linux (with --enable-cstdio=stdio_pure and without).
I intend to commit this next week.
This fixes most of the fstream failures seen with stdio_pure, although
there are still a few that fail (about half of them time out):
FAIL: 27_io/basic_filebuf/imbue/char/13171-2.cc execution
Pushed to trunk. Backports to 11, 12 and 13 will follow.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/110574
* doc/xml/manual/configure.xml: Describe stdio_pure argument to
--enable-cstdio.
* doc/html/manual/configure.html: Regenerate.
---
5db..fa551c5f900 100644
--- a/gcc/doc/contrib.texi
+++ b/gcc/doc/contrib.texi
@@ -1095,8 +1095,7 @@ Todd Vierling for contributions for NetBSD ports.
Andrew Waterman for contributing the RISC-V port, as well as maintaining it.
@item
-Jonathan Wakely for contributing libstdc++ Doxygen notes and XH
On Wed, 5 Jul 2023 at 16:54, shuaitq via Libstdc++
wrote:
>
> the first parameter of fwrite should be the const char* __s which want write
> to FILE *__file,
> rather than the FILE *__file write to the FILE *__file.
Thank you. The patch is correct and small enough to not require a
copyright
Tested x86_64-linux. Pushed to trunk.
-- >8 --
These tests fail with -std=gnu++98/-D_GLIBCXX_DEBUG in the runtest
flags. They should require the c++11 effective target.
libstdc++-v3/ChangeLog:
* testsuite/23_containers/forward_list/debug/iterator1_neg.cc:
Skip as UNSUPPORTED
This is a weird one as described in the PR. GCC doesn't complain about
this bug, but seems to have a bogus error elsewhere. I'll add a testcase
once I've understood/fixed the GCC error.
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/110542
*
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Similar to r14-2052-gdd2eb972a5b063, replace the try-block with RAII
types for deallocating storage and destroying elements.
libstdc++-v3/ChangeLog:
* include/bits/vector.tcc (_M_default_append): Replace try-block
with RAII types.
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This is needed by Clang 15.
libstdc++-v3/ChangeLog:
* include/bits/iterator_concepts.h (projected): Add typename.
---
libstdc++-v3/include/bits/iterator_concepts.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Mon, 3 Jul 2023 at 23:14, Thomas Rodgers via Libstdc++
wrote:
>
> This testcase is causing some timeout issues. This patch splits the
> testcase up by individual set algorithm.
I think the Apache license requires a notice saying the original file
was modified. A comment in each new file
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The header is only supported for the cxx11 ABI. The
declarations of basic_syncbuf, basic_osyncstream, syncbuf and
osyncstream were already correctly guarded by a check for
_GLIBCXX_USE_CXX11_ABI, but the wsyncbuf and wosyncstream declarations
were
Pushed to trunk now.
On Fri, 30 Jun 2023 at 21:17, Jonathan Wakely via Libstdc++
wrote:
>
> Jakub made a similar change a few yeas ago, but I think it got lost
> in the recent PSTL rebase.
>
> Tested x86_64-linux.
>
> Does this look OK for trunk?
>
> -- >8
Tested x86_64-linux. Pushed to trunk.
This isn't a regression, but is safe to backport.
-- >8 --
These calls should be qualified to prevent ADL, which can cause errors
for incomplete types that are associated classes.
libstdc++-v3/ChangeLog:
* include/bits/alloc_traits.h (_Destroy):
Jakub made a similar change a few yeas ago, but I think it got lost
in the recent PSTL rebase.
Tested x86_64-linux.
Does this look OK for trunk?
-- >8 --
This reapplies r10-1314-g32bab8b6ad0a90 which was lost in the recent
PSTL rebase from upstream.
* include/pstl/pstl_config.h
On Fri, 30 Jun 2023 at 15:29, Patrick Palka wrote:
>
> On Fri, 30 Jun 2023, Jonathan Wakely wrote:
>
> > Tested x86_64-linux. Patrick, PTAL.
> >
> > -- >8 --
> >
> > The __has_attribute(init_priority) check in is true for Clang
> > on darw
Tested powerpc64le-linux and x86_64-linux. Pushed to trunk.
-- >8 --
This newly-introduced variable isn't used on all paths, so add the
[[maybe_unused]] attribute.
libstdc++-v3/ChangeLog:
* src/c++11/random.cc (random_device::_M_init): Add maybe_unused
attribute.
---
Tested x86_64-linux. Patrick, PTAL.
-- >8 --
The __has_attribute(init_priority) check in is true for Clang
on darwin, which means that user code including thinks the
library will initialize the global streams. However, when libstdc++ is
built by GCC on darwin, the
Tested x86_64-linux. Pushed to trunk.
-- >8 --
In r14-289-gf9412cedd6c0e7 I made the std::random_device constructor
throw std::system_error for unrecognized tokens. But it still throws
std::runtime_error for a token such as "rdseed" that is recognized but
not supported at runtime by the CPU the
On Fri, 30 Jun 2023 at 09:42, Jonathan Wakely wrote:
>
> On Fri, 30 Jun 2023 at 04:48, Hans-Peter Nilsson wrote:
> >
> > > Date: Mon, 26 Jun 2023 11:57:49 -0700
> > > From: Thomas Rodgers via Gcc-patches
> >
> > > On Wed, May 17, 2023 at 12:32
On Fri, 30 Jun 2023 at 04:48, Hans-Peter Nilsson wrote:
>
> > Date: Mon, 26 Jun 2023 11:57:49 -0700
> > From: Thomas Rodgers via Gcc-patches
>
> > On Wed, May 17, 2023 at 12:32 PM Jonathan Wakely wrote:
> > > All the actual code changes look good.
>
>
On Thu, 29 Jun 2023 at 17:59, Tom Tromey wrote:
> >>>>> Jonathan Wakely writes:
>
> > Looks good. OK for trunk, and OK to backport after some soak time on
> trunk. Thanks.
>
> AdaCore doesn't need a backport of this, and I don't think it's
> extremely
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Although the copy_file_range(2) man page shows the arguments as off64_t*
that is not portable. For musl there is no off64_t type, as off_t is
always 64-bit. Use the loff_t type which is always 64-bit even if off_t
isn't. We could just use off_t
This build failure for riscv32-esp-elf was "reported" on the gcc-help list:
https://gcc.gnu.org/pipermail/gcc-help/2023-June/142641.html
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Building libstdc++ reportedly fails for targets without lock-free
std::atomic which don't define
On Thu, 1 Jun 2023 at 12:05, Jonathan Wakely wrote:
> On Thu, 1 Jun 2023 at 10:30, Christophe Lyon via Libstdc++
> wrote:
> >
> > Hi,
> >
> >
> > On Wed, 31 May 2023 at 14:25, Jonathan Wakely via Gcc-patches <
> > gcc-patches@gcc.gnu.org> w
On Wed, 28 Jun 2023 at 16:58, Tom Tromey via Libstdc++ <
libstd...@gcc.gnu.org> wrote:
> The libstdc++ test suite checks whether gdb type printers are
> available like so:
>
> set do_whatis_tests [gdb_batch_check "python print(gdb.type_printers)"
> \
>"\\\[\\\]"]
>
On Wed, 28 Jun 2023 at 08:56, Jan Hubicka wrote:
> > I think the __throw_bad_alloc() and __throw_bad_array_new_length()
> > functions should always be rare, so marking them cold seems fine (users
> who
> > define their own allocators that want to throw bad_alloc "often" will
> > probably throw it
Tested x86_64-linux. Pushed to trunk.
-- >8 --
The formatter for pointers was casting to uint64_t which sign extends a
32-bit pointer and produces a value that won't fit in the provided
buffer. Cast to uintptr_t instead.
There was also a bug in the __parse_integer helper when converting a
wide
Tested x86_64-linux. Pushed to trunk.
-- >8 --
This was recently approved for C++26, but there's no harm in
implementing it unconditionally for C++20 and C++23. As it says in the
paper, it doesn't change the meaning of any valid code. It only enables
things that were previously ill-formed for
Tested x86_64-linux. Pushed to trunk.
-- >8 --
These functions should be qualified to disable unwanted ADL.
The overload of __check_singular_aux for safe iterators was previously
being found by ADL, because it wasn't declared before __check_singular.
Add a declaration so that it can be found by
On Fri, 23 Jun 2023 at 17:44, Jan Hubicka wrote:
> > I intend to push this to trunk once testing finishes.
> >
> > I generated the diff with -b so the whitespace changes aren't shown,
> > because there was some re-indenting that makes the diff look larger than
> > it really is.
> >
> > Honza, I
I've pushed Jason's patch from https://gcc.gnu.org/PR105651#c17 to the
gcc-12 branch, because Jakub's fix on gcc-13 isn't possible to backport.
Tested x86_64-linux, pushed to gcc-12.
-- >8 --
PR tree-optimization/105651
libstdc++-v3/ChangeLog:
* include/bits/basic_string.tcc
On Tue, 20 Jun 2023 at 09:29, Jonathan Wakely wrote:
>
>
> On Tue, 20 Jun 2023 at 01:54, Patrick Palka wrote:
>
>> On Fri, 9 Jun 2023, Jonathan Wakely via Libstdc++ wrote:
>>
>> > Tested powerpc64le-linux. Pushed to trunk.
>> >
>> > This ma
I intend to push this to trunk once testing finishes.
I generated the diff with -b so the whitespace changes aren't shown,
because there was some re-indenting that makes the diff look larger than
it really is.
Honza, I don't think this is likely to make much difference for the PR
110287
On Tue, 20 Jun 2023 at 11:45, Jonathan Wakely wrote:
> On Tue, 20 Jun 2023 at 09:21, Andreas Schwab wrote:
>
>> On Jun 20 2023, Jakub Jelinek via Gcc-patches wrote:
>>
>> > Is it safe even on 64bit targets? I mean, doesn't say PowerPC already
>> allow
>&
On Tue, 20 Jun 2023 at 09:21, Andreas Schwab wrote:
> On Jun 20 2023, Jakub Jelinek via Gcc-patches wrote:
>
> > Is it safe even on 64bit targets? I mean, doesn't say PowerPC already
> allow
> > full 64-bit virtual address space? The assumption that one can't have
> > more than half of virtual
On Tue, 20 Jun 2023 at 01:54, Patrick Palka wrote:
> On Fri, 9 Jun 2023, Jonathan Wakely via Libstdc++ wrote:
>
> > Tested powerpc64le-linux. Pushed to trunk.
> >
> > This makes sense to backport after some soak time on trunk.
> >
> > -- >8 --
> >
On Mon, 19 Jun 2023 at 16:13, Jonathan Wakely wrote:
> On Mon, 19 Jun 2023 at 12:20, Jakub Jelinek wrote:
>
>> On Mon, Jun 19, 2023 at 01:05:36PM +0200, Jan Hubicka via Gcc-patches
>> wrote:
>> > - if (max_size() - size() < __n)
>> > - __throw_l
P.S. please CC libstd...@gcc.gnu.org for all libstdc++ patches.
On Mon, 19 Jun 2023 at 16:13, Jonathan Wakely wrote:
> On Mon, 19 Jun 2023 at 12:20, Jakub Jelinek wrote:
>
>> On Mon, Jun 19, 2023 at 01:05:36PM +0200, Jan Hubicka via Gcc-patches
>> wrote:
>> > - if
On Mon, 19 Jun 2023 at 12:20, Jakub Jelinek wrote:
> On Mon, Jun 19, 2023 at 01:05:36PM +0200, Jan Hubicka via Gcc-patches
> wrote:
> > - if (max_size() - size() < __n)
> > - __throw_length_error(__N(__s));
> > + const size_type __max_size = max_size();
> > + // On 64bit systems
On Sun, 18 Jun 2023 at 19:37, Jan Hubicka wrote:
> Hi,
> _M_check_len is used in vector reallocations. It computes __n + __s but
> does
> checking for case that (__n + __s) * sizeof (Tp) would overflow ptrdiff_t.
> Since we know that __s is a size of already allocated memory block if __n
> is
>
On Thu, 15 Jun 2023, 01:49 Alexandre Oliva via Libstdc++, <
libstd...@gcc.gnu.org> wrote:
>
> rtems, like vxworks, uses fast-float doubles for from_chars even for
> long double, so it loses precision, so expect the long double bits to
> fail on aarch64.
>
> Regstrapped on x86_64-linux-gnu, also
On Thu, 15 Jun 2023, 01:46 Alexandre Oliva via Libstdc++, <
libstd...@gcc.gnu.org> wrote:
>
> Contributing a patch by Joel Brobecker .
> Regstrapped on x86_64-linux-gnu just to be sure, also tested with
> aarch64-rtems6. I'm going to put this in later this week if there
> aren't any objections.
On Sat, 10 Jun 2023 at 23:04, Jonny Grant wrote:
>
> libstdc++-v3/ChangeLog:
>
> * doc/xml/manual/extensions.xml: Remove demangle exception
> description and include.
Thanks, pushed to trunk.
>
> ---
> libstdc++-v3/doc/xml/manual/extensions.xml | 6 ++
> 1 file changed, 2
On Sat, 10 Jun 2023, 06:18 Hans-Peter Nilsson via Libstdc++, <
libstd...@gcc.gnu.org> wrote:
> Thank you for your consideration. (Or is that phrase only used
> negatively?)
>
> > From: Jonathan Wakely
> > Date: Fri, 9 Jun 2023 21:40:15 +0100
>
> > test01,
On Fri, 9 Jun 2023 at 17:20, Hans-Peter Nilsson wrote:
> Hi!
>
> The test 27_io/basic_istream/ignore/wchar_t/94749.cc takes
> about 10 minutes to run for cris-elf in the "gdb simulator"
> here on my arguably way-past-retirement machine (and it
> looks like it gained a minute with LRA). I've
Tested powerpc64le-linux, sparc-solaris. Pushed to trunk.
-- >8 --
When long double uses IEEE binary128 representation we define the
_Float128 overload of std::from_chars inline in . My changes
in r14-1431-g7037e7b6e4ac41 cause it to also be defined non-inline in
the library, leading to an
801 - 900 of 9534 matches
Mail list logo
