From: Randy MacLeod <randy.macleod@windriver.com>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2] valgrind: update from 3.13.0 to 3.14.0
Date: Mon, 22 Oct 2018 17:38:17 -0400 [thread overview]
Message-ID: <95316079-8f79-ea9a-161d-aeefe45a97f1@windriver.com> (raw)
In-Reply-To: <CAMKF1srghdS66FHbZv_ikGHLDUqGDK1oxZOC40UnSied=Y2EGw@mail.gmail.com>
On 10/21/18 6:24 PM, Khem Raj wrote:
> On Sun, Oct 21, 2018 at 9:48 PM Randy MacLeod
> <randy.macleod@windriver.com> wrote:
>>
>> On 10/21/18 5:47 AM, Khem Raj wrote:
>>> fails ptest compile on musl/mips
>>> http://errors.yoctoproject.org/Errors/Details/197122/
>>
>> I have a fix that I'll send later tonight or tomorrow morning
>> once I've tested it a bit more. I'll paste it inline below in
>> case anyone wants it now.
>>
>> I did notice that the ptest build of valgrind takes a more than
>> 30 minutes!:
>>
>> 0: valgrind-3.14.0-r0 do_compile_ptest_base - 2306s (pid 21911)
>>
>> It's building:
>> none/tests/mips32/msa_fpu.c
>> which is from a commit [1] that tries to cover
>> all MIPS SIMD architecture instructions. I'll
>> drop that test unless someone objects since it's overkill
>> for a ptest IMO.
>
> I do not use MSA here so it might be ok to to save some time. but I am
> curious how it looks on real h/w
>
I don't have a mips target at hand but I may decide
to dig one up and see if there's any value in the MSA test
at some point. Until then I'll leave the test as is.
Here are the valgrind bugs that I reported :
musl bug:
https://bugs.kde.org/show_bug.cgi?id=400162
assembler bug:
https://bugs.kde.org/show_bug.cgi?id=400164
I have update the oe-core patch status locally
with a link to these bugs IDs and I'll send that
once the:
valgrind: Make local functions static to avoid assembler error
patch is merged.
--
# Randy MacLeod
# Wind River Linux
prev parent reply other threads:[~2018-10-22 21:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-20 5:40 v2: valgrind upgrade to 3.14 Randy MacLeod
2018-10-20 5:40 ` [PATCH v2] valgrind: update from 3.13.0 to 3.14.0 Randy MacLeod
2018-10-21 9:47 ` Khem Raj
2018-10-21 20:48 ` Randy MacLeod
2018-10-21 22:24 ` Khem Raj
2018-10-22 21:38 ` Randy MacLeod [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=95316079-8f79-ea9a-161d-aeefe45a97f1@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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