Summary: | net-misc/networkmanager-0.9.8.8 - hardened gcc-4.6.3 miscompiles due to -fpartial-inlining | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jan Kundrát (RETIRED) <jkt> |
Component: | Hardened | Assignee: | The Gentoo Linux Hardened Team <hardened> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gnome |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugzilla.gnome.org/show_bug.cgi?id=721465 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 915000 |
Description
Jan Kundrát (RETIRED)
![]() Looks like it fixed in newer gcc? (In reply to Magnus Granberg from comment #1) > Looks like it fixed in newer gcc? Yes, that's what I reported here three months ago. We could add a check to the networkmanager ebuild to automatically add -fno-partial-inlining to CFLAGS if a problematic compiler is detected. The question is, how to check for a problematic compiler? Is there something we can do with gcc-specs-directive() to determine whether this is gcc on a hardened profile? Way need to check for hardened compiler when it is GCC that have a bug and it is fixed in newer version? (In reply to Magnus Granberg from comment #4) > Way need to check for hardened compiler when it is GCC that have a bug and > it is fixed in newer version? Is this bug still relevant? Sould we just block against an older version of gcc and move on? Fixed in newer gcc >=4.7.3 |