public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: gcc-patches@gcc.gnu.org, Matthias Klose <doko@ubuntu.com>
Subject: Re: [PATCH] gcov: Fix use of __LIBGCC_HAVE_LIBATOMIC
Date: Fri, 1 Dec 2023 09:38:18 +0100	[thread overview]
Message-ID: <CAFiYyc0HB2DNVNsK=ky1sBXZQOcc5wEXGx1ifjZuwhoC12jPnw@mail.gmail.com> (raw)
In-Reply-To: <20231201081902.33740-1-sebastian.huber@embedded-brains.de>

On Fri, Dec 1, 2023 at 9:19 AM Sebastian Huber
<sebastian.huber@embedded-brains.de> wrote:
>
> libgcc/ChangeLog:

OK.

>         PR target/112777
>
>         * libgcov.h (GCOV_SUPPORTS_ATOMIC):  Honor that __LIBGCC_HAVE_LIBATOMIC is
>         always defined as either 0 or 1.
> ---
>  libgcc/libgcov.h | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/libgcc/libgcov.h b/libgcc/libgcov.h
> index f5959a8bf5c..a44f145ce25 100644
> --- a/libgcc/libgcov.h
> +++ b/libgcc/libgcov.h
> @@ -98,7 +98,7 @@ typedef unsigned gcov_type_unsigned __attribute__ ((mode (QI)));
>  /* Detect whether target can support atomic update of profilers.  */
>  #if (__SIZEOF_LONG_LONG__ == 4 && __GCC_HAVE_SYNC_COMPARE_AND_SWAP_4) \
>      || (__SIZEOF_LONG_LONG__ == 8 && __GCC_HAVE_SYNC_COMPARE_AND_SWAP_8) \
> -    || defined (__LIBGCC_HAVE_LIBATOMIC)
> +    || __LIBGCC_HAVE_LIBATOMIC
>  #define GCOV_SUPPORTS_ATOMIC 1
>  #else
>  #define GCOV_SUPPORTS_ATOMIC 0
> --
> 2.35.3
>

      reply	other threads:[~2023-12-01  8:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-01  8:19 Sebastian Huber
2023-12-01  8:38 ` Richard Biener [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='CAFiYyc0HB2DNVNsK=ky1sBXZQOcc5wEXGx1ifjZuwhoC12jPnw@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=doko@ubuntu.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sebastian.huber@embedded-brains.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).