From: Meelis Roos <mroos@linux.ee>
To: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Should I report UBSAN Undefined behaviour warnings?
Date: Tue, 16 Feb 2016 16:05:21 +0200 (EET) [thread overview]
Message-ID: <alpine.LRH.2.20.1602161603310.24671@math.ut.ee> (raw)
I have turned on UBSAN on multiple test machines to see what it's like
and it gives me multiple kinds of warnings from multiple places in code.
What's the status of UBSAN - should I report them or not yet?
--
Meelis Roos (mroos@linux.ee)
reply other threads:[~2016-02-16 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.LRH.2.20.1602161603310.24671@math.ut.ee \
--to=mroos@linux.ee \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®