public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Mark Rutland <mark.rutland@arm.com>
Cc: Uros Bizjak <ubizjak@gmail.com>,
	Alejandro Jimenez <alejandro.j.jimenez@oracle.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Help with atomic fallback
Date: Tue, 3 Dec 2024 10:49:55 -0400	[thread overview]
Message-ID: <20241203144955.GL1253388@nvidia.com> (raw)
In-Reply-To: <Z08YT5nD6uHC-PSm@J2N7QTR9R3.cambridge.arm.com>

On Tue, Dec 03, 2024 at 02:40:15PM +0000, Mark Rutland wrote:
> > Which expands to:
> > 
> >  old = ({ typeof(ptep) __ai_ptr = (ptep); instrument_atomic_read_write(__ai_ptr, sizeof(*__ai_ptr)); raw_cmpxchg64_relaxed_not_implemented(); });
> > 
> > And no compiler error. Presumably it doesn't link, but my compiler
> > ICE's before it gets that far.
> 
> I don't think that "my compiler ICE's" implies "compiles OK".

Well, it ICE's later. I'm using the 0-day instructions with
make.cross

during RTL pass: mach
../drivers/iommu/of_iommu.c: In function 'of_iommu_configure':
../drivers/iommu/of_iommu.c:163:1: internal compiler error: in arc_ifcvt, at config/arc/arc.cc:9703
  163 | }
      | ^

> When building io-pgtable-arm.c for ARC (with your tree!) I see the same error:

Okay, I think I see it too, it got lost in all the other noise :\

Jason

      reply	other threads:[~2024-12-03 14:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03  0:38 Help with atomic fallback Jason Gunthorpe
2024-12-03  8:06 ` Uros Bizjak
2024-12-03 12:26 ` Mark Rutland
2024-12-03 13:08   ` Jason Gunthorpe
2024-12-03 14:40     ` Mark Rutland
2024-12-03 14:49       ` Jason Gunthorpe [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=20241203144955.GL1253388@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=alejandro.j.jimenez@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ubizjak@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