Bug 863587

Summary:	sys-apps/ipmitool-1.8.19 fails to compile (lto): ipmi_dcmi.c:1956:30: error: dereferencing type-punned pointer will break strict-aliasing rules [-Werror=strict-aliasing]
Product:	Gentoo Linux	Reporter:	Agostino Sarubbo <ago>
Component:	Current packages	Assignee:	Sysadmin Bugs <sysadmin>
Status:	RESOLVED FIXED
Severity:	normal	CC:	anthonyryan1
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:
Bug Blocks:	618550
Attachments:	build.log

Description Agostino Sarubbo gentoo-dev

2022-08-04 10:44:15 UTC

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

Issue: sys-apps/ipmitool-1.8.18_p20201004-r3 fails to compile (lto).
Discovered on: amd64 (internal ref: lto_tinderbox)

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

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 1 Agostino Sarubbo gentoo-dev

2022-08-04 10:44:18 UTC

Created attachment 797626 [details]
build.log

build log and emerge --info

Comment 2 Agostino Sarubbo gentoo-dev

2022-11-06 13:15:47 UTC

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

Comment 3 Larry the Git Cow gentoo-dev

2023-09-23 23:17:25 UTC

The bug has been closed via the following commit(s):

https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=65133120acc4590beec5e77e6a92f2a7fc49b375

commit 65133120acc4590beec5e77e6a92f2a7fc49b375
Author:     Sam James <sam@gentoo.org>
AuthorDate: 2023-09-23 23:16:44 +0000
Commit:     Sam James <sam@gentoo.org>
CommitDate: 2023-09-23 23:16:46 +0000

    sys-apps/ipmitool: filter-lto & -fno-strict-aliasing
    
    Not really worried about fixing this properly at the moment given it's
    filled with device-specific hax anyway and hard to test.
    
    Closes: https://bugs.gentoo.org/863587
    Signed-off-by: Sam James <sam@gentoo.org>

 sys-apps/ipmitool/ipmitool-1.8.19-r1.ebuild | 155 ++++++++++++++++++++++++++++
 1 file changed, 155 insertions(+)