Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: linaro-toolchain@lists.linaro.org
Cc: llvm@lists.linux.dev
Subject: Re: [Linaro-TCWG-CI] llvmorg-21-init-262-gcff0a460ae86: Failure on arm
Date: Tue, 4 Feb 2025 13:15:22 -0700	[thread overview]
Message-ID: <20250204201522.GB3466315@ax162> (raw)
In-Reply-To: <1599984364.127113.1738492219737@jenkins.jenkins>

On Sun, Feb 02, 2025 at 10:30:18AM +0000, ci_notify@linaro.org wrote:
> Dear contributor,
> 
> Our automatic CI has detected problems related to your patch(es). Please find some details below.
> 
> In tcwg_kernel/llvm-master-arm-stable-allyesconfig, after:
>   | commit llvmorg-21-init-262-gcff0a460ae86
>   | Author: Bill Wendling <morbo@google.com>
>   | Date:   Thu Jan 30 15:36:13 2025 -0800
>   | 
>   |     [Clang][counted_by] Refactor __builtin_dynamic_object_size on FAMs (#122198)
>   |     
>   |     Refactoring of how __builtin_dynamic_object_size() is calculated for
>   |     flexible array members (in preparation for adding support for the
>   |     'counted_by' attribute on pointers in structs).
>   | ... 86 lines of the commit log omitted.
> 
> Produces Failure:
>   | Results changed to
>   | # reset_artifacts:
>   | -10
>   | # build_abe binutils:
>   | -9
>   | # build_kernel_llvm:
>   | -5
>   | # build_abe qemu:
>   | -2
>   | # linux_n_obj:
>   | 22473
>   | 
>   | From
>   | # reset_artifacts:
>   | -10
>   | # build_abe binutils:
>   | -9
>   | # build_kernel_llvm:
>   | -5
>   | # build_abe qemu:
>   | -2
>   | # linux_n_obj:
>   | 22474
> 
> Used configuration :
>  tcwg_kernel/llvm-master-arm-stable-allyesconfig
> 
> We track this bug report under https://linaro.atlassian.net/browse/LLVM-1541. Please let us know if you have a fix.
> 
> If you have any questions regarding this report, please ask on linaro-toolchain@lists.linaro.org mailing list.
> 
> -----------------8<--------------------------8<--------------------------8<--------------------------
> 
> The information below contains the details of the failures, and the ways to reproduce a debug environment:
> 
> 
> 
> Current build   : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-stable-allyesconfig-build/233/artifact/artifacts
> Reference build : https://ci.linaro.org/job/tcwg_kernel--llvm-master-arm-stable-allyesconfig-build/232/artifact/artifacts
> 
> Instruction to reproduce the build : https://git-us.linaro.org/toolchain/ci/interesting-commits.git/plain/llvm/sha1/cff0a460ae864505bc2a064c269ebe548aa35949/tcwg_kernel/llvm-master-arm-stable-allyesconfig/reproduction_instructions.txt
> 
> Full commit : https://github.com/llvm/llvm-project/commit/cff0a460ae864505bc2a064c269ebe548aa35949

Thanks, I think Bill fixed this with
https://github.com/llvm/llvm-project/commit/2eb44aa0a94a8d4230c1c9a0c306af16bfc92925

Cheers,
Nathan

  reply	other threads:[~2025-02-04 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-02 10:30 [Linaro-TCWG-CI] llvmorg-21-init-262-gcff0a460ae86: Failure on arm ci_notify
2025-02-04 20:15 ` Nathan Chancellor [this message]
2025-02-06 14:52   ` Christophe Lyon

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=20250204201522.GB3466315@ax162 \
    --to=nathan@kernel.org \
    --cc=linaro-toolchain@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox