Package Details: libgccjit-fast-optimized 16.1.0-2

Git Clone URL: https://aur.archlinux.org/gcc-fast-optimized.git (read-only, click to copy)
Package Base: gcc-fast-optimized
Description: Just-In-Time Compilation with GCC backend optimized with -O3 and local cpu tuning
Upstream URL: https://gcc.gnu.org
Keywords: compilers, gcc, local optimized, tuning,
Licenses: GFDL-1.3-or-later, GPL-3.0-or-later WITH GCC-exception-3.1
Conflicts: libgccjit
Provides: libgccjit, libgccjit.so
Replaces: libgccjit
Submitter: devlavender
Maintainer: devlavender
Last Packager: devlavender
Votes: 0
Popularity: 0.000000
First Submitted: 2026-06-23 17:28 (UTC)
Last Updated: 2026-06-25 22:52 (UTC)

Required by (17)

Sources (4)

Pinned Comments

devlavender commented on 2026-06-26 16:17 (UTC) (edited on 2026-07-03 21:55 (UTC) by devlavender)

There's a request for deletion of this package, I responded it on the mailing list but I'm not sure the email arrived the list. It's been argued that -O3 and local tuning should be part of the local makepkg.conf.

The package description fails indeed to point out all optimizations, but even if it was only those optimizations, this is simply not how the original gcc package's build works. Some makepkg.conf flags are suppressed and gcc has specific mechanics that simply adding those options to the makepkg.conf won't build an optimized gcc the way you expect.

You cannot build stage1 with -O3, for instance, and that's why the option is suppressed. It's in fact the safest way to go to put those options in the PKGBUILD script, that's why this package (and the related packages) do exist.

Latest Comments

devlavender commented on 2026-06-26 16:17 (UTC) (edited on 2026-07-03 21:55 (UTC) by devlavender)

There's a request for deletion of this package, I responded it on the mailing list but I'm not sure the email arrived the list. It's been argued that -O3 and local tuning should be part of the local makepkg.conf.

The package description fails indeed to point out all optimizations, but even if it was only those optimizations, this is simply not how the original gcc package's build works. Some makepkg.conf flags are suppressed and gcc has specific mechanics that simply adding those options to the makepkg.conf won't build an optimized gcc the way you expect.

You cannot build stage1 with -O3, for instance, and that's why the option is suppressed. It's in fact the safest way to go to put those options in the PKGBUILD script, that's why this package (and the related packages) do exist.