Actions
Bug #2686
closedQT3 test case filter-limits-003 fails with bytecode feature
Status:
Closed
Priority:
Normal
Assignee:
Category:
Byte code generation
Sprint/Milestone:
Start date:
2016-03-24
Due date:
% Done:
100%
Estimated time:
Legacy ID:
Applies to branch:
9.7
Fix Committed on Branch:
9.7
Fixed in Maintenance Release:
Platforms:
Description
The following test case filter-limits-003 fails when the bytecode feature switched on.
the expected results is achieved in the interpreted mode.
Test case:
<test-case name="filter-limits-002">
<description>Test numeric predicates at integer limits</description>
<created by="Christian Gruen" on="2016-02-04"/>
<dependency type="spec" value="XQ10+"/>
<test>'a'[4294967296]</test>
<result>
<assert-empty/>
</result>
</test-case>
Test suite driver setup:
. catalog.xml -o:results/saxon -lang:XQ31 -bytecode:on -s:prod-Predicate -t:filter-limits-003
Actual result:
Assertion assert-empty () failed
*** TEST-FAILURE. Result:
a<=======
Updated by Michael Kay over 8 years ago
- Status changed from New to Resolved
- Assignee set to Michael Kay
- Fix Committed on Branch 9.7 added
I have fixed this particular case by checking the literal value of the filter expression at compile time (before bytecode generation). This won't fix the case where a large subscript value is computed dynamically, however, this is sufficient of an edge case that I don't feel compelled to investigate it until some user reports that they are affected by the problem.
Updated by O'Neil Delpratt over 8 years ago
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in Maintenance Release 9.7.0.5 added
Bug fix applied in the Saxon 9.7.0.5 maintenance release.
Please register to edit this issue
Actions