From: Fam Zheng <famz@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 3/3] build-sys: enable sanitizers by default with --enable-debug
Date: Fri, 9 Feb 2018 10:24:01 +0800 [thread overview]
Message-ID: <20180209022401.GL24289@lemon.usersys.redhat.com> (raw)
In-Reply-To: <CAJ+F1C+TFo96++C61fkp-_GdD43VHj1=zimnFSnEUkx+e=HRZQ@mail.gmail.com>
On Thu, 02/08 20:03, Marc-André Lureau wrote:
> Hi
>
> On Thu, Feb 8, 2018 at 6:46 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
> > On 08/02/2018 17:23, Marc-André Lureau wrote:
> >> The original commit 247724cb302af5d70c8853154b640dfabf2bbb56 was meant
> >> to enable sanitizers by default when --enable-debug, but failed
> >> because of a gcc static linking bug. Try to enable it back now that
> >> there is a stronger check.
> >>
> >> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> >
> > I'm more afraid that there are quite a few reports from sanitizers. I
> > wonder if that makes --enable-debug unusable; as a non-user of
> > --enable-debug I'm a bit wary of pushing this patch.
>
> I understand the concern, but at the same time, people should care
> about fixing those. If they want to keep ignoring them (for bad
> reasons), they can --disable-sanitizers. At least, I would want to
> reach a point where no ASAN regression get introduced in x86 target.
> It would be nice if patchew warn on new ASAN reports for example.
Could you write a docker test for that?
Fam
prev parent reply other threads:[~2018-02-09 2:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 16:23 [Qemu-devel] [PATCH 1/3] build-sys: remove useless extra*flags variables Marc-André Lureau
2018-02-08 16:23 ` [Qemu-devel] [PATCH 2/3] build-sys: check static linking of UBSAN Marc-André Lureau
2018-02-08 17:48 ` Eric Blake
2018-02-08 16:23 ` [Qemu-devel] [PATCH 3/3] build-sys: enable sanitizers by default with --enable-debug Marc-André Lureau
2018-02-08 17:46 ` Paolo Bonzini
2018-02-08 19:03 ` Marc-André Lureau
2018-02-09 2:24 ` Fam Zheng [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=20180209022401.GL24289@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).