Summary: | sys-fs/udev-233 fails to compile with gcc-7.1.0 or gcc-7.3.0 and '-O3' | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Philipp Psurek <philipp.psurek+gentoo> |
Component: | Current packages | Assignee: | udev maintainers <udev-bugs> |
Status: | RESOLVED OBSOLETE | ||
Severity: | major | CC: | josef64 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=620092 https://github.com/systemd/systemd/issues/6119 |
||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 617524 | ||
Attachments: |
udev-233_build.log.xz
udev-233_build.log udev-233 compilation with -O2 CFLAG |
Description
Philipp Psurek
2017-07-08 19:58:46 UTC
This is a bug in gcc-7.1.0. Created attachment 482390 [details] udev-233_build.log udev-233 compilation with -O2 CFLAG Thank you Mike for the fast categorization of this bug and linking it to bug 620092. Indeed compiling udev-233 with 7.1.0-r1 and changing the CFLAG from -03 to -O2 was a success. For the sake of completeness I provide the build log I extracted from the console. There are some warnings, but no errors. With the next issue of GCC-7 I'll report how udev-233 compiles with -03. It might be a good idea to force -O2 in the ebuild. But I think that no change is needed as this seems to be a GCC-7 only bug, the users of other GCCs have no problems with -O3 and GCC-7 is not for the masses. sys-fs/udev-233 fails to compile with '-O3' even with gcc-7.3.0. I assume this version of gcc is quite mature. On the other hand sys-fs/udev-236-r1 compiles well with '-O3' and gcc-7.3.0 and even with gcc-7.1.0(!). All mentioned compile runs has been preformed on amd64 and arm. This bug seems not to be a gcc bug. Please close this bug unresolved or resolve it through removing sys-fs/udev-233 from portage tree. I believe this was worked around in systemd (and udev) at some point. It was definitely a bug in gcc-7.1.0 though. Marking this obsolete since the problem no longer occurs with the latest versions of each. |