llvm
meson
llvm | meson | |
---|---|---|
10 | 111 | |
1,166 | 5,278 | |
3.9% | 1.3% | |
10.0 | 9.8 | |
7 days ago | about 24 hours ago | |
Python | ||
GNU General Public License v3.0 or later | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
llvm
-
Vcc – The Vulkan Clang Compiler
Intel's modern compilers (icx, icpx) are clang-based. There is an open-source version [1], and the closed-source version is built atop of this with extra closed-source special sauce.
AOCC and ROCm are also based on LLVM/clang.
[1] https://github.com/intel/llvm
-
device::aspects ?
You are not missing anything spec-wise, it is just that particular version of the compiler/runtime doesn't support that query. Support for it was added in intel/llvm#7937 and it should be available in the next oneAPI release.
-
How to install OpenCL for AMD CPU?
Install the Intel OpenCL CPU Runtime. AMD CPUs are x86-64 too, so they work just like Intel CPUs do. Afaik, performance is significantly better than with POCL. This also works with EPYC, like the new 96-core Genoa.
-
Modern Software Development Tools and oneAPI Part 2
The Meson build system Version: 1.0.0 Source dir: /var/home/sri/Projects/simple-oneapi Build dir: /var/home/sri/Projects/simple-oneapi/builddir Build type: native build Project name: simple-oneapi Project version: 0.1.0 C compiler for the host machine: clang (clang 16.0.0 "clang version 16.0.0 (https://github.com/intel/llvm 08be083e07b1fd6437267e26adb92f1b647d57dd)") C linker for the host machine: clang ld.bfd 2.34 C++ compiler for the host machine: clang++ (clang 16.0.0 "clang version 16.0.0 (https://github.com/intel/llvm 08be083e07b1fd6437267e26adb92f1b647d57dd)") C++ linker for the host machine: clang++ ld.bfd 2.34 Host machine cpu family: x86_64 Host machine cpu: x86_64 Build targets in project: 1 Found ninja-1.11.1.git.kitware.jobserver-1 at /var/home/sri/.local/bin/ninja
-
Modern Software Development Tools and oneAPI Part 1
$ sudo mkdir -p /opt/intel $ sudo mkdir -p /etc/OpenCL/vendors/intel_fpgaemu.icd $ cd /tmp $ wget https://github.com/intel/llvm/releases/download/2022-WW50/oclcpuexp-2022.15.12.0.01_rel.tar.gz $ wget https://github.com/intel/llvm/releases/download/2022-WW50/fpgaemu-2022.15.12.0.01_rel.tar.gz $ sudo bash # cd /opt/intel # mkdir oclfpgaemu- # cd oclfpgaemu- # tar xvfpz /tmp/fpgaemu-2022.15.12.0.01_rel.tar.gz # cd .. # mkdir oclcpuexp_ # cd oclcpuexp- # tar xvfpz /tmp/oclcpuexp- # cd ..
-
Cross Platform Computing Framework?
oneAPI includes an implementation of SYCL called DPC++. This implementation supports Intel, Nvidia and AMD GPUs (currently for Nvidia and AMD you need to build the support from the source) but oneAPI also includes some libraries too like oneDNN and oneMKL that use SYCL.
-
Does an actually general purpose GPGPU solution exist?
Yes, you can use multiple backends with the same compiled binary. For example you can use DPC++ with Nvidia, AMD and Intel GPU at the same time. ComputeCpp also has the ability to output a binary that can target multiple targets. Each backend generates the ISA for each GPU, and then the SYCL runtime chooses the right one at execution time. There is no ODR violation because each GPU executable is stored on separate ELF sections and loaded at runtime : the C++ linker does not see them. The code doesn't need to have any layers, the only changes you might (but don't have to) make are to optimize for specific processor features.
-
Why Does SYCL Have Different Implementations, and What Version to Use for GPGPU Computing(With Slower CPU Mode for Testing/No Gpu Machines)?
Intel LLVM SYCL oneAPI DPC++ - an open source implementation of SYCL that is being contributed to the LLVM project
-
How to set up Intel oneAPI?
I'm using intel cpu, and after reading this i'm just curious can i set this up with portage? Are there any ebuilds to build this? Do i need whole toolchain from intel site (3Gb+) or just 300 mb tar from their github?
- Benchmarking Division and Libdivide on Apple M1 and Intel AVX512
meson
- Ask HN: How to handle user file uploads?
-
Which Build Tool for a Bootstrappable Project?
[1]: https://github.com/mesonbuild/meson/issues/8153
-
Building Waybar fails
The Meson build system Version: 1.2.3 Source dir: /home/patrik/workspace/Waybar Build dir: /home/patrik/workspace/Waybar/build Build type: native build Project name: waybar Project version: 0.9.24 C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-5) 13.2.0") C linker for the host machine: cc ld.bfd 2.41 C++ compiler for the host machine: c++ (gcc 13.2.0 "c++ (Debian 13.2.0-5) 13.2.0") C++ linker for the host machine: c++ ld.bfd 2.41 Host machine cpu family: x86_64 Host machine cpu: x86_64 Compiler for C++ supports link arguments -lc++fs: NO Compiler for C++ supports link arguments -lc++experimental: NO Compiler for C++ supports link arguments -lstdc++fs: YES Program git found: YES (/usr/bin/git) WARNING: You should add the boolean check kwarg to the run_command call. It currently defaults to false, but it will default to true in future releases of meson. See also: https://github.com/mesonbuild/meson/issues/9300 Has header "filesystem" : YES Checking if "nl_langinfo with _NL_TIME_WEEK_1STDAY, _NL_TIME_FIRST_WEEKDAY" : links: YES Run-time dependency threads found: YES Found pkg-config: /usr/bin/pkg-config (1.8.1) Run-time dependency fmt found: YES 9.1.0 Run-time dependency spdlog found: YES 1.12.0 Run-time dependency wayland-client found: YES 1.22.0 Run-time dependency wayland-cursor found: YES 1.22.0 Run-time dependency wayland-protocols found: YES 1.32 Run-time dependency gtkmm-3.0 found: YES 3.24.8 Run-time dependency dbusmenu-gtk3-0.4 found: YES 16.04.0 Run-time dependency gio-unix-2.0 found: YES 2.78.1 Run-time dependency jsoncpp found: YES 1.9.4 Run-time dependency sigc++-2.0 found: YES 2.12.1 Found CMake: /usr/bin/cmake (3.27.7) Run-time dependency libinotify found: NO (tried pkgconfig and cmake) Run-time dependency epoll-shim found: NO (tried pkgconfig and cmake) Run-time dependency libinput found: YES 1.23.0 Run-time dependency libnl-3.0 found: YES 3.7.0 Run-time dependency libnl-genl-3.0 found: YES 3.7.0 Run-time dependency upower-glib found: YES 1.90.2 Run-time dependency libpipewire-0.3 found: YES 0.3.85 Run-time dependency playerctl found: YES 2.4.1 Run-time dependency libpulse found: YES 16.1 Run-time dependency libudev found: YES 252 Run-time dependency libevdev found: YES 1.13.1 Run-time dependency libmpdclient found: YES 2.20 Run-time dependency xkbregistry found: YES 1.6.0 Run-time dependency jack found: YES 0.126.0 Run-time dependency wireplumber-0.4 found: YES 0.4.15 Library sndio found: YES Checking for function "sioctl_open" with dependency -lsndio: YES Run-time dependency gtk-layer-shell-0 found: YES 0.8.1 Run-time dependency systemd found: YES 252 Computing int of "__cpp_lib_chrono" : 201611 Configuring waybar.service using configuration Run-time dependency cava found: NO (tried pkgconfig and cmake) Looking for a fallback subproject for the dependency cava Executing subproject cava cava| Project name: cava cava| Project version: 0.9.1 cava| C compiler for the host machine: cc (gcc 13.2.0 "cc (Debian 13.2.0-5) 13.2.0") cava| C linker for the host machine: cc ld.bfd 2.41 cava| Has header "iniparser.h" : NO cava| Has header "iniparser4/iniparser.h" : NO Message: cava is not found. Building waybar without cava subprojects/cava-0.9.1/meson.build:65:3: ERROR: Problem encountered: iniparser library is required A full log can be found at /home/patrik/workspace/Waybar/build/meson-logs/meson-log.txt WARNING: Running the setup command as `meson [options]` instead of `meson setup [options]` is ambiguous and deprecated.
-
How to find a list of all gcc errors/warnings?
As it happens, I recently landed a PR in meson to add a clang-like Weverything mode that includes all of that, so you can get a minimal list of more or less all GCC warnings, organized by version, from the meson source here: https://github.com/mesonbuild/meson/blob/710a753c78077220b13a9f7e999dcdb61339efb1/mesonbuild/compilers/mixins/gnu.py
-
Makefile Tutorial
Came here to post the same. The answer for How to build software? is Meson[1] for C and C++ and also other languages. Works well on Windows and Mac, too.
I’ve written a small Makefile to learn the basic and backgrounds. Make is fine. But the next high-level would have been Autotools, which is an intimidating and weird set of tools. Most new stuff written in C/C++ use now Meson and it feels sane.
[1] https://mesonbuild.com
-
CMake x make?
If you are very fortunate, you'll be able to choose something else. I like meson myself: it looks a bit like python, it's popular, small, simple, well-documented, easy to install and update, and it works well everywhere.
-
C++ Papercuts
I suggest changing the build tool. Meson improved C and C++ a lot:
https://mesonbuild.com/
The dependency declaration and auto-detection is nice. But the hidden extra is WrapDB, built-in package management (if wanted):
https://mesonbuild.com/Wrap-dependency-system-manual.html
-
A Modern C Development Environment
> C's only REAL problem (in my opinion) which is the lack of dependency management. Most everything else can be done with a makefile and a half decent editor.
Care to hear about our lord and saviour Meson?
Both of your quoted problems are mutually incompatible: dependency management isn't the job of the compiler, it's a job for the build or host system. If you want to keep writing makefiles, be prepared to write your own `wget` and `git` invocations to download subprojects.
Meanwhile, Meson solves the dependency management problem in a way that makes both developers and system integrators/distributions happy. It forces you to make a project that doesn't have broken inter-file or header dependency chains and cleans up all the clutter and cruft of a makefile written for any non-trivial project, while making it trivial to integrate other meson projects into your build, let other people integrate your project into theirs, and provides all of the toggles and environment variables distribution developers need to package your library properly. You can really have your cake and eat it too.
https://mesonbuild.com/
-
cgen: another declarative CMake configuration generator
Other people going down this route seem to end up writing cmake replacements instead. I'm thinking of something like meson here except that meson never intended to transpile to cmake.
- Makefile vs Cmake - Objective comparison ?
What are some alternatives?
pocl - pocl - Portable Computing Language
CMake - Mirror of CMake upstream repository
oneTBB - oneAPI Threading Building Blocks (oneTBB)
ninja - a small build system with a focus on speed
AdaptiveCpp - Implementation of SYCL and C++ standard parallelism for CPUs and GPUs from all vendors: The independent, community-driven compiler for C++-based heterogeneous programming models. Lets applications adapt themselves to all the hardware in the system - even at runtime!
SCons
OCL-SDK
Bazel - a fast, scalable, multi-language and extensible build system
featuresupport
cmake-init - The missing CMake project initializer
Hackintosh-Intel - Hackintosh Intel
BitBake - The official bitbake Git is at https://git.openembedded.org/bitbake/. Do not open issues or file pull requests here.