On Tue, 7 May 2024 at 17:39, Jonathan Wakely wrote:
>
> On Tue, 7 May 2024 at 17:33, Jeff Law wrote:
> >
> >
> >
> > On 5/7/24 9:36 AM, Andreas Schwab wrote:
> > > On Mai 07 2024, Jonathan Wakely wrote:
> > >
> > >> +#ifdef __riscv
On Tue, 7 May 2024 at 17:39, Jonathan Wakely wrote:
>
> On Tue, 7 May 2024 at 17:33, Jeff Law wrote:
> >
> >
> >
> > On 5/7/24 9:36 AM, Andreas Schwab wrote:
> > > On Mai 07 2024, Jonathan Wakely wrote:
> > >
> > >> +#ifdef __riscv
On Tue, 7 May 2024 at 17:33, Jeff Law wrote:
>
>
>
> On 5/7/24 9:36 AM, Andreas Schwab wrote:
> > On Mai 07 2024, Jonathan Wakely wrote:
> >
> >> +#ifdef __riscv
> >> +return _M_insert(__builtin_copysign((double)__f,
> >> +
On Tue, 7 May 2024 at 17:33, Jeff Law wrote:
>
>
>
> On 5/7/24 9:36 AM, Andreas Schwab wrote:
> > On Mai 07 2024, Jonathan Wakely wrote:
> >
> >> +#ifdef __riscv
> >> +return _M_insert(__builtin_copysign((double)__f,
> >> +
On Tue, 7 May 2024 at 15:06, Jonathan Wakely wrote:
>
> On Tue, 7 May 2024 at 14:57, Jeff Law wrote:
> >
> >
> >
> > On 5/7/24 7:49 AM, Jonathan Wakely wrote:
> > > Do we want this change for RISC-V, to fix PR113578?
> > >
> > > I haven't te
On Tue, 7 May 2024 at 15:06, Jonathan Wakely wrote:
>
> On Tue, 7 May 2024 at 14:57, Jeff Law wrote:
> >
> >
> >
> > On 5/7/24 7:49 AM, Jonathan Wakely wrote:
> > > Do we want this change for RISC-V, to fix PR113578?
> > >
> > > I haven't te
On Tue, 7 May 2024 at 14:57, Jeff Law wrote:
>
>
>
> On 5/7/24 7:49 AM, Jonathan Wakely wrote:
> > Do we want this change for RISC-V, to fix PR113578?
> >
> > I haven't tested it on RISC-V, only on x86_64-linux (where it doesn't do
> > anything).
> >
&
On Tue, 7 May 2024 at 14:57, Jeff Law wrote:
>
>
>
> On 5/7/24 7:49 AM, Jonathan Wakely wrote:
> > Do we want this change for RISC-V, to fix PR113578?
> >
> > I haven't tested it on RISC-V, only on x86_64-linux (where it doesn't do
> > anything).
> >
&
Tested x86_64-linux. This one is less "obviously correct", as calling
the single-character narrow(char, char) overload no longer lazily
populates individual characters in the cache (because doing that is
racy). And the single-character widen(char) no longer calls
_M_wide_init() to populate the
Tested x86_64-linux. This one is less "obviously correct", as calling
the single-character narrow(char, char) overload no longer lazily
populates individual characters in the cache (because doing that is
racy). And the single-character widen(char) no longer calls
_M_wide_init() to populate the
Tested x86_64-linux. This seems "obviously correct", and I'd like to
push it. The current code definitely has a data race, i.e. undefined
behaviour.
-- >8 --
The lazy caching in std::basic_ios::fill() updates a mutable member
without synchronization, which can cause a data race if two threads
Tested x86_64-linux. This seems "obviously correct", and I'd like to
push it. The current code definitely has a data race, i.e. undefined
behaviour.
-- >8 --
The lazy caching in std::basic_ios::fill() updates a mutable member
without synchronization, which can cause a data race if two threads
Do we want this change for RISC-V, to fix PR113578?
I haven't tested it on RISC-V, only on x86_64-linux (where it doesn't do
anything).
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/113578
* include/std/ostream (operator<<(basic_ostream&, float)):
Restore signbit after
Do we want this change for RISC-V, to fix PR113578?
I haven't tested it on RISC-V, only on x86_64-linux (where it doesn't do
anything).
-- >8 --
libstdc++-v3/ChangeLog:
PR libstdc++/113578
* include/std/ostream (operator<<(basic_ostream&, float)):
Restore signbit after
Tested x86_64-linux. Pushed to trunk. gcc-14 backport to follow.
-- >8 --
Eddie Nolan reported to me that _Unicode_view was not correctly
implementing the substitution of ill-formed subsequences with U+FFFD,
due to failing to increment the counter when the iterator reaches the
end of the
Tested x86_64-linux. Pushed to trunk. gcc-14 backport to follow.
-- >8 --
Eddie Nolan reported to me that _Unicode_view was not correctly
implementing the substitution of ill-formed subsequences with U+FFFD,
due to failing to increment the counter when the iterator reaches the
end of the
https://gcc.gnu.org/g:3f04f3939ea0ac8fdd766a60655d29de2ffb44e5
commit r15-285-g3f04f3939ea0ac8fdd766a60655d29de2ffb44e5
Author: Jonathan Wakely
Date: Wed May 1 17:09:39 2024 +0100
libstdc++: Fix handling of incomplete UTF-8 sequences in _Unicode_view
Eddie Nolan reported to me
Tested x86_64-linux. Pushed to trunk. gcc-14 backport to follow.
-- >8 --
std::shared_ptr isn't declared for freestanding, so guard uses of it
with #if _GLIBCXX_HOSTED in .
libstdc++-v3/ChangeLog:
PR libstdc++/114866
* include/bits/out_ptr.h [!_GLIBCXX_HOSTED]: Don't refer to
Tested x86_64-linux. Pushed to trunk. gcc-14 backport to follow.
-- >8 --
std::shared_ptr isn't declared for freestanding, so guard uses of it
with #if _GLIBCXX_HOSTED in .
libstdc++-v3/ChangeLog:
PR libstdc++/114866
* include/bits/out_ptr.h [!_GLIBCXX_HOSTED]: Don't refer to
https://gcc.gnu.org/g:9927059bb88e966e0a45f09e4fd1193f93df708f
commit r15-284-g9927059bb88e966e0a45f09e4fd1193f93df708f
Author: Jonathan Wakely
Date: Thu May 2 12:14:52 2024 +0100
libstdc++: Fix for -std=c++23 -ffreestanding [PR114866]
std::shared_ptr isn't declared
I don't think using a macro for these really saves us much, we can do
this to avoid duplication instead. And now it's not a big, multi-line
macro that's a pain to edit.
Any objections?
Tested x86_64-linux.
-- >8 --
libstdc++-v3/ChangeLog:
* include/std/variant
I don't think using a macro for these really saves us much, we can do
this to avoid duplication instead. And now it's not a big, multi-line
macro that's a pain to edit.
Any objections?
Tested x86_64-linux.
-- >8 --
libstdc++-v3/ChangeLog:
* include/std/variant
On Wed, 10 Apr 2024 at 09:51, Jonathan Wakely wrote:
>
> Tested x86_64-linux.
>
> This is just a minor clean-up and could wait for stage 1.
Pushed now.
>
> -- >8 --
>
> libstdc++-v3/ChangeLog:
>
> * include/std/variant (_VARIANT_RELATION_FUNCT
On Wed, 10 Apr 2024 at 09:51, Jonathan Wakely wrote:
>
> Tested x86_64-linux.
>
> This is just a minor clean-up and could wait for stage 1.
Pushed now.
>
> -- >8 --
>
> libstdc++-v3/ChangeLog:
>
> * include/std/variant (_VARIANT_RELATION_FUNCT
https://gcc.gnu.org/g:6709e35457a30b2184fa8337aa4abdd2c0edaeb3
commit r15-283-g6709e35457a30b2184fa8337aa4abdd2c0edaeb3
Author: Jonathan Wakely
Date: Thu Mar 28 14:19:45 2024 +
libstdc++: Simplify std::variant comparison operators
libstdc++-v3/ChangeLog
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Implement the changes from P2944R3 which add constraints to the
comparison operators of std::pair, std::tuple, and std::variant.
The paper also changes std::optional, but we already constrain its
comparisons using SFINAE on the return type.
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Implement the changes from P2944R3 which add constraints to the
comparison operators of std::pair, std::tuple, and std::variant.
The paper also changes std::optional, but we already constrain its
comparisons using SFINAE on the return type.
https://gcc.gnu.org/g:b72e7addf855aed66c0922f17efc85f26193f801
commit r15-279-gb72e7addf855aed66c0922f17efc85f26193f801
Author: Jonathan Wakely
Date: Wed Mar 27 15:24:05 2024 +
libstdc++: Constrain equality ops for std::pair, std::tuple, std::variant
Implement the changes
Tested x86_64-linux. Pushed to trunk.
-- >8 --
If we update the list of "active" symbols versions now, rather than when
adding a new symbol version, we will notice if new symbols get added to
the wrong version (as in PR 114692).
libstdc++-v3/ChangeLog:
*
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/backward/auto_ptr.h: Use https for URL in comment.
* include/bits/basic_ios.h: Likewise.
* include/std/iostream: Likewise.
---
libstdc++-v3/include/backward/auto_ptr.h | 2 +-
Tested x86_64-linux. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/backward/auto_ptr.h: Use https for URL in comment.
* include/bits/basic_ios.h: Likewise.
* include/std/iostream: Likewise.
---
libstdc++-v3/include/backward/auto_ptr.h | 2 +-
Tested x86_64-linux. Pushed to trunk.
-- >8 --
If we update the list of "active" symbols versions now, rather than when
adding a new symbol version, we will notice if new symbols get added to
the wrong version (as in PR 114692).
libstdc++-v3/ChangeLog:
*
https://gcc.gnu.org/g:9ebd123432873edf1551006be07381150fd617ea
commit r15-278-g9ebd123432873edf1551006be07381150fd617ea
Author: Jonathan Wakely
Date: Fri May 3 18:14:09 2024 +0100
libstdc++: Use https instead of http in some comments
libstdc++-v3/ChangeLog
https://gcc.gnu.org/g:6e25ca387fbbb412a2e498e28ea5db28e033a318
commit r15-277-g6e25ca387fbbb412a2e498e28ea5db28e033a318
Author: Jonathan Wakely
Date: Thu Apr 11 15:35:11 2024 +0100
libstdc++: Update ABI test to disallow adding to released symbol versions
If we update the list
On Thu, 2 May 2024 at 19:03, Ben Boeckel wrote:
>
> On Tue, Apr 30, 2024 at 10:24:44 +0100, Jonathan Wakely wrote:
> > On 20/11/23 11:22 -0500, Ben Boeckel wrote:
> > >---
> > > htdocs/gcc-14/changes.html | 11 +++
> > > 1 file changed, 11 insertion
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".
The branch, master has been updated
via 8ee66061ef0ec3fb5593dc42cf04aaee1c5d5e1e (commit)
from
---
commit ced576434ed310d0afee01d88d0c56f78b4d04c5
Author: Jonathan Wakely
Date: Fri May 3 16:04:49 2024 +0100
Add caveat to GCC 14 release notes about C warnings-as-errors change
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 46a0266d..82906de1 100644
--- a/htdocs/gcc-14/changes.html
+++ b/
it in the caveats
section at the top, not as the last item of the C section.
How about this? OK for wwwdocs?
-- >8 --
commit fe5fd75ea5a7a08eee0831cadbdd05689e9408db
Author: Jonathan Wakely
Date: Fri May 3 16:04:49 2024 +0100
Add caveat to GCC 14 release notes about C warnings-as-err
On Fri, 3 May 2024 at 11:51, Jonathan Wakely wrote:
>
> On Fri, 3 May 2024 at 10:30, Andreas Schwab wrote:
> >
> > * config/abi/post/powerpc-linux-gnu/baseline_symbols.txt: Update.
> > * config/abi/post/powerpc64-linux-gnu/32/baseline_symbols.txt:
> &g
On Fri, 3 May 2024 at 11:51, Jonathan Wakely wrote:
>
> On Fri, 3 May 2024 at 10:30, Andreas Schwab wrote:
> >
> > * config/abi/post/powerpc-linux-gnu/baseline_symbols.txt: Update.
> > * config/abi/post/powerpc64-linux-gnu/32/baseline_symbols.txt:
> &g
On Fri, 3 May 2024 at 10:30, Andreas Schwab wrote:
>
> * config/abi/post/powerpc-linux-gnu/baseline_symbols.txt: Update.
> * config/abi/post/powerpc64-linux-gnu/32/baseline_symbols.txt: Update.
OK thanks
> ---
> .../powerpc-linux-gnu/baseline_symbols.txt| 98
On Fri, 3 May 2024 at 10:30, Andreas Schwab wrote:
>
> * config/abi/post/powerpc-linux-gnu/baseline_symbols.txt: Update.
> * config/abi/post/powerpc64-linux-gnu/32/baseline_symbols.txt: Update.
OK thanks
> ---
> .../powerpc-linux-gnu/baseline_symbols.txt| 98
On Thu, 2 May 2024 at 18:38, Ville Voutilainen
wrote:
>
> On Thu, 2 May 2024 at 20:25, Ken Matsui wrote:
> > > There was some discussion of how to name the built-ins back in
> > > https://gcc.gnu.org/pipermail/gcc-patches/2007-March/thread.html#212171
> > > but __builtin wasn't discussed.
> > >
On Thu, 2 May 2024 at 18:38, Ville Voutilainen
wrote:
>
> On Thu, 2 May 2024 at 20:25, Ken Matsui wrote:
> > > There was some discussion of how to name the built-ins back in
> > > https://gcc.gnu.org/pipermail/gcc-patches/2007-March/thread.html#212171
> > > but __builtin wasn't discussed.
> > >
https://gcc.gnu.org/g:fcf60d0baafa1245f768ac375dc60a07e92e9673
commit r13-8675-gfcf60d0baafa1245f768ac375dc60a07e92e9673
Author: Jonathan Wakely
Date: Thu Apr 4 10:33:33 2024 +0100
libstdc++: Fix infinite loop in std::istream::ignore(n, delim) [PR93672]
A negative delim value
https://gcc.gnu.org/g:3d16f8f2aec9583422d00c531732ca9d33e6ef26
commit r13-8674-g3d16f8f2aec9583422d00c531732ca9d33e6ef26
Author: Jonathan Wakely
Date: Wed Mar 27 21:51:13 2024 +
libstdc++: Reverse arguments in constraint for std::optional's <=>
[PR
Tested x86_64-linux.
It would also be possible to fix this with:
#if ! _GLIBCXX_HOSTED
template inline constexpr __is_shared_ptr = false;
#endif
But we would still need to guard the partial specializations that use
shared_ptr and __shared_ptr. It seemed cleaner to just guard all uses of
Tested x86_64-linux.
It would also be possible to fix this with:
#if ! _GLIBCXX_HOSTED
template inline constexpr __is_shared_ptr = false;
#endif
But we would still need to guard the partial specializations that use
shared_ptr and __shared_ptr. It seemed cleaner to just guard all uses of
On Thu, 2 May 2024 at 12:24, Jonathan Wakely wrote:
>
> I found some issues in the std::chrono::tzdb parser by testing the
> tzdata "vanguard" format, which uses new features that aren't enabled in
> the "main" and "rearguard" data formats.
>
> Sinc
On Thu, 2 May 2024 at 12:24, Jonathan Wakely wrote:
>
> I found some issues in the std::chrono::tzdb parser by testing the
> tzdata "vanguard" format, which uses new features that aren't enabled in
> the "main" and "rearguard" data formats.
>
> Sinc
I found some issues in the std::chrono::tzdb parser by testing the
tzdata "vanguard" format, which uses new features that aren't enabled in
the "main" and "rearguard" data formats.
Since 2024a the keyword "minimum" is no longer valid for the FROM and TO
fields in a Rule line, which means that "m"
I found some issues in the std::chrono::tzdb parser by testing the
tzdata "vanguard" format, which uses new features that aren't enabled in
the "main" and "rearguard" data formats.
Since 2024a the keyword "minimum" is no longer valid for the FROM and TO
fields in a Rule line, which means that "m"
https://gcc.gnu.org/g:0ecb0967b4f7e68027492ac03e5dc03b5bcfdcf7
commit r11-11411-g0ecb0967b4f7e68027492ac03e5dc03b5bcfdcf7
Author: Jonathan Wakely
Date: Fri Mar 1 11:16:58 2024 +
libstdc++: Add missing std::tuple constructor [PR114147]
I caused a regression with commit r10-908
Tested x86_64-linux.
I'm considering making the increment of __to_incr conditional:
if constexpr (!random_access_iterator<_Iter>)
++__to_incr;
and then when we call _M_update using _M_curr() - __g._M_orig for the
number of characters consumed. I should benchmark that to see if it
Tested x86_64-linux.
I'm considering making the increment of __to_incr conditional:
if constexpr (!random_access_iterator<_Iter>)
++__to_incr;
and then when we call _M_update using _M_curr() - __g._M_orig for the
number of characters consumed. I should benchmark that to see if it
On Wed, 1 May 2024 at 20:19, Jeff Law via Gcc wrote:
>
>
>
> On 4/22/24 9:24 PM, Tom Tromey wrote:
> > Jason> Someone mentioned earlier that gerrit was previously tried
> > Jason> unsuccessfully.
> >
> > We tried it and gdb and then abandoned it. We tried to integrate it
> > into the traditional
Tested x86_64-linux. Pushed to trunk.
I'll backport this to gcc-14 as well, but it can wait until after the
14.1 release.
-- >8 --
This type trait isn't supported by Clang 18. It's only used in static
assertions, so they can just be omitted if the trait isn't available.
libstdc++-v3/ChangeLog:
Tested x86_64-linux. Pushed to trunk.
I'll backport this to gcc-14 as well, but it can wait until after the
14.1 release.
-- >8 --
This type trait isn't supported by Clang 18. It's only used in static
assertions, so they can just be omitted if the trait isn't available.
libstdc++-v3/ChangeLog:
https://gcc.gnu.org/g:1fbe1a50d86df11f434351cf62461a32747f9710
commit r15-92-g1fbe1a50d86df11f434351cf62461a32747f9710
Author: Jonathan Wakely
Date: Tue Apr 30 09:48:00 2024 +0100
libstdc++: Guard uses of is_pointer_interconvertible_v [PR114891]
This type trait isn't supported
On Mon, 22 Apr 2024 at 12:35, Georg-Johann Lay wrote:
>
> Am 22.04.24 um 12:04 schrieb Jonathan Wakely:
> > OK for wwwdocs?
>
> For me it's ok (I am not a native speaker though,
> which is the reason the typos are there to begin with).
I've pushed this now.
>
> J
---
commit 8e626db7182e01ad09bdab91f6a83ecb2dbde4e3
Author: Jonathan Wakely
Date: Mon Apr 22 11:03:07 2024 +0100
Improve grammar for AVR changes in GCC 14
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 4a9670fd..8dfbf7dc 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/ch
https://gcc.gnu.org/g:61c38a231d2df60cb6e914b3ecc73a0229c17ff6
commit r13-8665-g61c38a231d2df60cb6e914b3ecc73a0229c17ff6
Author: Jonathan Wakely
Date: Fri Apr 26 11:42:26 2024 +0100
libstdc++: Do not apply localized formatting to NaN and inf [PR114863]
We don't want to add
On 20/11/23 11:22 -0500, Ben Boeckel wrote:
---
htdocs/gcc-14/changes.html | 11 +++
1 file changed, 11 insertions(+)
diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 7278f753..b506eeb1 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@
https://gcc.gnu.org/g:7a00c459cbb913ac165a39d344a48fc27800bb0a
commit r14-10154-g7a00c459cbb913ac165a39d344a48fc27800bb0a
Author: Jonathan Wakely
Date: Fri Apr 26 11:42:26 2024 +0100
libstdc++: Do not apply localized formatting to NaN and inf [PR114863]
We don't want to add
On Mon, 22 Apr 2024 at 22:43, Patrick Palka wrote:
>
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk? More tests
> are needed but I figured I'd submit this now for possible consideration into
> GCC 14 since we're getting close to release.. All changes are confined to
> C++26.
OK
On Mon, 22 Apr 2024 at 22:43, Patrick Palka wrote:
>
> Tested on x86_64-pc-linux-gnu, does this look OK for trunk? More tests
> are needed but I figured I'd submit this now for possible consideration into
> GCC 14 since we're getting close to release.. All changes are confined to
> C++26.
OK
On Sun, 28 Apr 2024, 11:24 Gerald Pfeifer, wrote:
> Hi Jonathan,
>
> On Fri, 26 Apr 2024, Jonathan Wakely wrote:
> > How are you testing on FreeBSD?
> >
> > When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++
> > testsuite it fails due to lot
Tested x86_64-linux. Pushed to trunk.
I'm going to push this to gcc-13 and gcc-14 too (approved by Jakub on
IRC).
-- >8 --
We don't want to add grouping to strings like "-inf", and there is no
radix character to replace either.
libstdc++-v3/ChangeLog:
PR libstdc++/114863
*
Tested x86_64-linux. Pushed to trunk.
I'm going to push this to gcc-13 and gcc-14 too (approved by Jakub on
IRC).
-- >8 --
We don't want to add grouping to strings like "-inf", and there is no
radix character to replace either.
libstdc++-v3/ChangeLog:
PR libstdc++/114863
*
https://gcc.gnu.org/g:a0bc71e480132a528a4869c1cd7863f709768c53
commit r15-5-ga0bc71e480132a528a4869c1cd7863f709768c53
Author: Jonathan Wakely
Date: Fri Apr 26 11:42:26 2024 +0100
libstdc++: Do not apply localized formatting to NaN and inf [PR114863]
We don't want to add grouping
You can view, comment on, or merge this pull request online at:
https://github.com/rpm-software-management/rpm/pull/3064
-- Commit Summary --
* Fix spelling and grammar in conditionalbuilds.md
-- File Changes --
M docs/manual/conditionalbuilds.md (4)
-- Patch Links --
Hi Gerald, Andreas,
How are you testing on FreeBSD?
When I build GCC trunk on FreeBSD 14.0 and try to run the libstdc++
testsuite it fails due to lots of these errors:
Excess errors:
/usr/local/bin/ld: /tmp//ccev946q.o: relocation R_X86_64_32 against
symbol
Pushed to gcc-14.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/html/manual/status.html: Regenerate.
* doc/xml/manual/status_cxx1998.xml: Replace references to
mainline GCC.
* doc/xml/manual/status_cxx2011.xml: Likewise.
* doc/xml/manual/status_cxx2014.xml:
Pushed to gcc-14.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/html/manual/status.html: Regenerate.
* doc/xml/manual/status_cxx1998.xml: Replace references to
mainline GCC.
* doc/xml/manual/status_cxx2011.xml: Likewise.
* doc/xml/manual/status_cxx2014.xml:
https://gcc.gnu.org/g:5e5f33a067d03d11f67eba719d3ef9f37b23886d
commit r14-10139-g5e5f33a067d03d11f67eba719d3ef9f37b23886d
Author: Jonathan Wakely
Date: Fri Apr 26 11:46:01 2024 +0100
libstdc++: Update status tables to refer to GCC 14 not mainline
libstdc++-v3/ChangeLog
Pushed to gcc-13.
-- >8 --
This should have been done before the 13.1.0 release.
libstdc++-v3/ChangeLog:
* doc/html/manual/status.html: Regenerate.
* doc/xml/manual/status_cxx1998.xml: Replace references to
mainline GCC.
* doc/xml/manual/status_cxx2011.xml:
Pushed to gcc-13.
-- >8 --
This should have been done before the 13.1.0 release.
libstdc++-v3/ChangeLog:
* doc/html/manual/status.html: Regenerate.
* doc/xml/manual/status_cxx1998.xml: Replace references to
mainline GCC.
* doc/xml/manual/status_cxx2011.xml:
Pushed to trunk. I'll also be following this with the non-whitespace
equivalents for the gcc-14 and gcc-13 branches.
-- >8 --
This simplifies the changes needed after branching for a new release, so
that new line breaks don't need to be introduced every time we branch.
libstdc++-v3/ChangeLog:
https://gcc.gnu.org/g:56f28dd436c75b5cfbd6af7a02bff968894eafa6
commit r13-8653-g56f28dd436c75b5cfbd6af7a02bff968894eafa6
Author: Jonathan Wakely
Date: Fri Apr 26 11:46:01 2024 +0100
libstdc++: Update status tables to refer to GCC 13 not mainline
This should have been done before
Pushed to trunk. I'll also be following this with the non-whitespace
equivalents for the gcc-14 and gcc-13 branches.
-- >8 --
This simplifies the changes needed after branching for a new release, so
that new line breaks don't need to be introduced every time we branch.
libstdc++-v3/ChangeLog:
https://gcc.gnu.org/g:772250a36c53a7b29a53e090d911b502afdfd1fe
commit r15-3-g772250a36c53a7b29a53e090d911b502afdfd1fe
Author: Jonathan Wakely
Date: Fri Apr 26 11:48:48 2024 +0100
libstdc++: Adjust whitespace in status tables in manual
This simplifies the changes needed after
On Thu, 25 Apr 2024 at 20:29, Aleksey Cheusov via cfarm-users
wrote:
>
> Can any one please fix broken clang++ on cfarm103?
>
> 0 ~>cat ~/tmp/2.cc
> #include
>
> int main(int argc, char **argv)
> {
> std::cout << "Hello";
> return 0;
> }
>
> 0 ~>clang++ -o ~/tmp/2 ~/tmp/2.cc
>
On Thu, 18 Apr 2024 at 21:34, Jonathan Wakely wrote:
>
> On Thu, 18 Apr 2024 at 20:51, Jonathan Wakely wrote:
> >
> > This completes the fixes to put all experimental symbols into
> > libstdc++exp.a.
> >
> > On trunk the libstdc++_libbacktrace.a was removed
On Thu, 18 Apr 2024 at 21:34, Jonathan Wakely wrote:
>
> On Thu, 18 Apr 2024 at 20:51, Jonathan Wakely wrote:
> >
> > This completes the fixes to put all experimental symbols into
> > libstdc++exp.a.
> >
> > On trunk the libstdc++_libbacktrace.a was removed
https://gcc.gnu.org/g:f3cff718df0cf7590ccf9bc1d8cd17e4e08f1e6d
commit r13-8649-gf3cff718df0cf7590ccf9bc1d8cd17e4e08f1e6d
Author: Jonathan Wakely
Date: Thu Apr 18 17:26:55 2024 +0100
libstdc++: Add libstdc++_libbacktrace.a to libstdc++exp
This completes the fixes to put all
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
The Doxygen-generated man pages for some new types need to be renamed to
use '::' instead of '_' in the filenames.
libstdc++-v3/ChangeLog:
* scripts/run_doxygen: Rename man pages for nested types.
---
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/std/chrono (tzdb_list): Fix typo in Doxygen comment.
---
libstdc++-v3/include/std/chrono | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
Doxygen switched from \fC to \fR in its man page output:
https://github.com/doxygen/doxygen/pull/10497
This breaks our script that expects \fC so change the regaulr expression
to work with either style.
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
The Doxygen-generated man pages for some new types need to be renamed to
use '::' instead of '_' in the filenames.
libstdc++-v3/ChangeLog:
* scripts/run_doxygen: Rename man pages for nested types.
---
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/doxygen/stdheader.cc (init_map): Add missing headers.
* doc/doxygen/user.cfg.in (EXCLUDE): Exclude generated files for
std::format and std::text_encoding.
---
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* include/std/chrono (tzdb_list): Fix typo in Doxygen comment.
---
libstdc++-v3/include/std/chrono | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
Doxygen switched from \fC to \fR in its man page output:
https://github.com/doxygen/doxygen/pull/10497
This breaks our script that expects \fC so change the regaulr expression
to work with either style.
Tested x86_64-linux, and docs regenerated. Pushed to trunk.
-- >8 --
libstdc++-v3/ChangeLog:
* doc/doxygen/stdheader.cc (init_map): Add missing headers.
* doc/doxygen/user.cfg.in (EXCLUDE): Exclude generated files for
std::format and std::text_encoding.
---
Tested x86_64-linux. Pushed to trunk.
-- >8 --
It's not obvious why needs so add a
comment to it.
libstdc++-v3/ChangeLog:
* include/std/variant: Add comment to #include.
---
libstdc++-v3/include/std/variant | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
https://gcc.gnu.org/g:8d80e3c5a641556e32fdf3637f08a0648f5aaab3
commit r14-10129-g8d80e3c5a641556e32fdf3637f08a0648f5aaab3
Author: Jonathan Wakely
Date: Thu Apr 25 14:02:36 2024 +0100
libstdc++: Rename man pages to use '::' instead of '_'
The Doxygen-generated man pages for some
https://gcc.gnu.org/g:6391cf8bd9c1d71805d9aba00b25fdaa550f39c8
commit r14-10128-g6391cf8bd9c1d71805d9aba00b25fdaa550f39c8
Author: Jonathan Wakely
Date: Thu Apr 25 13:52:00 2024 +0100
libstdc++: Fix typo in Doxygen comment
libstdc++-v3/ChangeLog:
* include/std
Tested x86_64-linux. Pushed to trunk.
-- >8 --
It's not obvious why needs so add a
comment to it.
libstdc++-v3/ChangeLog:
* include/std/variant: Add comment to #include.
---
libstdc++-v3/include/std/variant | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
https://gcc.gnu.org/g:c9cc1c850c6d084752207b6cf247a0a48bae0d52
commit r14-10127-gc9cc1c850c6d084752207b6cf247a0a48bae0d52
Author: Jonathan Wakely
Date: Thu Apr 25 13:24:56 2024 +0100
libstdc++: Fix run_doxygen for Doxygen 1.10 man page format
Doxygen switched from \fC to \fR
https://gcc.gnu.org/g:d5b2c6b32c97e1fd03214771d35f8d67b0d72940
commit r14-10126-gd5b2c6b32c97e1fd03214771d35f8d67b0d72940
Author: Jonathan Wakely
Date: Thu Apr 25 13:09:27 2024 +0100
libstdc++: Update Doxygen config for new headers
libstdc++-v3/ChangeLog:
* doc
https://gcc.gnu.org/g:f3021e6e0600bedd69567b21d2a06b0b9854c533
commit r14-10125-gf3021e6e0600bedd69567b21d2a06b0b9854c533
Author: Jonathan Wakely
Date: Thu Apr 25 13:04:43 2024 +0100
libstdc++: Add comment to #include in
It's not obvious why needs so add a
comment
1 - 100 of 14754 matches
Mail list logo
