[Bug c++/64169] New: Partial template specialization of reference-qualified operator templates

2014-12-03 Thread knoepfel at fnal dot gov
: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: knoepfel at fnal dot gov System : x86_64-apple-darwin13.4.0 options: -Wall -Wextra std: c++1y The preprocessed version of the below code looks identical except for the

[Bug c++/111685] New: Segfault while sorting on array element address

2023-10-03 Thread knoepfel at fnal dot gov via Gcc-bugs
Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: knoepfel at fnal dot gov Target Milestone: --- The following file (`sort-bug.cpp`) results in a segmentation violation: ``` #include #include #include #include int main() { std::vector vnums{1, 5, 4}; std

[Bug libstdc++/111685] Segfault while sorting on array element address

2023-10-03 Thread knoepfel at fnal dot gov via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111685 --- Comment #3 from Kyle Knoepfel --- @Andrew Pinski, yes I surmised as much. My difficulty, though, is in understanding if this is the correct behavior according to the standard's specification of std::sort, which presumably is reasonably summ

[Bug libstdc++/111685] Segfault while sorting on array element address

2023-10-03 Thread knoepfel at fnal dot gov via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111685 Kyle Knoepfel changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID

[Bug libstdc++/111685] Segfault while sorting on array element address

2023-10-05 Thread knoepfel at fnal dot gov via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111685 Kyle Knoepfel changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED