Re: [Development] RFC: more liberal 'auto' rules?

2015-12-24 Thread Kevin Kofler
Matthew Woehlke wrote: > auto result = QString{a + b}; IMHO, that's just a complicated and ugly way to write: QString result = a + b; There is no way the variable can be uninitialized if you initialize it right there in the declaration. Kevin Kofler

Re: [Development] V4 porting

2015-12-24 Thread Hausmann Simon
Hi, Registers that are native to the processor are saved on the regular stack. Simon From: Dmitriy - Sent: Thursday, December 24, 2015 14:11 To: Hausmann Simon Cc: development@qt-project.org Subject: Re: [Development] V4 porting One more question: qt-5.5.1/qtdeclarative/src/qml/jit/qv4assemb

Re: [Development] V4 porting

2015-12-24 Thread Hausmann Simon
Hi, The method parse implies a transformation from source code to a form that we can interpret, so technically the name of the method isn't quite accurate. Nevertheless it does what you can see in the implementation, which includes parsing into a syntax tree structure, transformation into an in

Re: [Development] wec2013 build fails with qt 5.6 beta in dbus.

2015-12-24 Thread Thiago Macieira
On Tuesday 22 December 2015 12:01:41 Thiago Macieira wrote: > On Monday 21 December 2015 23:43:15 Gunnar Roth wrote: > > Hi Simon. > > The conflict happens in a dozen files in qtbase/src/dbus/ and > > qttools/src/qdbus. > > I can add the #undef to qdbusmessage.h. It has a function called > interfa

Re: [Development] V4 porting

2015-12-24 Thread Dmitriy -
One more question: qt-5.5.1/qtdeclarative/src/qml/jit/qv4assembler_p.h // V4 uses two stacks: one stack with QV4::Value items, which is checked by the garbage // collector, and one stack used by the native C/C++/ABI code. This C++ stack is not scanned // by the garbage collector, s

Re: [Development] V4 porting

2015-12-24 Thread Dmitriy -
Thank. I want to port JIT. Where should I start? You have any roadmap for this? Now I'm using qmljs tool for testing purpose. I has seen in qt-5.5.1/qtdeclarative/src/qml/jsruntime/qv4script.cpp: Script::parse(): ... RuntimeCodegen cg(v4, strictMode); cg.generateFromProgram(sourceFile, sourceC

Re: [Development] V4 porting

2015-12-24 Thread Hausmann Simon
Hi, Moth is the portable interpreter that will be used instead of the just-in-time compiler if your platform doesn't support it. It should be chosen automatically for you according to the #ifdefs in qv4global_p.h. So if you have qtbase compiling, then qml should also work. If you want things t

[Development] V4 porting

2015-12-24 Thread Dmitriy -
Hi! I want to port v4 engine to the new platform. The platform is Linux OS and new processor. The processor looks like intel itanium. It is VLIW and EPIC. I have a c++/c compilers for the new architecture. I want to design qt quic qml application for the new platform. As a can see in code, I need