Outreachy Linux Kernel Community
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: outreachy@lists.linux.dev
Subject: Re: Compilation errors
Date: Fri, 01 Apr 2022 16:39:18 +0200	[thread overview]
Message-ID: <6296770.K2JlShyGXD@leap> (raw)
In-Reply-To: <20220401145714.5a0d826f@elisabeth>

On venerdì 1 aprile 2022 14:57:14 CEST Stefano Brivio wrote:
> You reported this issue three hours ago and, as far as I can tell,
> there are 672 hours in four weeks...

Nice calculation. Helpful to use to start countdown to April 22nd...
I'm just kidding :)

However, despite I reported this issue just few hours ago, it's since two
or three days that I have been struggling with this issue.
 
Finally I found the "culprit": the "Undefined Sanity Checker" (UBSan).

I had enabled it some days ago and forgot about it. When I set it, I 
(wrongly) thought that, since I have CONFIG_WERROR set to off, it wouldn't 
have failed the builds. I was just expecting error messages, my fault :(

What led me to figure out this explanation are the messages I got. If you 
noticed, they were all about "case label does not reduce to an integer 
constant".

Well, now I have some more stuff to fix in mainline for my spare time :)

Thanks again,

Fabio




      parent reply	other threads:[~2022-04-01 14:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  9:35 Compilation errors Fabio M. De Francesco
2022-04-01 10:13 ` Stefano Brivio
2022-04-01 12:01   ` Fabio M. De Francesco
2022-04-01 12:57     ` Stefano Brivio
2022-04-01 13:07       ` Fabio M. De Francesco
2022-04-01 16:09         ` Alison Schofield
2022-04-01 17:58           ` Fabio M. De Francesco
2022-04-01 14:39       ` Fabio M. De Francesco [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=6296770.K2JlShyGXD@leap \
    --to=fmdefrancesco@gmail.com \
    --cc=outreachy@lists.linux.dev \
    --cc=sbrivio@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