From: Thomas Monjalon <thomas@monjalon.net>
To: Harman Kalra <hkalra@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
John McNamara <john.mcnamara@intel.com>,
Marko Kovacevic <marko.kovacevic@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [EXT] Re: [PATCH] mk: add support for UBSAN
Date: Sat, 16 Nov 2019 09:31:13 +0100 [thread overview]
Message-ID: <5144340.QROL6Lj2PW@xps> (raw)
In-Reply-To: <20191115144549.GA158812@outlook.office365.com>
15/11/2019 15:46, Harman Kalra:
> On Mon, Nov 11, 2019 at 08:07:00AM +0100, Thomas Monjalon wrote:
> > External Email
> >
> > ----------------------------------------------------------------------
> > Hi,
> >
> > Sorry for the very late review.
> > I hope someone else would try it.
> >
> > I tried this:
> > devtools/test-build.sh -v x86_64-native-linux-clang+shared+UBSAN+SANITIZE_ALL
> > and it triggers some link errors:
> > /usr/bin/ld: rte_kvargs.c:(.text+0xc65): undefined reference to `__ubsan_handle_pointer_overflow'
> Hi,
>
> Thanks for trying it out. I came across these errors when compiler
> versions doesn't supports UBSAN
If the support is not available, we should print a clear error message,
not random link errors.
> Can you please with latest clang version if issue still persists.
I am using clang 8.
prev parent reply other threads:[~2019-11-16 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 13:48 [dpdk-dev] [PATCH] mk: add support for UBSAN Harman Kalra
2019-09-13 11:40 ` Harman Kalra
2019-10-09 14:25 ` Harman Kalra
2019-10-28 10:50 ` Harman Kalra
2019-11-11 7:07 ` Thomas Monjalon
2019-11-15 14:46 ` [dpdk-dev] [EXT] " Harman Kalra
2019-11-15 14:54 ` [dpdk-dev] [PATCH v2] " Harman Kalra
2019-11-15 15:34 ` [dpdk-dev] [PATCH v3] " Harman Kalra
2019-11-27 14:23 ` Aaron Conole
2019-11-16 8:31 ` Thomas Monjalon [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=5144340.QROL6Lj2PW@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=hkalra@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.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 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.