[Bug libstdc++/114325] std::format gives incorrect results for negative numbers

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114325 Michael Duggan changed: What|Removed |Added CC||mwd at md5i dot com --- Comment #1

[Bug gcov-profile/110827] C++20 coroutines aren't being measured by gcov

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827 --- Comment #10 from Michael Duggan --- To sum up what I have figured out, C++ transforms the coroutine "function" into a trio of functions: a ramp function, an actor function, and a destruction function. The ramp function acts as the actual

[Bug gcov-profile/110827] C++20 coroutines aren't being measured by gcov

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827 --- Comment #9 from Michael Duggan --- More data: The coroutine actor is marked as artificial in coro_build_actor_or_destroy_function. As a result, it is completely ignored by gcov. In gcov's process_all_functions function, artificial

[Bug gcov-profile/110827] C++20 coroutines aren't being measured by gcov

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827 --- Comment #8 from Michael Duggan --- Using the better test case, I have determined that the coroutine _is_ being instrumented with gcov counters. When disassembled, the output contains the following in the bar() actor function: Dump of

[Bug gcov-profile/110827] C++20 coroutines aren't being measured by gcov

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827 Michael Duggan changed: What|Removed |Added Attachment #55648|0 |1 is obsolete|

[Bug gcov-profile/110827] C++20 coroutines aren't being measured by gcov

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827 --- Comment #4 from Michael Duggan --- I should be more explicit. The `std::cout` line in the example is just a placeholder for "does some work here," and this example is specifically the simplest version of a coroutine I could come up with

[Bug gcov-profile/110827] C++20 coroutines aren't being measured by gcov

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827 --- Comment #3 from Michael Duggan --- (In reply to Richard Biener from comment #1) > I'm seeing all code properly instrumented. The coverage I see is > > -:1:#include > -:2:#include > -:3: > -:

[Bug gcov-profile/110827] New: C++20 coroutines aren't being measured by gcov

: gcov-profile Assignee: unassigned at gcc dot gnu.org Reporter: mwd at md5i dot com CC: marxin at gcc dot gnu.org Target Milestone: --- Created attachment 55648 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55648=edit Simple bug exemplar When compil

[Bug libstdc++/108265] New: chrono::hh_mm_ss can't be constructed from unsigned durations

Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: mwd at md5i dot com Target Milestone: --- chrono::hh_mm_ss can't be constructed from unsigned durations. For example: #include int main() { std::chrono::duration dur

[Bug libstdc++/108258] std::ranges::begin() fails on zero sized std::array

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108258 --- Comment #1 from Michael Duggan --- Preprocessed source will be added once I've reduced it. In the meantime, the non-preprocessed source in the comment should be enough to trigger the problem with the specified version of gcc.

[Bug libstdc++/108258] New: std::ranges::begin() fails on zero sized std::array

Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: mwd at md5i dot com Target Milestone: --- The following snippet fails to compile (with -std=c++20) in snapshot gcc-13-20221225. #include #include static constexpr std::array a; static constexpr

[Bug tree-optimization/106247] GCC12 warning in Eigen: array subscript is partly outside array bounds

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106247 --- Comment #8 from Michael Duggan --- Created attachment 53533 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53533=edit Reduced bug exemplar

[Bug tree-optimization/106247] GCC12 warning in Eigen: array subscript is partly outside array bounds

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106247 Michael Duggan changed: What|Removed |Added CC||mwd at md5i dot com --- Comment #7

[Bug libstdc++/71500] regex::icase only works on first character in a range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 --- Comment #12 from Michael Duggan --- Just a ping. I haven't seen a fix for this (even the basic case) in the repo yet. I'm going to suggest that you at least install your initial patch, as it will work in the vast majority of cases.

[Bug libstdc++/71500] regex::icase only works on first character in a range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 --- Comment #11 from Michael Duggan --- "timshen at gcc dot gnu.org" writes: > (In reply to Michael Duggan from comment #9) >> I will make two suggestions. The initial suggestion is simple enough: >> Given that

[Bug libstdc++/71500] regex::icase only works on first character in a range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 --- Comment #9 from Michael Duggan --- "timshen at gcc dot gnu.org" writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 > > --- Comment #8 from Tim Shen --- > (In reply to Michael Duggan from comment #7) >>

[Bug libstdc++/71500] regex::icase only works on first character in a range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 --- Comment #7 from Michael Duggan --- "timshen at gcc dot gnu.org" writes: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 > > --- Comment #6 from Tim Shen --- > (In reply to mwd from comment #5) >> All of the

[Bug libstdc++/71500] regex::icase only works on first character in a range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 --- Comment #3 from Michael Duggan --- Still fails for the following code: #include #include #include using namespace std; void check(const string& s, regex re) { cout << s << " : " << (regex_match(s, re) ? "Match" : "Nope") << endl; }

[Bug libstdc++/71500] regex::icase only works on first character in a range

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500 Michael Duggan changed: What|Removed |Added CC||mwd at md5i dot com --- Comment #1