LLVM

I see comments suggesting adding this to understand how loops are being handled by numba, and in the their own FAQ (https://numba.pydata.org/numba-doc/latest/user/faq.html)

from llvmlite import binding as llvm
llvm.set_option('','--debug-only=loop-vectorize')

You would then create your njit function and run it, and I believe the idea is that it prints debug information about whether

$ sw_vers
ProductName:	Mac OS X
ProductVersion:	10.14.6
BuildVersion:	18G9028

struct utsname name;
    if (uname(&name) == 0) {
        printf("os.name=%s\n",name.sysname);
        printf("os.version=%s\n",name.release);
    }
// os.name=Darwin
// os.version=18.7.0

Seems no way to map Darwin version to Mac OS X version.

/usr/libexec/PlistBuddy -c "Print:

Hey everyone!

mapd-core-cpu is already available on conda-forge (https://anaconda.org/conda-forge/omniscidb-cpu)

now we should add some instructions on the documentation.

at this moment it is available for linux and osx.

some additional information about the configuration:

1. for now, always install omniscidb-cpu inside a conda environment (also it is a good practice), eg:

Scenario:
I have a project, with build tools of cmake, when I try to run it with cling. It prompts some headers are not included.

So I was wondering if there is a way to make use of the cmake script to load the build environment into cling and run directly?

Appreciate the great work!

While the test_suite presented in #589 does work, it is still pretty simple and can be improved and enhanced.

• Add tests for gnutils and coreutils.
• Add necessary utilities so more complex programs can be compiled from sources.
• Integrate CMake, so one could write something like make validate and the subset of test that is deemed necessary (for example everything with min t

Currently, the architecture of the CLI is based on (sub)commands and options. Commands are expected to be provided as the first argument, and do effectively decide which feature is to be used. OTOH, options provide parameters to the commands. However, there is no syntactical difference, as both commands and options start with -- or -i. As a result, we rely on properly formating --help and on

The CodeChecker cmd subcommand communicates with the server via Thrift, and on a Jenkins docker image, I have tried to use it to get run information from a local CodeChecker server. The output of the CodeChecker cmd runs command was just the help message. I have found out that using a proxy is not supported right now, and the issue was solved by disabling proxy via unsetting the environmental

std.math was split into a package with v2.097. This might imply that some little helpers (isNaN etc.) aren't inlined any longer without LTO (incl. Phobos), thus reducing performance of some math functions.