database/sqlite
1
0
Fork 0
mirror of https://github.com/sqlite/sqlite.git synced 2025-07-27 20:41:58 +03:00
Code Activity

Remove a few more traces of long double from the code.

Browse Source 
FossilOrigin-Name: 11d6a89e4a25c3f884ff617036d239dc42522859400cd1f4674634f6c7adbb02
This commit is contained in:
drh
2024-10-02 11:34:11 +00:00
parent e8b2c92240
commit 010f9f8704
5 changed files with 9 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
ext/wasm/api/sqlite3-wasm.c
View File

@ -127,10 +127,6 @@
# define SQLITE_USE_URI 1
#endif
#ifndef SQLITE_USE_LONG_DOUBLE
# define SQLITE_USE_LONG_DOUBLE 0
#endif
#ifdef SQLITE_WASM_EXTRA_INIT
# define SQLITE_EXTRA_INIT sqlite3_wasm_extra_init
#endif
@ -163,8 +159,6 @@
# define SQLITE_OMIT_PROGRESS_CALLBACK
# undef SQLITE_OMIT_WAL
# define SQLITE_OMIT_WAL
# undef SQLITE_USE_LONG_DOUBLE
# define SQLITE_USE_LONG_DOUBLE 0
/*
The following OMITs do not work with the standard amalgamation, so
require a custom build:
@ -227,23 +221,6 @@
// See also:
//__attribute__((export_name("theExportedName"), used, visibility("default")))
#if 0
/* Details at https://sqlite.org/forum/forumpost/cbfb0d0ac0a4e349
**
** Summary: changing to `double` reduces the wasm file size by a mere
** 2k. It is hypothetically not possible that any clients rely on
** doubles larger than 64-bit because there is no mapping between C
** and JS for them. i.e. we "could" switch LONGDOUBLE_TYPE to double
** for wasm builds with very little risk of problems. Clang 18.1 maps
** `long double` to float128 but Emscripten doesn't (cannot) expose
** that to JS.
**
** See also: SQLITE_USE_LONG_DOUBLE
*/
#undef LONGDOUBLE_TYPE
#define LONGDOUBLE_TYPE double
#endif
/*
** Which sqlite3.c we're using needs to be configurable to enable
** building against a custom copy, e.g. the SEE variant. Note that we