This fix addresses a bug of the HPUX C++ compiler, in the way it uses registers.
As result, the last comparison of the variable 'result' failed, and next_prefix()
looped forever.

into mysql.com:/home/timka/mysql/src/5.0-bug-8576

into ua141d10.elisa.omakaista.fi:/home/my/bk/mysql-5.0

into mysql.com:/home/timka/mysql/src/5.0-bug-8576

into gluh.mysql.r18.ru:/home/gluh/MySQL/mysql-5.0

        bug #7215: information_schema: columns are longtext instead of varchar

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 poseidon.ndb.mysql.com:/home/tomas/mysql-5.0

   make sure transporter connections are close early in shutdown

into gluh.mysql.r18.ru:/home/gluh/MySQL/mysql-5.0

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

into mysql.com:/home/jimw/my/mysql-4.1-clean

into mysql.com:/home/jimw/my/mysql-4.1-clean

into mysql.com:/home/psergey/mysql-5.0-bug8397

In Item_cache_decimal::store(item) the call item->val_decimal_result() 
returns NULL if the passed item has an SQL null value. Don't try copying
NULL into Item_cache_decimal::val in this case.

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

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

into mysql.com:/home/psergey/mysql-5.0-build

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

  Take into account that bitmap_is_set() may return any non-zero zero value when the bit is set.

into hundin.mysql.fi:/home/heikki/mysql-5.0

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

  Disable the XA code in InnoDB crash recovery; when Jan and Sergei want to test XA, they should revert this patch