[Bug c++/106434] [12/13 Regression] Spurious -Wnull-dereference when using std::unique_copy() since r12-5187-g1ae8edf5f73ca5c3

2022-08-12 Thread joshua.r.marshall.1991 at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106434 --- Comment #2 from Josh Marshall --- How involved should I be on this?

[Bug libstdc++/86188] Enhancement to std::merge, constexpr check of iterator types

2018-06-18 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86188 --- Comment #2 from Josh Marshall --- That looks similar enough. But I think the Bidirectional iterator tag in the case of sorting is expressive enough and for std::merge, either forward iterator tags or output iterator tags would express the de

[Bug libstdc++/86188] New: Enhancement to std::merge, constexpr check of iterator types

2018-06-16 Thread joshua.r.marshall.1991 at gmail dot com
Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: joshua.r.marshall.1991 at gmail dot com Target Milestone: --- Before I go in an submitting patches all willy-nilly, I've been poking at std::merge and I think I see that it

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-06 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #15 from Josh Marshall --- That is bizarre. Then did I stumble upon the vestiges of elements of the standard which were partially removed prior to 2003? This may be open for awhile. I'll start on a proposal for 2020. I'll also hav

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-06 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #12 from Josh Marshall --- I can now say why this bothers me from a design perspective. If the requirement you are giving is correct, then the distance_type template parameter must always be signed and always describe the distance be

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-06 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #11 from Josh Marshall --- Then please give me a concrete reference.

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-06 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #9 from Josh Marshall --- Confirmed in 8.1.1 Also, looking over the following documents: https://en.cppreference.com/w/cpp/types/ptrdiff_t https://en.cppreference.com/w/cpp/iterator/iterator http://en.cppreference.com/w/cpp/iterator/

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-05 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #8 from Josh Marshall --- If this code is to work, given that this is the only way to track in detail use of various stdlib internals, one of two things need to change. Either all assignments to _Distance need to be explicitly wrappe

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-04 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #7 from Josh Marshall --- I got the licensing cleared up over the weekend, and so I can actually reference the code in question for this. https://github.com/anadon/Sort-Comparisons-and-Performance-metrics The only way to track use o

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-03 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #6 from Josh Marshall --- There is a kind of legacy manual specification, and a reason for that was for tracking usage. What I'm working on is adapted from David Musser's 1997 code which was using proposed and developmental stdlib co

[Bug libstdc++/86015] Better handling of iterator distances

2018-06-01 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #4 from Josh Marshall --- These changes may make the stdlib implementation more robust, but there may be an argument to stick to the more strict standard or tweak the standard. Could you link to the standard doc you're pulling from?

[Bug c++/86015] Better handling of iterator distances

2018-05-31 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #2 from Josh Marshall --- There are also lines close by which call std::distance() which need to be similarly wrapped.

[Bug c++/86015] Better handling of iterator distances

2018-05-31 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86015 --- Comment #1 from Josh Marshall --- It looks like wrappings would be applicable at the following lines: 296, 297, 2438, 2439, 2494, 2495 using https://github.com/gcc-mirror/gcc/blob/master/libstdc%2B%2B-v3/include/bits/stl_algo.h as reference

[Bug c++/86015] New: Better handling of iterator distances

2018-05-31 Thread joshua.r.marshall.1991 at gmail dot com
++ Assignee: unassigned at gcc dot gnu.org Reporter: joshua.r.marshall.1991 at gmail dot com Target Milestone: --- I'm writing containers for containers to track usage and operations for performance metrics. I've found it impossible to allow implicit conversion from integer

[Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function

2018-05-17 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763 Josh Marshall changed: What|Removed |Added Status|WAITING |RESOLVED Resolution|---

[Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function

2018-05-17 Thread joshua.r.marshall.1991 at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763 --- Comment #2 from Josh Marshall --- Created attachment 44143 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44143&action=edit Example file I got to making an example, but it seems that this is no longer a problem. I'm going to close thi

[Bug c++/85763] New: Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function

2018-05-12 Thread joshua.r.marshall.1991 at gmail dot com
: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: joshua.r.marshall.1991 at gmail dot com Target Milestone: --- For friend functions with template parameters, it would be nice to have the structure