| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Update qscriptvalueiterator test to expect length property when
iterating arrays and strings.
- Use EvalExecutable::create() instead of EvalExecutable constructor.
The constructor is private.
- Reimplement getOwnPropertyDescriptor() in all custom script objects.
- Remove all reimplementations of getPropertyAttributes().
It doesn't exist in trunk anymore (getOwnPropertyDescriptor() is used
instead).
- Remove checkDontDelete argument from deleteProperty() reimplementations.
The purpose of this argument was to support deleting properties
with attribute Undeletable from C++. But it was quite an invasive
patch to JavaScriptCore, and it doesn't seem worth it. If this feature
is really crucial it should be re-done upstream.
One of the tests needed to be updated so it's not sensitive to the
C++ undeletability.
- Adapt getOwnPropertyNames() reimplementations to signature change.
- Add missing QScriptObject structure flags, otherwise we don't get all virtual calls.
- Remove our patch for reporting column numbers in the debugger callbacks.
It was just too intrusive. As with the checkDontDelete issue, this should
be redone upstream if it's really important. In 4.7, QScriptEngineAgent
will always report a column number of 1.
Other compilation fixes:
- InternalFunction::name() takes an ExecState* argument, not GlobalData*
- ScopeChain::globalObject is no longer a function but a member variable
- ScopeChainNode constructor takes a GlobalObject argument
- Heap::collect() is called collectAllGarbage()
- JSValue::strictEqual() takes an ExecState* argument
- Debugger::exception() takes a bool hasHandler argument
- Debugger no longer reports column number (we decided to drop that patch from JSC)
- UString doesn't have operator+=(char*)
- Update the autotests to reflect the columnNumber=1 change.
- Add helper class to avoid crashing inside JSC.
Ever since r52856 in WebKit trunk, this is needed. There are probably a lot of
other public API functions that need this guard as well, but I'll add them as they
are discovered.
- Update mkdist-javascriptcore tag, exclude a few more files.
- Set ENABLE_JSC_MULTIPLE_THREADS=0 define on Mac due to r52355 in trunk.
Reviewed-by: Simon Hausmann
|
|
|
|
| |
Reviewed-by: Kent Hansen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Usefull if we have 'native' properties with setter in a prototype
This happen if you use a QObject wrapper as a prototype.
Use getPropertyDescriptor that look up the prototype in order to
know if we have a setter.
Note that we cannot relly on PropertDescriptor::isAccessorDescriptor
as the Getter or Setter attributes are not necesserly updated correctly
when updating properties. (See the workaround QScriptValuePrivate::propertyFlags,
and tst_QScriptValue::getSetProperty with object7)
Task-number: QTBUG-5749 (also need the previous patch)
Reviewed-by: Kent Hansen
|
|\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
4.6-integration
* '4.6' of scm.dev.nokia.troll.no:qt/oslo-staging-2: (42 commits)
QVariant documentation: there is no function QVariant::isEmpty()
Added caching of vectorpaths to the GL paint engine.
Extended tst_QListView::indexAt to test viewport bounds.
Fix QFontCombobox autotest on X11
In QListViews, items were being hovered even when mouse was on the scrollbars
Fix crash in qt3support QPixmap constructor
Fix tst_qsharedmemory on Unix
Doc: Fixed up a known issue.
Only call updateFont if the font have changed.
Add some notes about known issues for win32-icc
Fixed square root of negative number in drawTextItem().
Fixed the GL2 engine stroker to handle Qt::SvgMiterJoin.
Do not fill the disabled background of item.
X11: Avoid loading all fonts in system for text with line breaks
Do not recoginze templated types or pointers as flags.
Compile webkit for win32-icc
Fix tst_qspinbox compilation with winscw.
compile fix for autotest
compile fix for autotest
state wasn't being correctly reloaded on mac with unified toolbar
...
|
| |
| |
| |
| | |
Reviewed-by: Kent Hansen
|
|/
|
|
|
|
|
|
|
|
| |
Import fix for https://bugs.webkit.org/show_bug.cgi?id=30730
The fix was already applied for src/3rdparty/webkit but not
for src/3rdparty/javascriptcore.
Task-number: QTBUG-6311
Reviewed-by: Simon Hausmann
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Symbols declared as extern "C" will always be exported even when using
-fvisibility=hidden (see gcc man-page).
Instead of exporting we surround the extern declaration with a pragma
push and pop to change the default visibility.
In addition the use of HIDE_SYMBOL was missing in the "arm traditional"
branch for declaring the trampoline functions in JITStubs.cpp
Task-number: QTBUG-5513
Reviewed-by: Kent Hansen
|
|
|
|
|
|
| |
This reverts commit baab5f7e77c1216ede839766c97abef1a708b365.
Reviewed-by: Paul
|
|\ |
|
| |
| |
| |
| | |
Reviewed-By: Jocelyn Turcotte
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
configure.exe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The file was erroneously imported from WebKit trunk.
It is not used when building QtScript, and the only practical
effect it has is to cause configure to spit out a warning.
Reviewed-by: Simon Hausmann
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 333bd2e761af8aaf6efd3d66eb028af046c4dfc2.
The change broke compilation of QWS, since QtGui depends on glib,
but doesn't link with it directly. This needs to be fixed properly,
but not just before the release.
Reviewed-by: Harald Fernengel
|
|\ \
| |/ |
|
| |\
| | |
| | |
| | |
| | | |
Conflicts:
dist/changes-4.6.0
|
| | |
| | |
| | |
| | |
| | | |
Task-number: QTBUG-3368
Reviewed-by: Thiago Macieira
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
Never use "linux-g++*" to check for linux-g++, since this will break embedded
builds which use linux-arm-g++ and friends. Use 'linux*-g++*' to check for any
g++ on linux mkspec.
Reviewed-by: Simon Hausmann
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
JavaScriptCore checks the Mac OS version when building, and uses
symbols only defined in i e.g.snow leopard when building on snow
leopard.
This means that if you build Qt on snow leopard and later move
it to leopard, applications will crash looking for a missing
symbol (pthread_setname_np in particular).
In Qt, we garuantee that you can run your applications on 10.4 and up
for Carbon, and 10.5 and up for Cocoa. So using compile time checks
this way is not a proper soulution.
Result: In Qt, never use symbols not defined on all supported OS
versions, or at least implement run-time checks.
Rev-By: Simon Hausmann
Rev-By: Tor Arne
Rev-By: MortenS
|
|/
|
|
|
|
|
|
| |
Again, we have fun with the C time functions on Windows CE.
On Windows CE 5: the functions are declared but not defined.
On Windows CE 6: the functions are neither declared nor defined.
Reviewed-by: Simon Hausmann
|
|
|
|
|
|
| |
"../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp", line 860: error #2101: "size" has already been declared in the current scope
"../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp", line 1560: error #2101: "span" has already been declared in the current scope
"../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp", line 1807: error #2101: "s" has already been declared in the current scope
|
|
|
|
|
|
| |
"../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp", line 2927: error #2101: "h" has already been declared in the current scope
for (TCMalloc_ThreadCache* h = thread_heaps; h != NULL; h = h->next_) {
^
|
|
|
|
| |
Reviewed-by:Simon Hausmann <simon.hausmann@nokia.com>
|
|
|
|
| |
"Error: "static WTF::TCMalloc_PageHeap::runScavengerThread(void*)" is expected to return a value."
|
|
|
|
| |
jsc-for-qtscript-4.6-staging-06102009 ( 32d226eb14d44f80e9ec96d4ca2c595181eeeca3 )
|
|
|
|
| |
jsc-for-qtscript-4.6-staging-06102009 ( fc2005c87bbbb743eba96041210902fec821a1af )
|
|
|
|
| |
jsc-for-qtscript-4.6-staging-05102009 ( ed678069ebd06579a26b4fb8cc944f06d6b0d55c )
|
|
|
|
|
|
| |
jsc-for-qtscript-4.6-staging-05102009 ( 38c2b17366f24220d9ae0456a7cfe2ac78a9f91c )
Adapt src/script to src/3rdparty/javascriptcore changes
|
|
|
|
|
|
|
|
|
| |
Also add configure test to see if arm toolchain can compile
JavaScript JIT
Task-number:QTBUG-4632
Reviewed-by:Simon Hausmann <simon.hausmann@nokia.com>,
Marius Storm-Olsen <marius.storm-olsen@nokia.com>
|
|
|
|
| |
jsc-for-qtscript-4.6-staging-01102009 ( 79e88e90aab6674098b6d73b1b41998117164499 )
|
|
|
|
|
|
|
|
|
|
|
| |
Cherry-picked-by: Simon Hausmann
http://trac.webkit.org/changeset/48928
This is not a perfect fix, it requires more fine tuning.
But this makes it possible again to debug in the emulator,
which is more important in order to be able to fix other
run-time issues.
|
|
|
|
|
|
|
|
| |
The compiler complained about ambiguity in calls to make_pair because
there is also a "using std::make_pair" in the WTF namespace
(wtf/HashTraits.h).
Reviewed-by: Simon Hausmann
|
|
|
|
| |
jsc-for-qtscript-4.6-staging-30092009 ( e8f42cf0203bee0ba89a05e0e773d713782129b4 )
|
|
|
|
|
|
|
|
|
| |
It is possible to call QScriptEngine::pushContext before we start any evaluation.
We need to change JSC so it doesn't always start at the beginning of the stack.
Also fix QScriptContext::pushContext not to waste space between callframes.
Reviewed-by: Kent Hansen
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove __clear_cache which is an internal function of GCC
https://bugs.webkit.org/show_bug.cgi?id=28886
Patch by Gabor Loki <loki@inf.u-szeged.hu> on 2009-09-28
Reviewed by Simon Hausmann.
Although __clear_cache is exported from GCC, this is an internal
function. GCC makes no promises about it.
* jit/ExecutableAllocator.h:
(JSC::ExecutableAllocator::cacheFlush):
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@48824 268f45cc-cd09-0410-ab3c-d52691b4dbfc
|
|
|
|
|
|
|
|
|
|
| |
I was assuming that the default return value register was always set
to 0 for native calls. But this is not the case. So we must ensure this.
Also be consistend in the way the stackframe grow and shrink. This expose
another bug in the way the call frame is created in JSC
Reviewed-by: Kent Hansen
|
|
|
|
| |
jsc-for-qtscript-4.6-staging-28092009 ( b98dec961e9389ddd5e10d7c4086de9a297cb984 )
|
|
|
|
| |
Reviewed-by: Simon Hausmann
|
|
|
|
| |
Reviewed-by: Simon Hausmann
|
|
|
|
| |
Reviewed-by: Simon Hausmann
|
|
|
|
|
|
|
|
|
|
| |
The problem is that the interpreter did not check for exception while
running the "while(true){}" loop, as it deduced that none of the generated
opcode would possibly generate an exception.
The solution is to force a check right after we come from a timeout.
Reviewed-by: Kent Hansen
|
|
|
|
|
|
|
| |
This add a hook inside JSC to be able to implement our own comparison function
when comparing objects.
Reviewed-by: Kent Hansen
|
|
|
|
|
|
| |
configure
Reviewed-by: Simon Hausmann
|
|
QtWebKit uses.
This is needed to decouple QtScript from QtWebKit, as discussed in the
WebKit team.
Reviewed-by: Kent Hansen
|