Andrea (Drea) Tamar PinskiOct 24

Let's try something different today.
Reply with your favorite still opened gcc bug report (https://gcc.gnu.org/bugzilla/) . I am going to put together a poll next week on which bug report i should fix and that poll will be based on the responses here.
Disclaimer, X86_64 and aarch64 target specific bugs are OK, other backends depending on the bug report might be fine but I will reply to your toot if it will be included in the poll. If I get a lot of responses, I might have a few polls to narrow down which one I implement.

This is for 2 reasons, one to show gcc developers still care about the bug reports (especially with over 18k of them filed) and 2 to give an opportunity to users to see more of the process. Also sometimes I like giving back to the users of gcc.

GCC Bugzilla Main Page

Show threadDan RileyOct 25

@pinskia I guess everyone is shy about admitting to a favorite bug? Well…if libstdc++ is in scope, I nominate https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77704

That’s been responsible for at least a couple of difficult to find failures in multithreaded code.

77704 – Data race on std::ctype<char>

Show threadAndrea (Drea) Tamar Pinski

@dan131riley

libstdc++ is definitely in the scope. Though I have not worked as much in the library as other areas of GCC.

I see Jonathan fixed one of the data races.

Oct 25 at 12:32amWeb
Show threadJ.W.Oct 25
@pinskia @dan131riley I think I have a patch for the remaining data race, but it adds overhead. I'll dig it out and refresh my memory