From: Nathan Chancellor <nathan@kernel.org>
To: ci_notify@linaro.org
Cc: Arthur Eubanks <aeubanks@google.com>, llvm@lists.linux.dev
Subject: Re: [TCWG CI] Regression caused by llvm: [GlobalOpt] Perform store->dominated load forwarding for stored once globals
Date: Tue, 21 Jun 2022 08:38:03 -0700 [thread overview]
Message-ID: <YrHl20+cA20MwpAP@dev-arch.thelio-3990X> (raw)
In-Reply-To: <786830855.4416.1655743809453@jenkins.jenkins>
On Mon, Jun 20, 2022 at 04:50:08PM +0000, ci_notify@linaro.org wrote:
> [TCWG CI] Regression caused by llvm: [GlobalOpt] Perform store->dominated load forwarding for stored once globals:
> commit 6f348b146b69a50d5fb1b9fbfd14bc1d204e45c4
> Author: Arthur Eubanks <aeubanks@google.com>
>
> [GlobalOpt] Perform store->dominated load forwarding for stored once globals
>
> Results regressed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 37
> # First few build errors in logs:
> # 00:00:51 error: include/uapi/linux/acct.h: leak CONFIG_M68K to user-space
> # 00:00:51 make[1]: *** [scripts/Makefile.headersinst:63: usr/include/linux/acct.h] Error 1
> # 00:00:51 make: *** [Makefile:1381: headers] Error 2
I know this change was reverted already (13ff7d6f393d) but I think the
only way this change could be responsible for this error is through a
miscompile of scripts/unifdef.c, as scripts/headers_install.sh relies on
that tool to strip away !__KERNEL__ sections. I can try to reduce
something out if necessary.
Cheers,
Nathan
prev parent reply other threads:[~2022-06-21 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 16:50 [TCWG CI] Regression caused by llvm: [GlobalOpt] Perform store->dominated load forwarding for stored once globals ci_notify
2022-06-21 15:38 ` Nathan Chancellor [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=YrHl20+cA20MwpAP@dev-arch.thelio-3990X \
--to=nathan@kernel.org \
--cc=aeubanks@google.com \
--cc=ci_notify@linaro.org \
--cc=llvm@lists.linux.dev \
/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.