diogo/yap-6.3
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

indexing code would get confused about size of float/1, db_reference1.

Browse Source 
git-svn-id: https://yap.svn.sf.net/svnroot/yap/trunk@1549 b08c6af1-5177-4d33-ba66-4b1c6b8b522a
This commit is contained in:
vsc
2006-02-22 11:55:36 +00:00
parent 2de3fd9474
commit ea6594491c
2 changed files with 12 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
C/index.c
View File

@@ -11,8 +11,11 @@
* File: index.c *
* comments: Indexing a Prolog predicate *
* *
* Last rev: $Date: 2006-02-19 02:55:46 $,$Author: vsc $ *
* Last rev: $Date: 2006-02-22 11:55:36 $,$Author: vsc $ *
* $Log: not supported by cvs2svn $
* Revision 1.152 2006/02/19 02:55:46 vsc
* disable indexing on bigints
*
* Revision 1.151 2006/01/16 02:57:51 vsc
* fix bug with very large integers
* fix bug where indexing code was looking at code after a cut.
@@ -2649,8 +2652,8 @@ move_next(ClauseDef *clause, UInt regno)
switch (op) {
case _p_db_ref_x:
case _p_float_x:
if (wreg == cl->u.x.x) {
clause->CurrentCode = NEXTOP(cl,x);
if (wreg == cl->u.xF.x) {
clause->CurrentCode = NEXTOP(cl,xF);
}
return;
case _get_list:
@@ -3026,6 +3029,8 @@ valid_instructions(yamop *end, yamop *cl)
switch (op) {
case _p_db_ref_x:
case _p_float_x:
cl = NEXTOP(cl,xF);
break;
case _get_list:
cl = NEXTOP(cl,x);
break;