All of lore.kernel.org
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Ian Rogers <irogers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Arnaldo Carvalho de Melo <acme@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Kan Liang <kan.liang@linux.intel.com>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH v1] perf build: Revert "enable -fno-strict-aliasing"
Date: Fri, 13 Mar 2026 14:17:21 -0700	[thread overview]
Message-ID: <abR-4crLwfNW2R7N@google.com> (raw)
In-Reply-To: <CAP-5=fUod99LkN6mX0iNizracGaHCtuDZQzU8iE7Ua61Vkb9bw@mail.gmail.com>

On Thu, Mar 12, 2026 at 01:58:31PM -0700, Ian Rogers wrote:
> On Thu, Sep 4, 2025 at 2:33 PM Ian Rogers <irogers@google.com> wrote:
> > Anyway, the intent with adding -fno-strict-aliasing was that it was
> > temporary as part of removing the libcrypto dependency and when the
> > unaligned code landed we'd do this revert.

I don't remember what's going on here but as it's not there originally,
I think we can revert to the change for now.

But it doesn't apply, care to rebase?

Thanks,
Namhyung


  reply	other threads:[~2026-03-13 21:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-04 17:44 [PATCH v1] perf build: Revert "enable -fno-strict-aliasing" Ian Rogers
2025-09-04 20:41 ` Peter Zijlstra
2025-09-04 20:59   ` Peter Zijlstra
2025-09-04 21:33     ` Ian Rogers
2026-03-12 20:58       ` Ian Rogers
2026-03-13 21:17         ` Namhyung Kim [this message]
2026-03-20 22:42           ` [PATCH v2] " Ian Rogers
2026-03-21  2:49             ` Ian Rogers
2026-03-13 23:30       ` [PATCH v1] " Peter Zijlstra

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=abR-4crLwfNW2R7N@google.com \
    --to=namhyung@kernel.org \
    --cc=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=ebiggers@google.com \
    --cc=irogers@google.com \
    --cc=jolsa@kernel.org \
    --cc=kan.liang@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.