[Bug tree-optimization/120945] New: Missed optimization opportunity with std::bind_front

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120945 Bug ID: 120945 Summary: Missed optimization opportunity with std::bind_front Product: gcc Version: 15.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Comp

[Bug tree-optimization/119480] Wrong code generated in simple program that uses LLVM::map_to_vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119480 --- Comment #4 from Mark Bourgeault --- Yes, it fails on 14.1. I was too quick to conclude it was fixed on 14.*.

[Bug tree-optimization/119480] Wrong code generated in simple program that uses LLVM::map_to_vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119480 --- Comment #1 from Mark Bourgeault --- https://www.godbolt.org/z/T5qE5M87T shows the issue on Compiler Explorer

[Bug tree-optimization/119480] New: Wrong code generated in simple program that uses LLVM::map_to_vector

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=119480 Bug ID: 119480 Summary: Wrong code generated in simple program that uses LLVM::map_to_vector Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal

[Bug c++/113791] New: Incorrect handling of lvalue to rvalue conversion in ternary operator

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113791 Bug ID: 113791 Summary: Incorrect handling of lvalue to rvalue conversion in ternary operator Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal

[Bug libstdc++/108636] [10 Regression] C++20 undefined reference to `std::filesystem::__cxx11::path::_List::type(std::filesystem::__cxx11::path::_Type)' with -fkeep-inline-functions

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108636 Mark Bourgeault changed: What|Removed |Added CC||Mark_B53 at yahoo dot com --- Comment

[Bug tree-optimization/111894] New: Missed vectorization opportunity

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111894 Bug ID: 111894 Summary: Missed vectorization opportunity Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: tree-optimiza

[Bug c++/108591] New: void{} does not error out in 12.1

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108591 Bug ID: 108591 Summary: void{} does not error out in 12.1 Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++

[Bug libstdc++/108487] [10/11/12/13 Regression] ~20-30x slowdown in populating std::vector from std::ranges::iota_view

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108487 --- Comment #8 from Mark Bourgeault --- What about something like this? #if __cplusplus >= 201709L template> vector(_InputIterator __first, _InputIterator __last, const allocator_type& __a = allocator_type())

[Bug libstdc++/108487] [10/11/12/13 Regression] ~20-30x slowdown in populating std::vector from std::ranges::iota_view

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108487 --- Comment #7 from MARK BOURGEAULT --- >> See PR 100070 for suggestions to deal with such iterators better. Unless I'm missing something, there's nothing in that PR that a *user* can do to achieve the gcc 10.3 performance w/ std::iota_view.

[Bug tree-optimization/108487] [10/11/12/13 Regression] ~20-30x slowdown in populating std::vector from std::ranges::iota_view

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108487 --- Comment #2 from MARK BOURGEAULT --- >> For fn1, assembly of the inner loop should be identical, so I think the 20% >> you were seeing may result from different loop alignment with respect to 32b >> fetch boundary Yes, it does appear that t

[Bug rtl-optimization/108487] New: ~20-30x slowdown in populating std::vector from std::ranges::iota_view

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108487 Bug ID: 108487 Summary: ~20-30x slowdown in populating std::vector from std::ranges::iota_view Product: gcc Version: 12.2.0 Status: UNCONFIRMED Severity: norma

[Bug rtl-optimization/107690] New: Regression in ranges::transform vectorization

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107690 Bug ID: 107690 Summary: Regression in ranges::transform vectorization Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: rt

[Bug c++/107188] New: using concept type-constraint declared in nested namespace causes incorrect compilation error

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107188 Bug ID: 107188 Summary: using concept type-constraint declared in nested namespace causes incorrect compilation error Product: gcc Version: 13.0 Status: UNCONFIRMED