https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71500
Michael Duggan changed:
What|Removed |Added
CC||mwd at md5i dot com
--- Comment #1
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;
}
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 ECMAScript engines I have f
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)
>> Hmm... Okay. For the sake
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.
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 regex_traits is mandated to be i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106247
Michael Duggan changed:
What|Removed |Added
CC||mwd at md5i dot com
--- Comment #7
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&action=edit
Reduced bug exemplar
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
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.
ormal
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::du
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114325
Michael Duggan changed:
What|Removed |Added
CC||mwd at md5i dot com
--- Comment #1
onent: 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&action=edit
Simple bug ex
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:
> -:
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 tha
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
Michael Duggan changed:
What|Removed |Added
Attachment #55648|0 |1
is obsolete|
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 assem
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 function
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 fu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117620
--- Comment #2 from Michael Duggan ---
I'm willing to help debug this if someone can point me to the right way to set
a breakpoint in the error reporting code such that I can walk back up the stack
and see why the error is being triggered.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117620
--- Comment #1 from Michael Duggan ---
When I said line 214, I actually meant line 213. (I modified the example but
didn't update all of my text.)
++
Assignee: unassigned at gcc dot gnu.org
Reporter: mwd at md5i dot com
Target Milestone: ---
Created attachment 59606
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=59606&action=edit
Example code
When I compile the attached test code with -std=c++20, I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=117620
Michael Duggan changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
--- Comment #15 from Michael Duggan ---
Would it be possible for one of these to make it into version 15?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
--- Comment #17 from Michael Duggan ---
Gcov doesn't have access to the function declaration, only to the information
that has been output to the count and graph files. Neither of those contain
any information (as far as I can tell) that would
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
--- Comment #19 from Michael Duggan ---
I submitted a patch. I also recently thought of another potential solution.
We could patch the code that outputs the function information for the graph
file, changing it to *not* mark the actor function
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
--- Comment #12 from Michael Duggan ---
I finally got around to this experiment today, after more than a year. I
changed this line in `coro_build_actor_or_destory_function` from:
DECL_ARTIFICIAL (fn) = true;
to
DECL_ARTIFICIAL (fn) = !act
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110827
--- Comment #14 from Michael Duggan ---
So, I applied the following patch instead, with identical results. Pro:
doesn't change the artificiality status of the function. Con: more complex
code.
1 file changed, 34 insertions(+), 2 deletions(-)
28 matches
Mail list logo
