Summary: | dev-libs/crypto++-5.5.2: does not compile with -O2 and -funroll-loops CXXFLAGS option | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | François Agrech <f.agrech> |
Component: | [OLD] Library | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
Status: | VERIFIED WONTFIX | ||
Severity: | minor | CC: | jlp.bugs |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
URL: | http://www.gentoo.org/doc/en/gcc-optimization.xml | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
François Agrech
2008-06-14 13:28:44 UTC
as per url funroll-loops is prone with faults. Other documentation indicates that funroll-loops as a concept make stuff slower. as such i'm not going to fix this. What about adding a warning about that in the ebuild? This could save some time searching for the problem for some people. (In reply to comment #2) > What about adding a warning about that in the ebuild? no. > This could save some time searching for the problem for some people. The valuable learning experience is to drop silly CFLAGS. By putting a warning some people will just keep using it and expecting every other package to work with a silly broken cflag. I was thinking about a message along the line of: "You have enabled funroll-loops, this package won't compile with this flag. Moreover, it is not wise to enable this flag as it has been proven to make things slower. Please unset this flag in your make.conf flag and reemerge" I mean a message that inform the user about the problem and at the same time that discourage from using this flag in other packages. |