From: Tom Tromey <tom@tromey.com>
To: Alan Modra <amodra@gmail.com>
Cc: Tom Tromey <tom@tromey.com>, binutils@sourceware.org
Subject: Re: [PATCH v2 1/2] Thread-safety improvements for bfd_check_format_matches
Date: Tue, 16 Apr 2024 13:51:58 -0600 [thread overview]
Message-ID: <877cgxgk69.fsf@tromey.com> (raw)
In-Reply-To: <Zh3s7MoQfC/FsVjH@squeak.grove.modra.org> (Alan Modra's message of "Tue, 16 Apr 2024 12:43:48 +0930")
>>>>> "Alan" == Alan Modra <amodra@gmail.com> writes:
Alan> You need this or something like it on top of your patch, otherwise
Alan> the first element with PER_XVEC_NO_TARGET won't have targ set (and the
Alan> first element will be used for everything).
Sorry about that.
Your change looks correct to me, I'll apply it and re-send.
Tom
next prev parent reply other threads:[~2024-04-16 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-15 18:22 [PATCH v2 0/2] Fix some races seen by thread sanitizer Tom Tromey
2024-04-15 18:22 ` [PATCH v2 1/2] Thread-safety improvements for bfd_check_format_matches Tom Tromey
2024-04-16 3:13 ` Alan Modra
2024-04-16 19:51 ` Tom Tromey [this message]
2024-04-15 18:22 ` [PATCH v2 2/2] Avoid cache race in bfd_check_format_matches Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877cgxgk69.fsf@tromey.com \
--to=tom@tromey.com \
--cc=amodra@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).