Re: [webkit-dev] RFC: stop using std::chrono, go back to using doubles for time

2016-05-23 Thread Filip Pizło
You guys are making a convincing case for Seconds/WallTime/MonotonicTime! -Filip > On May 22, 2016, at 11:19 PM, Ryosuke Niwa wrote: > > I'm with Brady here. In WebCore, there are enough DOM and network > APIs that mix wall time and monotonically increasing time (e.g. there

Re: [webkit-dev] RFC: stop using std::chrono, go back to using doubles for time

2016-05-23 Thread Filip Pizło
-Filip > On May 23, 2016, at 12:12 AM, Michal Debski wrote: > > Please this example: http://ideone.com/c640Xd > I'm not going to write "WTF::now()" every time I want the time. That's awful! One of the problems with chrono is the use of awkward templates throughout

Re: [webkit-dev] Build slave for JSCOnly Linux MIPS

2016-04-19 Thread Filip Pizło
> On Apr 19, 2016, at 5:50 AM, Carlos Alberto Lopez Perez > wrote: > >> On 18/04/16 21:50, Filip Pizlo wrote: >> I don't want a buildbot for MIPS. It's not a relevant architecture >> anymore. I don't think that JSC developers should have to expend >> effort towards keeping

Re: [webkit-dev] Build slave for JSCOnly Linux MIPS [WARNING - NOT VIRUS SCANNED]

2016-04-19 Thread Filip Pizło
I think that this is probably OK for the purposes of not creating obligations but I don't see it as a viable strategy for making WebKit work of MIPS. For example, you guys haven't even shown that JSC can pass all WebKit tests on MIPS. You haven't shown that the MIPS JIT produces a speed up

Re: [webkit-dev] Thought about Nix JavaScriptCore port

2016-02-10 Thread Filip Pizło
> On Feb 10, 2016, at 9:14 AM, Konstantin Tokarev <annu...@yandex.ru> wrote: > > > > 10.02.2016, 20:10, "Filip Pizło" <fpi...@apple.com>: >>> On Feb 10, 2016, at 1:40 AM, Konstantin Tokarev <annu...@yandex.ru> wrote: >>> >>&

Re: [webkit-dev] Thought about Nix JavaScriptCore port

2016-02-10 Thread Filip Pizło
> On Feb 10, 2016, at 1:40 AM, Konstantin Tokarev wrote: > > > > 10.02.2016, 05:41, "Eric Wing" : >>> On 2/7/16, Konstantin Tokarev wrote: >>> Please try updated version of my branch, it now does not use LLVM unless >>> you >>>

Re: [webkit-dev] Some text about the B3 compiler

2016-01-30 Thread Filip Pizło
http://trac.webkit.org/changeset/195841 >> >> I filed this bug about improving its style: >> https://bugs.webkit.org/show_bug.cgi?id=153674 >> >> -Filip >> >> >>> >>> -Filip >>> >>> >>>> On Jan 29, 2016, at 10

Re: [webkit-dev] Some text about the B3 compiler

2016-01-30 Thread Filip Pizło
> On Jan 30, 2016, at 3:16 PM, Michael Catanzaro <mcatanz...@igalia.com> wrote: > >> On Sat, 2016-01-30 at 14:13 -0800, Filip Pizło wrote: >> That's so awesome! I can't wait to see it enabled on Linux! >> >> The gcc-clang differences suggest that we will

Re: [webkit-dev] Some text about the B3 compiler

2016-01-29 Thread Filip Pizło
Context: https://trac.webkit.org/wiki/b3Discussion2015 I plan to write more on this topic soon. -Filip > On Jan 28, 2016, at 11:12 PM, Stéphane Letz wrote: > > Maybe a stupid question, but what is a the rationale for this new backend? (I > was thinking LLVM JIT was used

Re: [webkit-dev] Some text about the B3 compiler

2016-01-29 Thread Filip Pizło
lip >> >> >>> On Jan 28, 2016, at 4:39 PM, Saam barati <sbar...@apple.com> wrote: >>> >>> Yeah. That’d be the easiest way to keep it up IMO. >>> >>> Saam >>> >>>> On Jan 28, 2016, at 4:37 PM, Filip Pizło

Re: [webkit-dev] Some text about the B3 compiler

2016-01-29 Thread Filip Pizło
rojects/markdown/syntax >> For a refresher on the syntax. >> >> Tim, could you create a page that loads the markdown file? >> >> Thanks, >> Saam >> >>> On Jan 29, 2016, at 12:06 AM, Filip Pizło <fpi...@apple.com> wrote: >>>

Re: [webkit-dev] Some text about the B3 compiler

2016-01-28 Thread Filip Pizło
+1 Do you think we should move the documentation to a file in svn so that it can be reviewed as part of patch review? -Filip > On Jan 28, 2016, at 4:32 PM, Saam barati wrote: > > This is great. Thanks Fil. > > I propose that we do all that we can to keep this updated. > I

Re: [webkit-dev] Stack Alignment error in LLINT

2015-07-27 Thread Filip Pizło
We generally assume that calls into JavaScriptCore are made on an aligned stack. So, to my knowledge, our code does not usually do dynamic stack realignment. You should check the vmEntryToJavascript thunk - which gets called when you make a call into JS from native code - to see if it does