search for: webkits

...philipreames.com> wrote: > > After reading https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/ <https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/>., I jotted down a couple of thoughts of my own here: http://www.philipreames.com/Blog/2016/02/15/quick-thoughts-on-webkits-b3/ <http://www.philipreames.com/Blog/2016/02/15/quick-thoughts-on-webkits-b3/> Thanks for sharing. I think it’s worth noting that what you are doing would be considered 5th tier for WebKit, since you already had a decent optimizing backend without LLVM. You also have more room for backgroun...

----- Original Message ----- > > On Fri, Oct 18, 2013 at 1:39 AM, Andrew Trick < atrick at apple.com > > wrote: > > > > The initial documentation and patches name these intrinsics in a > "webkit" namespace. This clarifies their current purpose and conveys > that they haven't been standardized for other JITs yet. If someone on > the on the dev

On Oct 18, 2013, at 10:09 AM, Hal Finkel <hfinkel at anl.gov> wrote: > ----- Original Message ----- >> >> On Fri, Oct 18, 2013 at 1:39 AM, Andrew Trick < atrick at apple.com > >> wrote: >> >> >> >> The initial documentation and patches name these intrinsics in a >> "webkit" namespace. This clarifies their current purpose

> On Feb 9, 2016, at 9:55 AM, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > JavaScriptCore's [FTL JIT](https://trac.webkit.org/wiki/FTLJIT <https://trac.webkit.org/wiki/FTLJIT>) is moving away > > from using LLVM as its backend, towards [B3 (Bare Bones > > Backend)](https://webkit.org/docs/b3/

On Oct 18, 2013, at 11:08 AM, Andrew Trick <atrick at apple.com> wrote: >> >> I recommend, this being the case, to replace 'webkit' with 'experimental'. Having webkit in the name implies some dependence on webkit, and there is none. Plus, this functionality will be used by outside projects as soon as it lands in trunk, and I suspect that having webkit in the

...;> wrote: >>> >>> After reading https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/ <https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/>., I jotted down a couple of thoughts of my own here:http://www.philipreames.com/Blog/2016/02/15/quick-thoughts-on-webkits-b3/ <http://www.philipreames.com/Blog/2016/02/15/quick-thoughts-on-webkits-b3/> >> >> Thanks for sharing. I think it’s worth noting that what you are doing would be considered 5th tier for WebKit, since you already had a decent optimizing backend without LLVM. > So, serious, b...

On Fri, Oct 18, 2013 at 1:39 AM, Andrew Trick <atrick at apple.com> wrote: > > The initial documentation and patches name these intrinsics in a > "webkit" namespace. This clarifies their current purpose and conveys > that they haven't been standardized for other JITs yet. If someone on > the on the dev list says "yes we want to use these too, just the way

This is a proposal for adding Stackmaps and Patchpoints to LLVM. The first client of these features is the JavaScript compiler within the open source WebKit project. A Stackmap is a record of variable locations (registers and stack offsets) at a particular instruction address. A Patchpoint is an instruction address at which space is reserved for patching a new instruction sequence at runtime.

Hi @ll, I would like to obsolete and completely remove the WebKit Calling Convention. The CC was originally added for FTL and there are no other users I am aware off. Since WebKit moved away from LLVM a while ago I don’t see the need to keep the dead code around anymore. Please let me know if anyone happens to use this calling convention or has any objection with removing it. Thanks Cheers,

On Oct 18, 2013, at 2:59 PM, Evan Cheng <evan.cheng at apple.com> wrote: > > On Oct 18, 2013, at 12:39 PM, Chris Lattner <clattner at apple.com> wrote: > >> On Oct 18, 2013, at 11:08 AM, Andrew Trick <atrick at apple.com> wrote: >> >>>> >>>> I recommend, this being the case, to replace 'webkit' with 'experimental'.

Hello is the webkit with CentOS 7.4 compiled with ENABLE_MEDIASOURCE ? When I call the set_media_source function with TRUE and then ask get_media_source function for the value it returns TRUE. I presume it would no return TRUE if its not enabled. However, my webpage with a video tag using webkit is not finding the MediaSource. Thanks, Jerry

On Oct 18, 2013, at 12:39 PM, Chris Lattner <clattner at apple.com> wrote: > On Oct 18, 2013, at 11:08 AM, Andrew Trick <atrick at apple.com> wrote: > >>> >>> I recommend, this being the case, to replace 'webkit' with 'experimental'. Having webkit in the name implies some dependence on webkit, and there is none. Plus, this functionality will

> (7) Make the C API truly great. > > I think it’s harmful to LLVM in the long run if external embedders use the C++ API. I think that one way of ensuring that they don’t have an excuse to do it is to flesh out some things: > > - Add more tests of the C API to ensure that people don’t break it accidentally and to give more gravitas to the C API backwards compatibility claims. >

I am trying to compile webkitgtk I downloaded the webkit source, extracted CMake Error at Source/cmake/OptionsGTK.cmake:12 (message): GCC 4.9.0 is required to build WebKitGTK+, use a newer GCC version or clang I downloaded 2.14.7 - just like CentOS 7.4 has, how can I be getting a GCC error ? My goal is to get the MediaSource package in webkit working. It seems to not be enabled. Is there a

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META content="text/html; charset=utf-8" http-equiv=Content-Type> <META name=GENERATOR content="MSHTML 8.00.7601.18667"></HEAD> <BODY> <DIV><BR></DIV> <DIV> <DIV> <DIV> <TABLE border=0 cellSpacing=0

On Tue, Aug 5, 2014 at 2:49 PM, Filip Pizlo <fpizlo at apple.com> wrote: > >> On Aug 5, 2014, at 1:46 PM, Eric Christopher <echristo at gmail.com> wrote: >> >>> (7) Make the C API truly great. >>> >>> I think it’s harmful to LLVM in the long run if external embedders use the C++ API. I think that one way of ensuring that they don’t have an

LLVM Weekly - #110, Feb 8th 2016 ================================ If you prefer, you can read a HTML version of this email at <http://llvmweekly.org/issue/110>. Welcome to the one hundred and tenth issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by [Alex

On 7 June 2014 00:14, Filip Pizlo <fpizlo at apple.com> wrote: > The only setback is to ensure that we synchronize the renaming with WebKit. > > The WebKit->LLVM interface currently avoids revision-lock; you can take any > recent revision of either and build a working browser engine. This is mostly > true even when we change the stack map format because of versioning in the

Any thoughts on the feasibility of this? One thing you can''t test in Rails is the result of Ajax requests in the context of the source document. The best you can do (as far as I''m aware) is test that the Ajax response is correct and hope the page gets updated. I started thinking... WebKit (and more importantly JavaScriptCore) is open source WebKit has a Cocoa wrapper

Hi, I've been following the instructions on how to use the LLVM Gold plugin at http://llvm.org/docs/GoldPlugin.html while building an multiple versions of WebKit. The documentation hasn't been updated since 2010 and hasn't really matched my experiences, so I'd like to ask if I'm doing these steps incorrectly. What I'm trying to do is force all compilation steps to