database/sqlite
1
0
Fork 0
mirror of https://github.com/sqlite/sqlite.git synced 2025-08-01 06:27:03 +03:00
Code Activity

Add an #if'd-out block to sqlite3-wasm.c mentioning the LONGDOUBLE_TYPE, as brought up in [forum:cbfb0d0ac0a4e349 | forum post cbfb0d0ac]. No functional changes.

Browse Source 
FossilOrigin-Name: 0b83e8f1ef53b35a9dda0740b4922b8691428f7484f3058833a961f3f8d0b178
This commit is contained in:
stephan
2024-10-01 10:49:30 +00:00
parent cacef23082
commit ed94e0e677
3 changed files with 23 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -221,6 +221,21 @@
// 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.
*/
#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