[Bug c++/66763] [6 Regression] 25_algorithms/remove/requirements/explicit_instantiation/2.cc fails on AIX

2021-07-24 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66763 --- Comment #13 from Jonathan Wakely --- Ha! Oops

[Bug libstdc++/101587] ranges::uninitialized_copy/move incorrectly uses std::min

2021-07-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101587 --- Comment #5 from Jonathan Wakely --- Yes, much simpler than that! :-) There are lots of uses of std::min and std::max with explicit template argument lists in the Parallel Mode headers, but I have no intention of touching them, and they

[Bug libstdc++/101587] ranges::uninitialized_copy/move incorrectly uses std::min

2021-07-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101587 --- Comment #3 from Jonathan Wakely --- In theory yes, but it's unlikely to be a problem in practice because the library doesn't need to compare unsigned types with negative values. If it does need to do that, it is either already doing so

[Bug libstdc++/101587] ranges::uninitialized_copy/move incorrectly uses std::min

2021-07-23 Thread redi at gcc dot gnu.org via Gcc-bugs
|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org

[Bug target/95286] -march=native causes mt19937_64 + uniform_real_distribution generating wrong result.

2021-07-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95286 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug libstdc++/101587] ranges::uninitialized_copy/move incorrectly uses std::min

2021-07-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101587 --- Comment #1 from Jonathan Wakely --- Maybe we should add this somewhere and just stop using std::min for integers: struct __min_fn { template typename common_type<_Tp, _Up>::type operator()(_Tp __t, _Up __u) const

[Bug libstdc++/101587] ranges::uninitialized_copy/move incorrectly uses std::min

2021-07-23 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101587 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug analyzer/94355] support for C++ new expression

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94355 --- Comment #9 from Jonathan Wakely --- (In reply to William Navarre from comment #8) > It seems that `operator new` is generally not supposed to return NULL -- > std::bad_alloc() is supposed to be thrown instead. If an operator new overload

[Bug libstdc++/101034] wrong constraint in std::any's constructor

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

[Bug libstdc++/90415] [9 Regression] std::is_copy_constructible> is incomplete

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

[Bug libstdc++/92156] Cannot in-place construct std::any with std::any

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92156 --- Comment #7 from Jonathan Wakely --- Fixed for 9.5 too.

[Bug libstdc++/100982] wrong constraint in std::optional::operator=

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

[Bug libstdc++/89322] Use of new and -lsupc++ requires -lstdc++ on architectures without atomics

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89322 Bug 89322 depends on bug 96657, which changed state. Bug 96657 Summary: [9 Regression] libsupc++.a missing required functions from src/c++98/atomicity.cc when atomic builtins are not supported https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96657

[Bug libstdc++/96657] [9 Regression] libsupc++.a missing required functions from src/c++98/atomicity.cc when atomic builtins are not supported

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96657 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|---

[Bug libstdc++/101583] [12 Regression] error: use of deleted function when building gold

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

[Bug libstdc++/101583] [12 Regression] error: use of deleted function when building gold

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
|--- |12.0 Last reconfirmed||2021-07-22 Status|UNCONFIRMED |ASSIGNED Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org --- Comment #3 from Jonathan Wakely --- Oops, I need to call the non-default

[Bug libstdc++/96657] [9 Regression] libsupc++.a missing required functions from src/c++98/atomicity.cc when atomic builtins are not supported

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Summary|[9/10 Regression] |[9 Regression] libsupc++.a |libsupc++.a missing |missing required functions |required functions from |from src/c++98/atomicity.cc

[Bug libstdc++/98842] optional's spaceship operations generates wrong code when operator== is not present

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98842 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/99625] GCC does not detect narrowing in aggregate initialization

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99625 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-22

[Bug libstdc++/97570] avr-gcc: error: 'void* memalign' redeclared as different kind of entity

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97570 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Target Milestone|---

[Bug c++/98486] Variable template specialization doesn't account for primary's constraints

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98486 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-22 Ever confirmed|0

[Bug c++/96183] GCC accepts "convert '' from 'void' to 'int'" at compile time

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96183 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-22

[Bug libstdc++/95702] ranges::transform missing vectorization opportunity

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95702 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug libstdc++/94345] std::chrono overflows due to c++14 non-compliance

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

[Bug libstdc++/94295] use __builtin_operator_new and __builtin_operator_delete when available

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94295 Jonathan Wakely changed: What|Removed |Added Target Milestone|--- |12.0 Status|ASSIGNED

[Bug libstdc++/98518] std::array not bound checked with _GLIBCXX_ASSERTIONS

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

[Bug libstdc++/101571] DestroyGuard used by the ranges::uninitialized family should use addressof()

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101571 Jonathan Wakely changed: What|Removed |Added Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org

[Bug libstdc++/100682] Outdated manual about the debug mode using

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org --- Comment #3 from Jonathan Wakely --- Fixed on trunk for now.

[Bug c++/101015] Poor diagnostic for deprecated alias-declaration

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101015 Jonathan Wakely changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c++/84360] unnecessary aka in error message

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

[Bug c++/101572] Temporary object lifetime is not prolonged as required by the standard

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101572 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-22 Ever confirmed|0

[Bug libstdc++/101571] DestroyGuard used by the ranges::uninitialized family should use addressof()

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101571 --- Comment #2 from Jonathan Wakely --- We should also do this: --- a/libstdc++-v3/testsuite/util/testsuite_iterators.h +++ b/libstdc++-v3/testsuite/util/testsuite_iterators.h @@ -175,10 +175,14 @@ namespace __gnu_test #if __cplusplus >=

[Bug libstdc++/101571] DestroyGuard used by the ranges::uninitialized family should use addressof()

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101571 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug libstdc++/58909] C++11's condition variables fail with static linking

2021-07-22 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58909 --- Comment #26 from Jonathan Wakely --- If you create a new thread of execution then you'll get a non-weak reference to pthread_create, which should cause libpthread.so to be linked even with -Wl,--as-needed (and for static linking it will work

[Bug libstdc++/100682] Outdated manual about the debug mode using

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

[Bug c++/101566] gcc miscompiles lambda used as tuple-like object applied to function for call

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101566 --- Comment #8 from Jonathan Wakely --- (In reply to Dale Weiler from comment #5) > This is curious, omitting `decltype(auto)` for get, as in just `auto` seems > to work around the issue as well. > > template > constexpr auto get(T tuple) {

[Bug libstdc++/40380] class documentation should mention include file to use

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40380 --- Comment #6 from Jonathan Wakely --- My doxygen patch was merged, so we can start to use SHOW_HEADERFILE and @headerfile to do this.

[Bug libstdc++/101542] __gnu_cxx::sequence_buffer const copy constructor is badly broken

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101542 Jonathan Wakely changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug c++/100493] Lambda default copy capture that captures "this" cannot be used in both C++17 and C++20 modes

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100493 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-21

[Bug libstdc++/101542] __gnu_cxx::sequence_buffer const copy constructor is badly broken

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101542 --- Comment #3 from Jonathan Wakely --- (In reply to Brooks Moses from comment #0) > This started failing with a recent Clang change > (https://github.com/llvm/llvm-project/commit/ > 7d2d5a3a6d7aaa40468c30250bf6b0938ef02c08), described as

[Bug target/101544] [OpenMP][AMDGCN][nvptx] C++ offloading: unresolved _Znwm = "operator new(unsigned long)"

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101544 --- Comment #7 from Jonathan Wakely --- Yes, --disable-libstdcxx-hosted will build the freestanding version of libstdc++

[Bug libstdc++/101542] __gnu_cxx::sequence_buffer const copy constructor is badly broken

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101542 --- Comment #2 from Jonathan Wakely --- This should work: --- a/libstdc++-v3/include/ext/rope +++ b/libstdc++-v3/include/ext/rope @@ -203,6 +203,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION std::copy(__x._M_buffer, __x._M_buffer +

[Bug libstdc++/101542] __gnu_cxx::sequence_buffer const copy constructor is badly broken

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101542 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libstdc++/101527] The implementation of std::common_iterator::operator== seems to be wrong

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101527 --- Comment #2 from Jonathan Wakely --- I find it surprising, but the CWG consensus seems to be that a friend defined inline in the class body is "a member declaration of the befriended class".

[Bug target/101544] [OpenMP][AMDGCN][nvptx] C++ offloading: unresolved _Znwm = "operator new(unsigned long)"

2021-07-21 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101544 --- Comment #4 from Jonathan Wakely --- (In reply to Andrew Stubbs from comment #3) > C++ offloading works fine provided that there are no library calls or > exceptions. There's no reason std::pair, std::tuple, std::optional and types like

[Bug libstdc++/94295] use __builtin_operator_new and __builtin_operator_delete when available

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
|ASSIGNED Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org --- Comment #11 from Jonathan Wakely --- Patches posted: https://gcc.gnu.org/pipermail/gcc-patches/2021-July/575675.html

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 --- Comment #16 from Jonathan Wakely --- Fixed on trunk now, I'll backport it too, but not in time for 11.2

[Bug libstdc++/94295] use __builtin_operator_new and __builtin_operator_delete when available

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94295 --- Comment #9 from Jonathan Wakely --- Thanks

[Bug c++/93652] -Wconversion gives false warning with bitwise operations on reference types returned from function

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93652 --- Comment #3 from Jonathan Wakely --- Fixed by r10-7344: c++: Handle COMPOUND_EXPRs in get_narrower and warnings_for_convert_and_check [PR91993]

[Bug c++/38522] -Wconversion does not handle complex bitwise expressions

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

[Bug c/53277] -Wconversion cannot handle compound expressions

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53277 --- Comment #19 from Jonathan Wakely --- For C++ the comment 15 case seems to have been fixed by r10-6527: c++: Use constexpr to avoid wrong -Wsign-compare (PR90691). We would like to do constexpr evaluation to avoid false positives on

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 --- Comment #13 from Jonathan Wakely --- (In reply to Madhu from comment #11) > I think my initial problem remains Well your "initial problem" was talking exclusively about create_directory, which works perfectly. There is a problem is a

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 Jonathan Wakely changed: What|Removed |Added Status|WAITING |ASSIGNED --- Comment #12 from

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 Jonathan Wakely changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 --- Comment #8 from Jonathan Wakely --- I think you are still confused between the bool that crate_directory returns, and the bool that you get from !ec The bool that is returned tells you if a new directory was created. The bool you get from

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 Jonathan Wakely changed: What|Removed |Added Resolution|--- |INVALID Status|WAITING

[Bug libstdc++/100863] 23_containers/unordered_{map,set}/allocator/default_init.cc still fail at runtime even after r12-1153

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100863 Jonathan Wakely changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|---

[Bug c++/101519] Improve diagnostic for template name used as base class

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101519 --- Comment #2 from Jonathan Wakely --- See also PR 101526 which requests another improvement to the same diagnostic, but with a different cause.

[Bug c++/101526] New: Improve diagnostic for trailing comma in base-clause in class-head

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
Severity: enhancement Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- struct A { }; struct B : A, { }; GCC correctly says: base.C:2:15: error: expected class-name

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 --- Comment #4 from Jonathan Wakely --- I've added tests to verify that the behaviour is correct, and those tests pass with all versions of GCC.

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 --- Comment #2 from Jonathan Wakely --- (In reply to Madhu from comment #0) > cppreference.com states > > ``` > bool create_directory( const std::filesystem::path& p ); > > Creates the directory p as if by POSIX mkdir() with a second

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101510 Jonathan Wakely changed: What|Removed |Added Status|ASSIGNED|WAITING --- Comment #1 from Jonathan

[Bug c++/101524] New: Improve diagnostic for incorrect definition of namespace alias

2021-07-20 Thread redi at gcc dot gnu.org via Gcc-bugs
Severity: enhancement Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- This is an incorrect attempt to define a namespace alias: namespace x { namespace y { } } using z = x::y

[Bug libstdc++/101510] std::filesystem::create_directory on an existing symlink to a directory

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org Last reconfirmed||2021-07-19 Ever confirmed|0 |1

[Bug c++/101519] New: Improve diagnostic for template name used as base class

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
Severity: enhancement Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- template struct A { }; template struct B : A { }; a.C:2:35: error: expected class-name before ‘{’ token 2

[Bug libstdc++/94295] use __builtin_operator_new and __builtin_operator_delete when available

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94295 --- Comment #7 from Jonathan Wakely --- Richard S., is there any reason to use the built-ins for the constant evaluation case? I assume not. Currently std::allocator does: [[nodiscard,__gnu__::__always_inline__]] constexpr _Tp*

[Bug libstdc++/101055] [11/12 Regression] should use __has_cpp_attribute() with __ prefixed/suffixed names

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101055 --- Comment #7 from Jonathan Wakely --- I think this also affects the Intel compiler, as the latest release doesn't handle [[__no_unique_address__]].

[Bug libstdc++/101427] [11 Regression] std::get should refuse to compile if type is provided and it is duplicated in std::tuple

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

[Bug c++/101480] [11/12 Regression] Miscompiled code involving operator new

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101480 Jonathan Wakely changed: What|Removed |Added See Also||https://gcc.gnu.org/bugzill

[Bug c++/101480] [11/12 Regression] Miscompiled code involving operator new

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101480 --- Comment #8 from Jonathan Wakely --- But operator new is not defined in the runtime here, it's a replaceable global allocation function. The assumption seems unsafe for replaceable functions that users can define in their own code.

[Bug libstdc++/100863] 23_containers/unordered_{map,set}/allocator/default_init.cc still fail at runtime even after r12-1153

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
at gcc dot gnu.org |redi at gcc dot gnu.org Status|RESOLVED|REOPENED --- Comment #6 from Jonathan Wakely --- My fix causes a regression: #include template struct Allocator { using value_type = Tp; Allocator(int) noexcept { } template

[Bug c++/101500] [9/10/11/12 Regression] gcc accepts the code with extra curly braces

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101500 Jonathan Wakely changed: What|Removed |Added Known to fail||10.3.0, 11.1.0, 12.0,

[Bug c++/90033] [concepts] ICE segfault evaluating a requires clause that transitively depends on itself

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90033 --- Comment #3 from Jonathan Wakely --- It was fixed by the r10-3735 rewrite "Update the concepts implementation to conform to C++20." That definitely isn't going to be backported.

[Bug c++/82833] [concepts] Out-of-line definition of nested class template errors with constraint (ICE)

2021-07-19 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82833 --- Comment #2 from Jonathan Wakely --- Looks like the ICE was fixed by the concepts rewrite in r10-3735 "Update the concepts implementation to conform to C++20." Valid C++20 testcase: #include #include template concept CallYieldsType =

[Bug libstdc++/101485] Calling std::equal with std::byte* does not use memcmp

2021-07-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101485 Jonathan Wakely changed: What|Removed |Added Keywords||missed-optimization See

[Bug c++/101480] [11/12 Regression] Miscompiled code involving operator new

2021-07-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101480 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug c++/101480] [11/12 Regression] Miscompiled code involving operator new

2021-07-18 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101480 Jonathan Wakely changed: What|Removed |Added Known to work||10.3.0 Keywords|

[Bug c++/66968] Incorrect template argument shown in diagnostic

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66968 --- Comment #7 from Jonathan Wakely --- To reproduce the std::tuple error above, use this code at r12-2379 #include std::tuple t; auto a = std::get<1>(t);

[Bug c++/101477] Wrong location for unexpanded parameter pack in function template

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101477 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-16 See Also|

[Bug c++/101477] New: Wrong location for unexpanded parameter pack in function template

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org Target Milestone: --- template class tuple { }; template tuple get(const tuple& t) { return t; } The error shows the w

[Bug c++/66968] Incorrect template argument shown in diagnostic

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66968 Jonathan Wakely changed: What|Removed |Added Last reconfirmed|2017-08-21 00:00:00 |2021-7-16 --- Comment #5 from

[Bug c++/55664] Missing diagnostic "dependent using declaration resolved to type without 'typename'"

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55664 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-16 Ever confirmed|0

[Bug c++/53863] misleading error message for redefinitions

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53863 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED

[Bug c++/84895] Smarter suggestions for "private" accessor hints

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

[Bug c++/43253] improve diagnostics for invalid pseudo destructor call

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43253 Jonathan Wakely changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0

[Bug c++/15684] Pointer to member function called on incomplete type should diag

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15684 Jonathan Wakely changed: What|Removed |Added Resolution|--- |INVALID Status|NEW

[Bug libstdc++/101307] Variable templates for type traits—corrections

2021-07-16 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101307 Jonathan Wakely changed: What|Removed |Added Target Milestone|--- |12.0 Status|NEW

[Bug c++/50462] poor diagnostics for missing parenthesis in call to method

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50462 --- Comment #7 from Jonathan Wakely --- Oh, it's the overloaded function thjat makes the difference between saying "invalid use of non-static member function" and trying to do overload resolution with an . Reduced example that actually

[Bug c++/101465] Poorly worded error from a call to a pointer-to-member function not wrapped in parentheses

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101465 Jonathan Wakely changed: What|Removed |Added Ever confirmed|0 |1 Last reconfirmed|

[Bug c++/50462] poor diagnostics for missing parenthesis in call to method

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50462 --- Comment #6 from Jonathan Wakely --- (In reply to Jonathan Wakely from comment #5) > Since GCC 4.9 we don't perform overload resolution, so I think this is fixed: Huh, that's true for the reduced example in comment 4, but the original one

[Bug c++/50462] poor diagnostics for missing parenthesis in call to method

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50462 --- Comment #5 from Jonathan Wakely --- Since GCC 4.9 we don't perform overload resolution, so I think this is fixed: 50462.C: In function 'void print(V)': 50462.C:13:13: error: invalid use of non-static member function 'int V::size()' 13 |

[Bug c++/17459] Spurious message when forgetting parentheses on call of member

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=17459 Jonathan Wakely changed: What|Removed |Added Last reconfirmed|2005-06-13 00:43:47 |2021-7-15 --- Comment #6 from

[Bug c++/83596] ['17] can't use member pointer result of a constexpr function as template argument

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

[Bug c++/101233] ICE when using ::ranges::v3::to

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101233 --- Comment #6 from Jonathan Wakely --- (In reply to Patrick Palka from comment #5) > but one needs to include > as well (for pmr::polymorphic_allocator). For libstdc++ the header only declares the pmr::vector alias, without defining

[Bug libstdc++/101307] Variable templates for type traits—corrections

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101307 Jonathan Wakely changed: What|Removed |Added Last reconfirmed||2021-07-15 Ever confirmed|0

[Bug libstdc++/101427] [11 Regression] std::get should refuse to compile if type is provided and it is duplicated in std::tuple

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101427 Jonathan Wakely changed: What|Removed |Added Summary|[11/12 Regression] std::get |[11 Regression] std::get

[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++/101427] [11/12 Regression] std::get should refuse to compile if type is provided and it is duplicated in std::tuple

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101427 --- Comment #1 from Jonathan Wakely --- The std::get code stopped working as a result of r11-4693 which implemented a core language change: c++: DR2303, ambiguous base deduction [PR97453] When there are two possible matches and one is

[Bug c++/99664] Overriding virtual function with different return type (and not covariant) is allowed to compile, when it shouldn’t be

2021-07-15 Thread redi at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99664 Jonathan Wakely changed: What|Removed |Added CC||xmh970252187 at gmail dot com ---

[Bug c++/101458] An invalid covaraint return type is accepted

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

  1   2   3   4   5   6   7   8   9   10   >