public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] gcov: No atomic ops for -fprofile-update=single
Date: Thu, 23 Nov 2023 15:30:27 +0100	[thread overview]
Message-ID: <0ee31f0d-53c2-4e43-9b45-04812fa85d5f@embedded-brains.de> (raw)
In-Reply-To: <CAFiYyc0fv6khetoVnsannD819WOtVyVdGSRf9_cu0rzs2t8o1A@mail.gmail.com>

On 23.11.23 15:19, Richard Biener wrote:
> On Thu, Nov 23, 2023 at 2:47 PM Sebastian Huber
> <sebastian.huber@embedded-brains.de>  wrote:
>> gcc/ChangeLog:
>>          PR tree-optimization/112678
>>
>>          * tree-profile.cc (tree_profiling): Do not use atomic operations
>>          for -fprofile-update=single.
>> ---
>>   gcc/tree-profile.cc | 8 +++++---
>>   1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/gcc/tree-profile.cc b/gcc/tree-profile.cc
>> index 1ac0fdb3bc98..9c8fdb8b18f4 100644
>> --- a/gcc/tree-profile.cc
>> +++ b/gcc/tree-profile.cc
>> @@ -767,6 +767,7 @@ tree_profiling (void)
>>       = HAVE_sync_compare_and_swapsi || HAVE_atomic_compare_and_swapsi;
>>     bool have_atomic_8
>>       = HAVE_sync_compare_and_swapdi || HAVE_atomic_compare_and_swapdi;
>> +  bool needs_split = gcov_type_size == 8 && !have_atomic_8 && have_atomic_4;
>>     if (!can_support_atomic)
>>       {
>>         if (gcov_type_size == 4)
>> @@ -775,6 +776,9 @@ tree_profiling (void)
>>          can_support_atomic = have_atomic_8;
>>       }
>>
>> +  if (flag_profile_update != PROFILE_UPDATE_SINGLE && needs_split)
>> +    counter_update = COUNTER_UPDATE_ATOMIC_PARTIAL;
>> +
> I wonder if it's cleaner to set can_support_atomic when we can support
> it with splitting instead, avoiding a != PROFILE_UPDATE_SINGLE check
> here?

The bug was that counter_update was set to COUNTER_UPDATE_ATOMIC_PARTIAL 
for -fprofile-update=single. I don't think we can get rid of the 
flag_profile_update != PROFILE_UPDATE_SINGLE without changing this whole 
code block considerably.

-- 
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax:   +49-89-18 94 741 - 08

Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/

      reply	other threads:[~2023-11-23 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-23 13:47 Sebastian Huber
2023-11-23 14:19 ` Richard Biener
2023-11-23 14:30   ` Sebastian Huber [this message]

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=0ee31f0d-53c2-4e43-9b45-04812fa85d5f@embedded-brains.de \
    --to=sebastian.huber@embedded-brains.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).