On Thursday, 3 January, 2019 03:33, Dominique Devienne <[email protected]> wrote:
>PS: Strange how the compiler is reported as GCC 5.2. Mingw-build? >Instead of native MSVC? Cross-Compiled? >C:\Users\ddevienne>sqlite3 -version >3.26.0 2018-12-01 12:34:55 >bf8c1b2b7a5960c282e543b9c293686dccff272512d08865f4600fb58238b4f9 >C:\Users\ddevienne>sqlite3 >SQLite version 3.26.0 2018-12-01 12:34:55 >Enter ".help" for usage hints. >Connected to a transient in-memory database. >Use ".open FILENAME" to reopen on a persistent database. >sqlite> pragma compile_options; >COMPILER=gcc-5.2.0 >ENABLE_DBSTAT_VTAB >ENABLE_FTS3 >ENABLE_FTS5 >ENABLE_JSON1 >ENABLE_RTREE >ENABLE_STMTVTAB >ENABLE_UNKNOWN_SQL_FUNCTION >THREADSAFE=0 >sqlite> It is probably compiled with (one or another) MinGW port of GCC 5.2.0. I use the MinGW port of GCC 8.1.0 found here https://sourceforge.net/projects/mingw-w64/files/?source=navbar Specifically the 8.1.0 x86_64-win32-sjlj version https://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/8.1.0/threads-win32/sjlj/x86_64-8.1.0-release-win32-sjlj-rt_v6-rev0.7z Primarily this is because MSVC cannot do arithmetic -- it cannot do a lot of things -- it is a really crappy compiler -- as "lets pretend I'm an optimizing compiler" go. Of course, I have a real old version installed because it is a nightmare to install and takes many days of effort to turn off all the "bundled with crap" (especially that horrid Visual Studio crap) and return the computer to a useable state. Why cannot Microsoft have a compiler, just a compiler, with none of the added crap? (Then again, I find that the Windows gooey itself is nothing more than an environment to allow multiple command prompts at the same time, with none of this PowerSmell to stink up the place -- call me old-fashioned or even an old curmudgeon). This is a "native" port of GCC to Windows that produces "native" executables in either i86 or x64 (depending on the -m flag) and has all the necessary (and then some) x86 and i64 runtime libraries included. It is a "native windows" GCC compiler not a cross-compiler. Whether the distribution SQLite3 modules are built with native GCC or a cross-compiler I do not know. >sqlite -version 3.27.0 2019-01-03 00:44:03 120cb1768338eb86412fb69d4c7677247775bb37875ab3a98766cffd535falt2 2019-01-03 9:19:00 PY32 2.7 [D:\Source\SQLite] >sqlite SQLite version 3.27.0 2019-01-03 00:44:03 Enter ".help" for usage hints. Connected to a transient in-memory database. Use ".open FILENAME" to reopen on a persistent database. sqlite> pragma compile_options; ALLOW_COVERING_INDEX_SCAN ALLOW_URI_AUTHORITY COMPILER=gcc-8.1.0 DATETIME_NEW DEFAULT_CACHE_SIZE=262144 DEFAULT_FOREIGN_KEYS DEFAULT_MMAP_SIZE=0 DEFAULT_PAGE_SIZE=4096 DEFAULT_PROXYDIR_PERMISSIONS=0755 DEFAULT_RECURSIVE_TRIGGERS DEFAULT_WAL_AUTOCHECKPOINT=256 DEFAULT_WAL_SYNCHRONOUS=1 DEFAULT_WORKER_THREADS=8 ENABLE_8_3_NAMES=1 ENABLE_API_ARMOR ENABLE_COLUMN_METADATA ENABLE_COLUMN_USED_MASK ENABLE_COSTMULT ENABLE_CURSOR_HINTS ENABLE_DBSTAT_VTAB ENABLE_FTS3 ENABLE_FTS3_PARENTHESIS ENABLE_FTS4 ENABLE_FTS5 ENABLE_GEOPOLY ENABLE_JSON1 ENABLE_LOAD_EXTENSION ENABLE_LOCKING_STYLE=1 ENABLE_MEMORY_MANAGEMENT ENABLE_PREUPDATE_HOOK ENABLE_RBU ENABLE_RTREE ENABLE_SORTER_REFERENCES ENABLE_STMTVTAB ENABLE_STMT_SCANSTATUS EXPLAIN_ESTIMATED_ROWS EXTRA_INIT=core_init HAVE_ISNAN LIKE_DOESNT_MATCH_BLOBS MAX_ATTACHED=15 MAX_WORKER_THREADS=8 PRECISE_TIME SOUNDEX TEMP_STORE=2 THREADSAFE=1 USE_URI sqlite> --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
