Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Andrey Konovalov <andrey.konovalov@linaro.org>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-browser] [PATCH] chromium: fix null pointer dereference in V8 with gcc-6
Date: Tue, 11 Apr 2017 22:42:03 +0300	[thread overview]
Message-ID: <58ED318B.6090702@linaro.org> (raw)
In-Reply-To: <CAJ86T=WWRhgpONcfvJRGSyARzFS4pkmWrnx2BenOZKasv9Y7MQ@mail.gmail.com>

On 04/11/2017 09:51 PM, Andre McCurdy wrote:
> On Tue, Apr 11, 2017 at 6:02 AM, Andrey Konovalov
> <andrey.konovalov@linaro.org> wrote:
>> On 04/11/2017 03:40 AM, Andre McCurdy wrote:
>>>
>>> On Fri, Apr 7, 2017 at 11:40 AM, Andrey Konovalov
>>> <andrey.konovalov@linaro.org> wrote:
<snip>
>>>> -GYP_DEFINES += "${ARMFPABI}
>>>> release_extra_cflags='-Wno-error=unused-local-typedefs' sysroot=''"
>>>> +GYP_DEFINES += " ${ARMFPABI}
>>>> release_extra_cflags='-Wno-error=unused-local-typedefs' sysroot='' \
>>>> +       ${@bb.utils.contains("AVAILTUNES", "mips", "",
>>>> "release_extra_cflags='-fno-delete-null-pointer-checks'", d)}"
>>>
>>>
>>> What's the significance of skipping the workaround if AVAILTUNES
>>> contains "mips" ?
>>
>>
>> This change (to add '-fno-delete-null-pointer-checks' to gcc flags) was
>> initially merged into chromium directly,
>> but soon reverted as it broke mips somehow:
>> https://bugs.chromium.org/p/v8/issues/detail?id=3782#c10
>
> OK, thanks. Note that building for MIPS isn't currently supported at
> all according to the COMPATIBLE_MACHINE definitions at the top of the
> recipe.

Indeed.
So my check for "mips" in AVAILTUNES is a NOP until someone enables building for MIPS.
Thanks for pointing that out!


      reply	other threads:[~2017-04-11 19:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-07 18:40 [meta-browser] [PATCH] chromium: fix null pointer dereference in V8 with gcc-6 Andrey Konovalov
2017-04-07 19:16 ` Andrey Konovalov
2017-04-11  0:40 ` Andre McCurdy
2017-04-11 13:02   ` Andrey Konovalov
2017-04-11 18:51     ` Andre McCurdy
2017-04-11 19:42       ` Andrey Konovalov [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=58ED318B.6090702@linaro.org \
    --to=andrey.konovalov@linaro.org \
    --cc=armccurdy@gmail.com \
    --cc=openembedded-devel@lists.openembedded.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