Dimitry Sibiryakov <s...@ibphoenix.com> писал(а) в своём письме Tue, 25 Jun
2019 22:54:57 +0300:
21.06.2019 15:53, Alex Peshkoff via Firebird-devel wrote:
I.e. I suggest to replace high precision numeric's implementation using
decfloat with native 128-bit integer when possible and ttmath in other
cases. That will make it possible to use 128-bit integers in all cases
when 64 is not enough without serious performance penalty. Comments?
Just to be sure: do you suggest to remove DECFLOAT implementation
which you have been working on for several years?
BTW, does this piece of code really worth optimization? For example,
I know a method for multiplication overflow prediction which is much
faster than current one, but will it bring any noticeable change to
Fiebird performance as a whole?
Dmitry, the DECFLOAT type is defined in the SQL:2016 standard as a
separate type, so you don’t need to remove anything. We are talking only
about the implementation of NUMERIC (19+, x) and DECIMAL (19+, x)
--
Simonov Denis
Firebird-Devel mailing list, web interface at
https://lists.sourceforge.net/lists/listinfo/firebird-devel
