All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: ci_notify@linaro.org
Cc: Andre Vieira <andre.simoesdiasvieira@arm.com>, llvm@lists.linux.dev
Subject: Re: [TCWG CI] Regression caused by llvm: [TypePromotion] Search from ZExt + PHI
Date: Mon, 15 Aug 2022 17:46:11 -0700	[thread overview]
Message-ID: <Yvro06Uid0t0Ou1M@dev-arch.thelio-3990X> (raw)
In-Reply-To: <1465164958.6648.1660602445528@jenkins.jenkins>

On Mon, Aug 15, 2022 at 10:27:24PM +0000, ci_notify@linaro.org wrote:
> [TCWG CI] Regression caused by llvm: [TypePromotion] Search from ZExt + PHI:
> commit 164067918725d1ee8875e38213b6aee9be13383e
> Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
> 
>     [TypePromotion] Search from ZExt + PHI
> 
> Results regressed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_kernel_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 6329
> # First few build errors in logs:
> # 00:12:33 ld.lld: error: undefined symbol: __aeabi_uldivmod
> # 00:12:33 make: *** [Makefile:1208: vmlinux] Error 1

I noticed this towards the end of last week too:

https://github.com/ClangBuiltLinux/linux/issues/1688

I added some reduced reproducers to that thread. As I note in the
original post of that issue, I am not sure if this error is a standalone
problem or one that comes from another problem we are actively dealing
with:

https://github.com/ClangBuiltLinux/linux/issues/1666
https://github.com/llvm/llvm-project/issues/56153

Cheers,
Nathan

  reply	other threads:[~2022-08-16  0:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 22:27 [TCWG CI] Regression caused by llvm: [TypePromotion] Search from ZExt + PHI ci_notify
2022-08-16  0:46 ` Nathan Chancellor [this message]
2022-08-16  8:52   ` Andre Simoes Dias Vieira
2022-08-16 14:08     ` Andre Simoes Dias Vieira
2022-08-16 14:37       ` Andre Simoes Dias Vieira

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=Yvro06Uid0t0Ou1M@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=andre.simoesdiasvieira@arm.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.