From: Peter Zijlstra <peterz@infradead.org>
To: Mark Rutland <mark.rutland@arm.com>
Cc: James Clark <james.clark@arm.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Marc Zyngier <maz@kernel.org>,
Suzuki Poulose <suzuki.poulose@arm.com>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH V13 - RESEND 02/10] arm64/perf: Add BRBE registers and fields
Date: Tue, 15 Aug 2023 22:35:27 +0200 [thread overview]
Message-ID: <20230815203527.GB971582@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <ZNt3mQeGbql4oi55@FVFF77S0Q05N>
On Tue, Aug 15, 2023 at 02:05:36PM +0100, Mark Rutland wrote:
> From a quick dig, it's supposed to be like that: the GNU assembler uses a
> different operator precedence to C, and clang's assembler does the same for
> compatibility. What a great.
GNU assembler doesn't even have a consistent true value for boolean
expressions. The comparisons use -1/~0 as true value while the logical
ops use 1.
It's as if they purposefully want to mess you up :-(
https://sourceware.org/binutils/docs-2.38/as.html#Infix-Ops
next prev parent reply other threads:[~2023-08-15 20:36 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-11 8:24 [PATCH V13 - RESEND 00/10] arm64/perf: Enable branch stack sampling Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 01/10] drivers: perf: arm_pmu: Add new sched_task() callback Anshuman Khandual
2023-08-10 5:05 ` Anshuman Khandual
2023-08-10 9:41 ` Will Deacon
2023-08-10 11:49 ` Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 02/10] arm64/perf: Add BRBE registers and fields Anshuman Khandual
2023-07-28 16:20 ` Will Deacon
2023-07-28 16:52 ` James Clark
2023-07-31 2:33 ` Anshuman Khandual
2023-07-31 8:07 ` James Clark
2023-07-31 9:06 ` Mark Rutland
2023-07-31 12:19 ` Anshuman Khandual
2023-08-15 10:17 ` James Clark
2023-08-15 13:05 ` Mark Rutland
2023-08-15 20:35 ` Peter Zijlstra [this message]
2023-07-11 8:24 ` [PATCH V13 - RESEND 03/10] arm64/perf: Add branch stack support in struct arm_pmu Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 04/10] arm64/perf: Add branch stack support in struct pmu_hw_events Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 05/10] arm64/perf: Add branch stack support in ARMV8 PMU Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 06/10] arm64/perf: Enable branch stack events via FEAT_BRBE Anshuman Khandual
2023-07-11 19:26 ` Randy Dunlap
2023-07-12 2:42 ` Anshuman Khandual
2023-07-25 7:12 ` Yang Shen
2023-07-25 11:42 ` Anshuman Khandual
2023-07-25 13:29 ` Suzuki K Poulose
2023-07-26 5:32 ` Anshuman Khandual
2023-08-02 12:40 ` Suzuki K Poulose
2023-08-03 2:39 ` Anshuman Khandual
2023-07-26 6:26 ` Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 07/10] arm64/perf: Add PERF_ATTACH_TASK_DATA to events with has_branch_stack() Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 08/10] arm64/perf: Add struct brbe_regset helper functions Anshuman Khandual
2023-07-11 8:24 ` [PATCH V13 - RESEND 09/10] arm64/perf: Implement branch records save on task sched out Anshuman Khandual
2023-08-02 11:59 ` Rajnesh Kanwal
2023-08-02 19:16 ` Marc Zyngier
2023-07-11 8:24 ` [PATCH V13 - RESEND 10/10] arm64/perf: Implement branch records save on PMU IRQ Anshuman Khandual
2023-07-31 13:05 ` [PATCH V13 - RESEND 00/10] arm64/perf: Enable branch stack sampling Will Deacon
2023-08-18 3:12 ` Anshuman Khandual
2023-08-18 17:56 ` Will Deacon
2023-08-21 8:53 ` Anshuman Khandual
2023-09-27 8:37 ` Anshuman Khandual
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=20230815203527.GB971582@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=james.clark@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=mingo@redhat.com \
--cc=robh@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®