The problem was in different representations of double variables depending on
platform/compiler/compile options. In some cases double variables are represented by
64 bits (while in memory), or by 80 bits (while in FPU register). As a result equal
values are not considered "==". As many sources point out,  doubles should not be
compared by '==' for this reason. This fix subtracts the scaled minimal double
value X such that 1 + X != 1, to ensure that the inequality holds in any case.

into serg.mylan:/usr/home/serg/Abk/mysql-5.0

into mysql.com:/home/mysqldev/tulin/mysql-5.0

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

into mysql.com:/home/my/mysql-5.0

into poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

  Fix crash reported by Pekka Nousiainen if skip-innodb: do not try to release InnoDB's temporary latches if InnoDB has not been inited

into deer.(none):/home/hf/work/mysql-5.0.clean

into mysql.com:/home/mysqldev/tulin/mysql-5.0

into mysql.com:/home/my/mysql-5.0

into serg.mylan:/usr/home/serg/Abk/mysql-5.0

into deer.(none):/home/hf/work/mysql-5.0.clean

into mysql.com:/home/mysqldev/tulin/mysql-5.0

into mysql.com:/home/pem/work/mysql-5.0

(Which btw also fixed BUG#7295: Server crash when executing stored procedure,
 I just forgot to include that before.)

into mysql.com:/usr/home/ram/work/5.0

into mysql.com:/usr/home/ram/work/5.0

into mysql.com:/home/my/mysql-5.0

Portability fixes and cleanups
Fixed setting of 'res' in mysql_execute_command()

into mysql.com:/home/mysqldev/tulin/mysql-5.0

"create table ta(a bit...) engine=innodb" moved to innodb.test

into mysql.com:/home/mysqldev/tulin/mysql-5.0

into serg.mylan:/usr/home/serg/Abk/mysql-5.0

into mysql.com:/home/mysqldev/tulin/mysql-5.0

into mysql.com:/home/mysqldev/tulin/mysql-5.0

into mysql.com:/home/jonas/src/mysql-5.0