Building the Linux kernel with Clang and LLVM
 help / color / mirror / Atom feed
From: Kees Cook <keescook@chromium.org>
To: ndesaulniers@google.com
Cc: linux-kernel@vger.kernel.org, gustavoars@kernel.org,
	dlatypov@google.com, gwan-gyeong.mun@intel.com,
	nathan@kernel.org, trix@redhat.com, llvm@lists.linux.dev
Subject: Re: [PATCH v2] overflow: disable failing tests for older clang versions
Date: Thu, 6 Oct 2022 16:01:39 -0700	[thread overview]
Message-ID: <202210061600.84A665DA2B@keescook> (raw)
In-Reply-To: <166509712398.1833114.15283539764161050044.b4-ty@chromium.org>

On Thu, Oct 06, 2022 at 03:58:49PM -0700, Kees Cook wrote:
> On Thu, 6 Oct 2022 10:17:51 -0700, Nick Desaulniers wrote:
> > Building the overflow kunit tests with clang-11 fails with:
> > 
> > $ ./tools/testing/kunit/kunit.py run --arch=arm --make_options LLVM=1 \
> > overflow
> > ...
> > ld.lld: error: undefined symbol: __mulodi4
> > ...
> > 
> > [...]
> 
> Applied to for-next/hardening, thanks!
> 
> [1/1] overflow: disable failing tests for older clang versions
>       https://git.kernel.org/kees/c/2d4df670c64c

I sent a follow-up that refactor this -- I realized I actually wanted to
see "skips" instead of just having the test go missing.

-- 
Kees Cook

      reply	other threads:[~2022-10-06 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05 22:21 [PATCH] overflow: disable failing tests for older clang versions Nick Desaulniers
2022-10-06  5:17 ` kernel test robot
2022-10-06 17:17   ` [PATCH v2] " Nick Desaulniers
2022-10-06 22:58     ` Kees Cook
2022-10-06 23:01       ` Kees Cook [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=202210061600.84A665DA2B@keescook \
    --to=keescook@chromium.org \
    --cc=dlatypov@google.com \
    --cc=gustavoars@kernel.org \
    --cc=gwan-gyeong.mun@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=trix@redhat.com \
    /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