863860 – app-text/tesseract-5.2.0: error: inlining failed in call to 'always_ inline' '__m512d _mm512_setzero_pd()': target specific option mismatch

Bug 863860 - app-text/tesseract-5.2.0: error: inlining failed in call to 'always_ inline' '__m512d _mm512_setzero_pd()': target specific option mismatch

Summary: app-text/tesseract-5.2.0: error: inlining failed in call to 'always_ inline' ...

Status:	UNCONFIRMED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Current packages (show other bugs)
Hardware:	AMD64 Linux

Importance:	Normal normal (vote)
Assignee:	Bernard Cafarelli

URL:	https://github.com/tesseract-ocr/tess...
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2022-08-05 20:14 UTC by Luke-Jr
Modified:	2022-09-15 13:41 UTC (History)
CC List:	1 user (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Luke-Jr 2022-08-05 20:14:34 UTC

configure tests -mavx512f (and other variants) with $CXX $CXXFLAGS -mavx512f (simplified) which detects compiler AVX512F support, but then builds with $CXX -mavx512f $CXXFLAGS which fails because my CXXFLAGS includes -mno-avx512f.

Probably the configure check should be adjusted so it detects no AVX512F support when the user specifies -mno-avx512f in CXXFLAGS. Or at the very least (if there's reason to enforce runtime detection even when the user has said "no"), building should use the same order so AVX512F is force-enabled for the files that use it.

Upstream bug: https://github.com/tesseract-ocr/tesseract/issues/3891

Comment 1 Luke-Jr 2022-09-15 13:41:21 UTC

Upstream is apparently not planning to fix this