public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/113772] [14 Regression] atomic.d compile error since recent upstream imports.
Date: Mon, 05 Feb 2024 17:52:28 +0000	[thread overview]
Message-ID: <bug-113772-4-uzbQZiboil@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113772-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113772

--- Comment #4 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Looking at gcc/builtins.cc, I have a bad feeling that the only compile-time
values one can get out of this built-in are "true" and "defer to run-time"

---
/* Return a one or zero if it can be determined that object ARG1 of size ARG 
   is lock free on this architecture.  */

static tree
fold_builtin_atomic_is_lock_free (tree arg0, tree arg1)
{
  if (!flag_inline_atomics)
    return NULL_TREE;

  /* If it isn't always lock free, don't generate a result.  */
  if (fold_builtin_atomic_always_lock_free (arg0, arg1) == boolean_true_node)
    return boolean_true_node;

  return NULL_TREE;
} 
---

The upstream contributor who tested this on x86 likely didn't get this because
it's all lock-free.

  parent reply	other threads:[~2024-02-05 17:52 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-05 16:10 [Bug d/113772] New: " iains at gcc dot gnu.org
2024-02-05 16:12 ` [Bug d/113772] " iains at gcc dot gnu.org
2024-02-05 17:39 ` ibuclaw at gdcproject dot org
2024-02-05 17:41 ` ibuclaw at gdcproject dot org
2024-02-05 17:51 ` iains at gcc dot gnu.org
2024-02-05 17:52 ` ibuclaw at gdcproject dot org [this message]
2024-02-05 18:04 ` iains at gcc dot gnu.org
2024-02-05 18:06 ` iains at gcc dot gnu.org
2024-02-05 18:27 ` ibuclaw at gdcproject dot org
2024-02-05 18:31 ` ibuclaw at gdcproject dot org
2024-02-05 18:32 ` ibuclaw at gdcproject dot org
2024-02-05 20:57 ` iains at gcc dot gnu.org
2024-02-05 22:50 ` ibuclaw at gdcproject dot org
2024-02-06  6:18 ` dkm at gcc dot gnu.org
2024-02-07 22:20 ` pinskia at gcc dot gnu.org
2024-02-08  2:48 ` doko at gcc dot gnu.org
2024-02-12 16:08 ` cvs-commit at gcc dot gnu.org
2024-02-12 16:20 ` ibuclaw at gdcproject dot org

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=bug-113772-4-uzbQZiboil@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.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).