Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-14 Thread Jens Alfke
> On Jul 13, 2017, at 3:41 PM, Keith Medcalf wrote: > > CLang must be just catching up. > > That is better though than Intel, Microsoft, et al, who make really shoddy > compilers (buggy and suitable for amateur use only) let alone have any actual > "advanced" features.

Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-13 Thread Keith Medcalf
Not really. (At least not for anyone else's Link Time Optimizer) LTO outputs the intermediate parse tree rather than object code into the .obj/.a files. The LTO linker merges all the parse tree's into a single parse tree then generates actual object code. In other words, it makes it "look"

Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-13 Thread Richard Hipp
On 7/13/17, Jens Alfke wrote: > > Have you tested Clang? These days it may generate even better code, We do a lot of testing with clang - it is part of our standard test protocol. It generates code that is slightly larger and slower than the GCC-generated code, but not

Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-13 Thread Jens Alfke
> On Jul 13, 2017, at 7:49 AM, Richard Hipp wrote: > > I've spent some time investigating this, and I think the answer is > that GCC simply generates better code. Have you tested Clang? These days it may generate even better code, especially with -Ofast and the link-time

Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-13 Thread Richard Hipp
On 7/9/17, Bob Friesenhahn wrote: > On Sat, 8 Jul 2017, Richard Hipp wrote: >> >> gcc-5.4: 491585 bytes, 1,124 million CPU cycles. >> icc-17.0: 536596 bytes, 1,274 million CPU cycles > > Sqlite3 has been cycle-optimized for GCC. You now have 29-days to > also

Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-09 Thread Bob Friesenhahn
On Sat, 8 Jul 2017, Richard Hipp wrote: (3) I compiled SQLite on each of gcc-5.4, gcc-7.1, clang-3.5, and icc-17.0 and compared both the size of the resulting binary and the performance. icc gave the largest binary and the slowest performance. Here are the actual results: gcc-5.4: 491585

Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-08 Thread Richard Hipp
On 7/8/17, Roberto C. wrote: > > while trying to install and sqlite package for R statistical language > (Rsqlite) I came across I bug: i could not compile the package with the > intel compiler ICC / ICPC. You can find the whole discussion (and the > solution) here -

Re: [sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-08 Thread Richard Hipp
On 7/8/17, Roberto C. wrote: > > The undefined symbol, __builtin_mul_overflow, is a GCC primitive. SQLite > has the option to call it directly. It's supposed to disable itself through > a some pre-processor checks if it's not supported by the current compiler, > but I believe

[sqlite] cannot compile sqlite3 with intel compiler (ICC) - log and hints for a possible solution

2017-07-08 Thread Roberto C.
Hi, while trying to install and sqlite package for R statistical language (Rsqlite) I came across I bug: i could not compile the package with the intel compiler ICC / ICPC. You can find the whole discussion (and the solution) here - https://github.com/rstats-db/RSQLite/issues/223 However, the