Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Add an #if'd-out block to sqlite3-wasm.c mentioning the LONGDOUBLE_TYPE, as brought up in forum post cbfb0d0ac. No functional changes. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
0b83e8f1ef53b35a9dda0740b4922b86 |
| User & Date: | stephan 2024-10-01 10:49:30 |
Context
|
2024-10-01
| ||
| 16:55 | Add compile-time option -DSQLITE_USE_LONG_DOUBLE=0 to omit all attempts to use "long double". Or =1 to omit attempts to use the Dekker algorithms to achieve high-resolution floating point. (check-in: ca5964ef user: drh tags: trunk) | |
| 10:49 | Add an #if'd-out block to sqlite3-wasm.c mentioning the LONGDOUBLE_TYPE, as brought up in forum post cbfb0d0ac. No functional changes. (check-in: 0b83e8f1 user: stephan tags: trunk) | |
|
2024-09-30
| ||
| 18:19 | Fix the character width tables for the CLI such that all unicode code-points less than 0x300 have a width of 1. This is in fact the case for Mac, Ubuntu, and Windows. (check-in: f0c5a86f user: drh tags: trunk) | |
Changes
Changes to ext/wasm/api/sqlite3-wasm.c.
| ︙ | ︙ | |||
217 218 219 220 221 222 223 224 225 226 227 228 229 230 |
** this writing we are tied to Emscripten for various reasons
** and cannot test the library with other build environments.
*/
#define SQLITE_WASM_EXPORT __attribute__((used,visibility("default")))
// See also:
//__attribute__((export_name("theExportedName"), used, visibility("default")))
/*
** 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
** #include the .c file, rather than the header, so that the WASM
** extensions have access to private API internals.
**
** The caveat here is that custom variants need to account for
| > > > > > > > > > > > > > > > | 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 |
** this writing we are tied to Emscripten for various reasons
** and cannot test the library with other build environments.
*/
#define SQLITE_WASM_EXPORT __attribute__((used,visibility("default")))
// 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
** #include the .c file, rather than the header, so that the WASM
** extensions have access to private API internals.
**
** The caveat here is that custom variants need to account for
|
| ︙ | ︙ |