[Bug libstdc++/101429] __replacement_assert should be marked as noexcept

2021-10-01 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101429 --- Comment #5 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:92936be47461b99d624b6a90a745f6cdc60d3e51 commit r12-4084-g92936be47461b99d624b6a90a745f6cdc60d3e51 Author: Jonathan Wakely Date:

[Bug libstdc++/101429] __replacement_assert should be marked as noexcept

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101429 Jonathan Wakely changed: What|Removed |Added Resolution|--- |FIXED Target Milestone|---

[Bug libstdc++/101429] __replacement_assert should be marked as noexcept

2021-07-15 Thread cvs-commit at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101429 --- Comment #3 from CVS Commits --- The master branch has been updated by Jonathan Wakely : https://gcc.gnu.org/g:1f7182d68c24985dace2a94422c671ff987c262c commit r12-2326-g1f7182d68c24985dace2a94422c671ff987c262c Author: Jonathan Wakely Date:

[Bug libstdc++/101429] __replacement_assert should be marked as noexcept

2021-07-12 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101429 --- Comment #2 from cqwrteur --- (In reply to cqwrteur from comment #1) > By the way, i think if _GLIBCXX_VERBOSE==0, it should be just an > __builtin_abort(). This will make optimizers much happier. The bounds > checking will be only once. > >

[Bug libstdc++/101429] __replacement_assert should be marked as noexcept

2021-07-12 Thread unlvsur at live dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101429 --- Comment #1 from cqwrteur --- By the way, i think if _GLIBCXX_VERBOSE==0, it should be just an __builtin_abort(). This will make optimizers much happier. The bounds checking will be only once. https://godbolt.org/z/7MxMoe3Yn