b5a19c1036
separate JS stack.
In exception handling, we need to be able to compare addresses into
the JavaScript portion of the stack with the address of a C++ handler
on the stack. Since the stacks are separate on the simulator, we need
a JavaScript stack address corresponding to a C++ try catch handler in
order to perform valid address comparisons.
On the simulator, we now link the C++ try catch handlers indirectly
through the JS stack and use the JS stack indirection address for
comparisons.
JS C++
handler
[C++ address] <------ next_
\
\
\----> handler
[C++ address] <------ next_
On actual hardware the C++ try catch handlers continue to be directly
linked.
BUG=http://code.google.com/p/v8/issues/detail?id=271
Review URL: http://codereview.chromium.org/360004
git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3228 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
68 lines
2.8 KiB
Plaintext
68 lines
2.8 KiB
Plaintext
# Copyright 2008 the V8 project authors. All rights reserved.
|
|
# Redistribution and use in source and binary forms, with or without
|
|
# modification, are permitted provided that the following conditions are
|
|
# met:
|
|
#
|
|
# * Redistributions of source code must retain the above copyright
|
|
# notice, this list of conditions and the following disclaimer.
|
|
# * Redistributions in binary form must reproduce the above
|
|
# copyright notice, this list of conditions and the following
|
|
# disclaimer in the documentation and/or other materials provided
|
|
# with the distribution.
|
|
# * Neither the name of Google Inc. nor the names of its
|
|
# contributors may be used to endorse or promote products derived
|
|
# from this software without specific prior written permission.
|
|
#
|
|
# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
|
|
# "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
|
|
# LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
|
|
# A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
|
|
# OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
|
|
# SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
|
|
# LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
|
|
# DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
|
|
# THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
|
|
# (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
|
|
# OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|
|
|
prefix cctest
|
|
|
|
# BUG(281): This test fails on some Linuxes.
|
|
test-debug/DebuggerAgent: PASS, (PASS || FAIL) if $system == linux
|
|
|
|
# BUG(382): Weird test. Can't guarantee that it never times out.
|
|
test-api/ApplyInterruption: PASS || TIMEOUT
|
|
|
|
# This is about to go away anyway since new snapshot code is on the way.
|
|
test-serialize/Deserialize: FAIL
|
|
test-serialize/DeserializeAndRunScript: FAIL
|
|
test-serialize/DeserializeNatives: FAIL
|
|
test-serialize/DeserializeExtensions: FAIL
|
|
|
|
# These tests always fail. They are here to test test.py. If
|
|
# they don't fail then test.py has failed.
|
|
test-serialize/TestThatAlwaysFails: FAIL
|
|
test-serialize/DependentTestThatAlwaysFails: FAIL
|
|
|
|
|
|
[ $arch == arm ]
|
|
|
|
# New serialization doesn't work on ARM yet.
|
|
test-serialize/Deserialize2: SKIP
|
|
test-serialize/DeserializeAndRunScript2: SKIP
|
|
|
|
# BUG(113): Test seems flaky on ARM.
|
|
test-spaces/LargeObjectSpace: PASS || FAIL
|
|
|
|
# BUG(240): Test seems flaky on ARM.
|
|
test-api/RegExpInterruption: SKIP
|
|
|
|
# We cannot assume that we can throw OutOfMemory exceptions in all situations.
|
|
# Apparently our ARM box is in such a state. Skip the test as it also runs for
|
|
# a long time.
|
|
test-api/OutOfMemory: SKIP
|
|
test-api/OutOfMemoryNested: SKIP
|
|
|
|
# BUG(355): Test crashes on ARM.
|
|
test-log/ProfLazyMode: SKIP
|