[Bug build/29359] [gdb/build] Flush out thread sanitizer issues

["vries at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=29359

Tom de Vries <vries at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
   Target Milestone|---                         |13.1
         Resolution|---                         |FIXED

--- Comment #4 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #3)
> (In reply to Tom de Vries from comment #2)
> > Another idea I had was to make sure that this in parallel_for:
> > ...
> >   /* Process all the remaining elements in the main thread.  */
> >   return results.finish ([=] ()
> >     {
> >       return callback (first, last);
> >     });
> > ...
> > is not run on the main thread, but only in the thread pool, to maximize the
> > skew between main thread and parallel for, but given that the parallel for
> > waits for the elements to finish, I don't expects any results from this
> > currently.
> > 
> > But if we start to use thread_local memory, this could be something useful
> > to try.
> 
> https://sourceware.org/pipermail/gdb-patches/2022-July/190830.html

This was not deemed acceptable in review.

I've done all I could think of, so I'm marking this task done, even though
there are no actual resulting commits.

-- 
You are receiving this mail because:
You are on the CC list for the bug.