Bug 179209 - [GTK] error: no member named 'isEnabled' in namespace 'Gigacage' and error: too few arguments to function call, expected 2, have 1 LValue basePtr = m_out.constIntPtr(Gigacage::basePtr(kind));
Summary: [GTK] error: no member named 'isEnabled' in namespace 'Gigacage' and error: t...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P3 Normal
Assignee: Nobody
URL:
Keywords: Gtk
Depends on:
Blocks:
 
Reported: 2017-11-02 16:32 PDT by kkuehl
Modified: 2017-11-03 11:37 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kkuehl 2017-11-02 16:32:04 PDT
In file included from DerivedSources/JavaScriptCore/unified-sources/UnifiedSource61.cpp:4:
../../Source/JavaScriptCore/ftl/FTLLowerDFGToB3.cpp:12232:24: error: no member named 'isEnabled' in namespace 'Gigacage'
        if (!Gigacage::isEnabled(kind))
             ~~~~~~~~~~^
../../Source/JavaScriptCore/ftl/FTLLowerDFGToB3.cpp:12242:66: error: too few arguments to function call, expected 2, have 1
        LValue basePtr = m_out.constIntPtr(Gigacage::basePtr(kind));
                                           ~~~~~~~~~~~~~~~~~     ^
../../Source/WTF/wtf/Gigacage.h:81:1: note: 'basePtr' declared here
ALWAYS_INLINE void*& basePtr(BasePtrs& basePtrs, Kind kind)
^
../../Source/WTF/wtf/Compiler.h:184:23: note: expanded from macro 'ALWAYS_INLINE'
#define ALWAYS_INLINE inline __attribute__((__always_inline__))
                      ^
Comment 1 kkuehl 2017-11-03 10:19:46 PDT
Should have mentioned that this is on git master.
Head of git log is

commit 61cc25446d7f19494af105d96d1d406d75bc7bb5 (HEAD -> master, origin/master, origin/HEAD)
Author: cdumez@apple.com <cdumez@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc>
Date:   Fri Nov 3 16:37:04 2017 +0000
Comment 2 kkuehl 2017-11-03 10:33:13 PDT
git blame shows it broke with this commit.

80e5eb76d
Comment 3 Michael Catanzaro 2017-11-03 11:37:43 PDT
(In reply to kkuehl from comment #2)
> git blame shows it broke with this commit.
> 
> 80e5eb76d

What's the SVN revision number? Look towards the bottom of the commit message.