Bug 853895 – sys-devel/llvm-15.0.4 fails to compile: DwarfDebug.h:288: error: type llvm::AccelTableKind violates the C++ One Definition Rule [-Werror=odr]

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Agostino Sarubbo 2022-06-23 16:08:00 UTC]

https://blogs.gentoo.org/ago/2020/07/04/gentoo-tinderbox/

Issue: sys-devel/llvm-14.0.5 fails to compile.
Discovered on: amd64 (internal ref: tinderbox)

NOTE:
This machine uses lto with CFLAGS=-flto -Werror=odr -Werror=lto-type-mismatch -Werror=strict-aliasing

[Comment 1 Agostino Sarubbo 2022-06-23 16:08:04 UTC]

Created attachment 787115 [details]
build.log.xz

build log and emerge --info (compressed because it exceeds attachment limit, use 'xzless' to read it)

[Comment 2 Agostino Sarubbo 2022-06-23 16:08:05 UTC]

Error(s) that match a know pattern in addition to what has been reported in the summary:


-- Could NOT find OCaml (missing: OCAMLFIND OCAML_VERSION OCAML_STDLIB_PATH) 
-- Could NOT find Python module yaml
FAILED: lib64/libLLVM-14.so 
/var/tmp/portage/sys-devel/llvm-14.0.5/work/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.h:288: error: type ‘llvm::AccelTableKind’ violates the C++ One Definition Rule [-Werror=odr]

[Comment 3 Agostino Sarubbo 2022-06-24 07:05:04 UTC]

(In reply to Agostino Sarubbo from comment #0)
> Discovered on: amd64 (internal ref: tinderbox)

internal ref is: lto_tinderbox

[Comment 4 Agostino Sarubbo 2022-07-26 08:59:37 UTC]

Here is a bit of explanation:

-Werror=lto-type-mismatch:
User to find possible runtime issues in packages. It likely means the package is unsafe to build & use with LTO.
For projects using the same identifier but with different types across different files, they must be fixed to be consistent across the codebase.

-Werror=odr:
Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO. C++ code must comply with the One Definition Rule (ODR) - see https://en.cppreference.com/w/cpp/language/definition#One_Definition_Rule.

-Werror=strict-aliasing:
Used to find possible runtime issues in packages. These bugs are a problem anyway but may be even worse when combined with LTO.

Workarounds:
- If upstream is friendly and still active, file a bug upstream. For emulators, codecs, games, or multimedia packages, it may be worth just applying a workaround instead, as upstreams sometimes aren't receptive to these bugs (VALID FOR ALL).
- Use the new 'filter-lto' from flag-o-matic.eclass as it's likely to be unsafe with LTO (VALID FOR lto-type-mismatch - odr).
- Fix it yourself if interested, of course (VALID FOR ALL).
- Append-flags -fno-strict-aliasing (VALID FOR strict-aliasing).
- Use memcpy() but a union is sometimes suitable too (VALID FOR strict-aliasing).
- -fstrict-aliasing is implied by -O2, so this must be addressed in some form (VALID FOR strict-aliasing).

See also: https://marc.info/?l=gentoo-dev&m=165639574126280&w=2

[Comment 5 Agostino Sarubbo 2022-11-08 14:44:29 UTC]

lto_tinderbox has reproduced this issue with version 15.0.4 - Updating summary.

[Comment 6 Eli Schwartz 2024-05-13 04:34:59 UTC]

We filter lo in llvm's ebuild now for this reason.