aboutsummaryrefslogtreecommitdiff
path: root/src/sqliteInt.h
diff options
context:
space:
mode:
authordrh <>2024-10-01 20:29:43 +0000
committerdrh <>2024-10-01 20:29:43 +0000
commite8b2c92240388cad4d41e83a7383b179b7a78acd (patch)
tree4c0ced6fcb8a22a9d9ebffb563d0d48733271ec1 /src/sqliteInt.h
parent7151010919cff7ab5134173f5d22fdf534104c34 (diff)
downloadsqlite-e8b2c92240388cad4d41e83a7383b179b7a78acd.tar.gz
sqlite-e8b2c92240388cad4d41e83a7383b179b7a78acd.zip
Remove all code that makes use of the C-language "long double" datatype.
FossilOrigin-Name: f622b52024c8bec1d241b1dc480fbbd839fc1af50b6220f012812503de2c656e
Diffstat (limited to 'src/sqliteInt.h')
-rw-r--r--src/sqliteInt.h40
1 files changed, 0 insertions, 40 deletions
diff --git a/src/sqliteInt.h b/src/sqliteInt.h
index 5b166d9a3..2b800abd9 100644
--- a/src/sqliteInt.h
+++ b/src/sqliteInt.h
@@ -660,7 +660,6 @@
# define float sqlite_int64
# define fabs(X) ((X)<0?-(X):(X))
# define sqlite3IsOverflow(X) 0
-# define LONGDOUBLE_TYPE sqlite_int64
# ifndef SQLITE_BIG_DBL
# define SQLITE_BIG_DBL (((sqlite3_int64)1)<<50)
# endif
@@ -835,9 +834,6 @@
# define INT8_TYPE signed char
# endif
#endif
-#ifndef LONGDOUBLE_TYPE
-# define LONGDOUBLE_TYPE long double
-#endif
typedef sqlite_int64 i64; /* 8-byte signed integer */
typedef sqlite_uint64 u64; /* 8-byte unsigned integer */
typedef UINT32_TYPE u32; /* 4-byte unsigned integer */
@@ -4249,41 +4245,6 @@ typedef struct {
# define Tuning(X) 0
#endif
-/* By default, SQLite will use long double if the long double type
-** actually provides higher resolution than double. This use or non-use
-** of long double is switchable at run-time by a test-control. Dekker
-** algorithms are used for high-precision floating point when long double
-** is not available.
-**
-** Having the run-time option to enable/disable long double support
-** causes problems for some compiler tool chains. So the following
-** compile-time option is available to permanently enable/disable the use
-** of long double.
-**
-** -DSQLITE_USE_LONG_DOUBLE=0 Omit all use of "long double" from
-** the code. Instead, the Dekker algorithm
-** is always used when high-precision
-** floating point is required.
-**
-** -DSQLITE_USE_LONG_DOUBLE=1 Always use long double when high
-** precision is needed. Never fall back
-** to using Dekker algorithms.
-**
-** If the SQLITE_USE_LONG_DOUBLE macro is not defined, then the determination
-** of whether or not to use long double is made at run-time.
-*/
-#ifndef SQLITE_USE_LONG_DOUBLE
-# define SqliteUseLongDouble sqlite3Config.bUseLongDouble
-#elif SQLITE_USE_LONG_DOUBLE+0==1
-# define SqliteUseLongDouble 1
-#elif SQLITE_USE_LONG_DOUBLE+0==0
-# undef LONGDOUBLE_TYPE
-# define LONGDOUBLE_TYPE double
-# define SqliteUseLongDouble 0
-#else
-# error "SQLITE_USE_LONG_DOUBLE should be set to either 0 or 1"
-#endif
-
/*
** Structure containing global configuration data for the SQLite library.
**
@@ -4297,7 +4258,6 @@ struct Sqlite3Config {
u8 bUseCis; /* Use covering indices for full-scans */
u8 bSmallMalloc; /* Avoid large memory allocations if true */
u8 bExtraSchemaChecks; /* Verify type,name,tbl_name in schema */
- u8 bUseLongDouble; /* Make use of long double */
#ifdef SQLITE_DEBUG
u8 bJsonSelfcheck; /* Double-check JSON parsing */
#endif