From: Richard Biener <richard.guenther@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Jakub Jelinek <jakub@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 2/3] lto-plugin: make claim_file_handler thread-safe
Date: Fri, 24 Jun 2022 10:37:00 +0200 [thread overview]
Message-ID: <BF327155-53C6-4687-8B15-E1F380FA4FFE@gmail.com> (raw)
In-Reply-To: <ad68664f-cd03-5400-790d-ba41832a7ebd@suse.cz>
> Am 21.06.2022 um 10:43 schrieb Martin Liška <mliska@suse.cz>:
>
> On 6/21/22 09:56, Richard Biener wrote:
>>> On Mon, Jun 20, 2022 at 12:20 PM Martin Liška <mliska@suse.cz> wrote:
>>>
>>> On 6/20/22 11:32, Richard Biener wrote:
>>>> On Thu, Jun 16, 2022 at 9:01 AM Martin Liška <mliska@suse.cz> wrote:
>>>>>
>>>>> lto-plugin/ChangeLog:
>>>>>
>>>>> * lto-plugin.c (plugin_lock): New lock.
>>>>> (claim_file_handler): Use mutex for critical section.
>>>>> (onload): Initialize mutex.
>>>>> ---
>>>>> lto-plugin/lto-plugin.c | 16 +++++++++++++++-
>>>>> 1 file changed, 15 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/lto-plugin/lto-plugin.c b/lto-plugin/lto-plugin.c
>>>>> index 00b760636dc..13118c4983c 100644
>>>>> --- a/lto-plugin/lto-plugin.c
>>>>> +++ b/lto-plugin/lto-plugin.c
>>>>> @@ -55,6 +55,7 @@ along with this program; see the file COPYING3. If not see
>>>>> #include <unistd.h>
>>>>> #include <fcntl.h>
>>>>> #include <sys/types.h>
>>>>> +#include <pthread.h>
>>>>
>>>> Not sure if we support any non-pthread target for building the LTO
>>>> plugin, but it
>>>> seems we have
>>>>
>>>> # Among non-ELF, only Windows platforms support the lto-plugin so far.
>>>> # Build it unless LTO was explicitly disabled.
>>>> case $target in
>>>> *-cygwin* | *-mingw*) build_lto_plugin=$enable_lto ;;
>>>>
>>>> which suggests that at least build validating the above with --enable-lto
>>>
>>> Verified that it's fine.
>>>
>>>>
>>>> IIRC we have gthr-*.h in libgcc/, not sure if that's usable in a
>>>> host linker plugin.
>>>>
>>>>> #ifdef HAVE_SYS_WAIT_H
>>>>> #include <sys/wait.h>
>>>>> #endif
>>>>> @@ -157,6 +158,9 @@ enum symbol_style
>>>>> ss_uscore, /* Underscore prefix all symbols. */
>>>>> };
>>>>>
>>>>> +/* Plug-in mutex. */
>>>>> +static pthread_mutex_t plugin_lock;
>>>>> +
>>>>> static char *arguments_file_name;
>>>>> static ld_plugin_register_claim_file register_claim_file;
>>>>> static ld_plugin_register_all_symbols_read register_all_symbols_read;
>>>>> @@ -1262,15 +1266,18 @@ claim_file_handler (const struct ld_plugin_input_file *file, int *claimed)
>>>>> lto_file.symtab.syms);
>>>>> check (status == LDPS_OK, LDPL_FATAL, "could not add symbols");
>>>>>
>>>>> + pthread_mutex_lock (&plugin_lock);
>>>>> num_claimed_files++;
>>>>> claimed_files =
>>>>> xrealloc (claimed_files,
>>>>> num_claimed_files * sizeof (struct plugin_file_info));
>>>>> claimed_files[num_claimed_files - 1] = lto_file;
>>>>> + pthread_mutex_unlock (&plugin_lock);
>>>>>
>>>>> *claimed = 1;
>>>>> }
>>>>>
>>>>> + pthread_mutex_lock (&plugin_lock);
>>>>> if (offload_files == NULL)
>>>>> {
>>>>> /* Add dummy item to the start of the list. */
>>>>> @@ -1333,11 +1340,12 @@ claim_file_handler (const struct ld_plugin_input_file *file, int *claimed)
>>>>> offload_files_last_lto = ofld;
>>>>> num_offload_files++;
>>>>> }
>>>>> + pthread_mutex_unlock (&plugin_lock);
>>>>>
>>>>> goto cleanup;
>>>>>
>>>>> err:
>>>>> - non_claimed_files++;
>>>>> + __atomic_fetch_add (&non_claimed_files, 1, __ATOMIC_RELAXED);
>>>>
>>>> is it worth "optimizing" this with yet another need for target specific support
>>>> (just use pthread_mutex here as well?)
>>>
>>> Sure.
>>>
>>> May I install the patch with the change?
>>
>> Can you at least add a configure check for pthread.h and maybe disable
>> locking when not found or erroring out? I figure we have GCC_AC_THREAD_HEADER
>
> All right, let's error out then.
>
>> for the gthr.h stuff using $target_thread_file (aka --enable-threads=XYZ),
>> but as said that's for the target and I don't see any host uses. We might also
>> add an explicit list of hosts (*-linux*?) where we enable thread support for
>> lto-plugin, providing opt-in (so you'd have to wrap the mutex taking or
>> if-def it out).
>>
>> I think you also need to link lto-plugin with -pthread, no?
>
> Yep.
>
> Please see the updated patch.
>
Please use -pthread instead of -lpthread
Otherwise looks OK to me.
>> On linux
>> it might work omitting that but I'm not sure other libc have serial pthread
>> stubs in their libc. BFD ld definitely doesn't link against pthread so
>> dlopening lto-plugin will fail (also not all libc might like
>> initializing threads
>> from a dlopen _init).
>
> What initializing threads do you mean?
It’s target dependent what kind of global state init need to be done when any pthread facility is used.
Richard
> Martin
>
>>
>> Richard.
>>
>>> Cheers,
>>> Martin
>>>
>>>>
>>>>> free (lto_file.name);
>>>>>
>>>>> cleanup:
>>>>> @@ -1415,6 +1423,12 @@ onload (struct ld_plugin_tv *tv)
>>>>> struct ld_plugin_tv *p;
>>>>> enum ld_plugin_status status;
>>>>>
>>>>> + if (pthread_mutex_init (&plugin_lock, NULL) != 0)
>>>>> + {
>>>>> + fprintf (stderr, "mutex init failed\n");
>>>>> + abort ();
>>>>> + }
>>>>> +
>>>>> p = tv;
>>>>> while (p->tv_tag)
>>>>> {
>>>>> --
>>>>> 2.36.1
>>>>>
>>>>>
> <0001-lto-plugin-make-claim_file_handler-thread-safe.patch>
next prev parent reply other threads:[~2022-06-24 8:37 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 7:51 [PATCH] Support LDPT_GET_SYMBOLS_V3 Martin Liška
2022-05-04 12:20 ` [PATCH] lto-plugin: add support for feature detection Martin Liška
2022-05-04 12:32 ` Alexander Monakov
2022-05-04 12:41 ` Martin Liška
2022-05-04 13:10 ` Alexander Monakov
2022-05-04 13:31 ` Martin Liška
2022-05-04 15:06 ` Bernhard Reutner-Fischer
2022-05-05 6:15 ` Richard Biener
2022-05-05 6:31 ` Richard Biener
2022-05-05 10:52 ` Alexander Monakov
2022-05-05 12:50 ` Martin Liška
2022-05-06 14:46 ` Alexander Monakov
2022-05-09 9:05 ` Martin Liška
2022-05-15 6:57 ` Rui Ueyama
2022-05-15 7:53 ` Alexander Monakov
2022-05-15 8:07 ` Rui Ueyama
2022-05-15 8:50 ` Alexander Monakov
2022-05-15 10:01 ` Rui Ueyama
2022-05-15 10:09 ` Alexander Monakov
2022-05-15 10:32 ` Rui Ueyama
2022-05-15 11:37 ` Alexander Monakov
2022-05-15 11:52 ` Rui Ueyama
2022-05-15 12:07 ` Alexander Monakov
2022-05-16 2:41 ` Rui Ueyama
2022-05-16 6:38 ` Alexander Monakov
2022-05-16 8:37 ` Rui Ueyama
2022-05-16 9:10 ` Richard Biener
2022-05-16 9:15 ` Alexander Monakov
2022-05-16 9:25 ` Jan Hubicka
2022-05-16 9:38 ` Martin Liška
2022-05-16 9:50 ` Jan Hubicka
2022-05-16 10:22 ` Richard Biener
2022-05-16 9:58 ` Rui Ueyama
2022-05-16 10:28 ` Richard Biener
2022-05-16 10:44 ` Rui Ueyama
2022-05-16 12:04 ` Martin Liška
2022-05-16 13:07 ` Rui Ueyama
2022-05-16 13:38 ` Alexander Monakov
2022-05-16 15:16 ` Alexander Monakov
2022-05-17 6:20 ` Richard Biener
2022-05-17 13:44 ` Martin Liška
2022-06-16 6:59 ` [PATCH 1/3] lto-plugin: support LDPT_GET_SYMBOLS_V3 Martin Liška
2022-06-20 9:23 ` Richard Biener
2022-06-16 7:01 ` [PATCH 2/3] lto-plugin: make claim_file_handler thread-safe Martin Liška
2022-06-20 9:32 ` Richard Biener
2022-06-20 10:20 ` Martin Liška
2022-06-21 7:56 ` Richard Biener
2022-06-21 8:43 ` Martin Liška
2022-06-24 8:37 ` Richard Biener [this message]
2022-06-16 7:01 ` [PATCH 3/3] lto-plugin: implement LDPT_GET_API_VERSION Martin Liška
2022-06-16 8:00 ` Alexander Monakov
2022-06-16 12:25 ` Martin Liška
2022-06-20 9:35 ` Richard Biener
2022-06-20 13:01 ` Martin Liška
2022-06-30 6:43 ` Rui Ueyama
2022-06-30 8:42 ` Martin Liška
2022-07-01 6:36 ` Richard Biener
2022-07-04 14:17 ` Martin Liška
2022-07-07 2:19 ` Rui Ueyama
2022-07-08 8:42 ` Martin Liška
2022-07-08 12:41 ` Alexander Monakov
2022-07-11 7:23 ` Rui Ueyama
2022-07-11 9:16 ` Alexander Monakov
2022-07-11 9:55 ` Richard Biener
2022-07-11 10:51 ` Martin Liška
2022-07-11 12:24 ` Rui Ueyama
2022-07-11 12:38 ` Alexander Monakov
2022-07-11 12:51 ` Martin Liška
2022-07-12 1:36 ` Rui Ueyama
2022-07-11 16:35 ` Alexander Monakov
2022-07-12 6:28 ` Richard Biener
2022-07-12 7:36 ` Martin Liška
2022-07-12 11:50 ` Rui Ueyama
2022-07-12 13:21 ` Richard Biener
2022-07-12 13:31 ` Martin Liška
2022-07-13 7:44 ` Rui Ueyama
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=BF327155-53C6-4687-8B15-E1F380FA4FFE@gmail.com \
--to=richard.guenther@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=mliska@suse.cz \
--cc=ro@cebitec.uni-bielefeld.de \
/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).