LLVM

~/go/src/go.googlesource.com/go/src/compress/flate $ tinygo test -c compress/flate && ./flate.test
~/go/src/go.googlesource.com/go/src/compress/flate $ go test -c &&  ./flate.test
PASS

• I have tried using the latest released version of Numba (most recent is
  visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
• I have included a self contained code sample to reproduce the problem.
  i.e. it's possible to run as 'python bug.py'.

I think I have discovered a very minor bug - or rather inconsistency with numpy - in Numba's implementation

If we have the following resources:

a.txt
folder/b.txt

And run the following code:

object Main {
  def main(args: Array[String]): Unit =
    if (Option(this.getClass().getResourceAsStream("/a.txt")).isDefined) println("Loaded /a.txt")
    if (Option(this.getClass().getResourceAsStream("/folder/b.txt")).isDefined) println("Loaded /folder/b.txt")
    if (Option(this

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

They are awful.

To elaborate, currently the parser will usually issue an error in the form "failed trying to parse a [foo]" where [foo] may be term, expression, pattern, etc. Sometimes it will give even worse errors resembling "parser expected end of input, but got ..." which does not explain well what the user did that was wrong. The parser also stops after 1 error currently. A recoverable par

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.

There is a lowering pass called LLHDToLLVM (CLI flag --convert-llhd-to-llvm) that collects all conversion patterns necessary to lower a design compiled by the Moore compiler (which outputs comb, hw, and llhd operations) to LLVM IR code that can be used by llhd-sim for simulation. Most of those patterns are more general though and could be useful for other backends. This includes all comb