Summary: | sys-cluster/openmpi-1.4.3 strips '--' from --param arg to GCC when multiple --param args are specified | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Joshua Rich <joshua.rich> |
Component: | Current packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | bircoph, pchrist |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
portage build.log.gz
configure config.log portage environment |
Description
Joshua Rich
2011-01-10 22:48:02 UTC
Created attachment 259508 [details]
portage build.log.gz
Created attachment 259509 [details]
configure config.log
Created attachment 259510 [details]
portage environment
Well, 1) This is not a gentoo bug. You should report this upstream. 2) Why do you have to use all these custom cflags? unless you're doing some exotic custom test case, you shouldn't. As a start, I don't want to bother our maintainers with this. I'll resolve it as UPSTREAM. If you still insist that they should be notified for a reason, you're free to reopen it. This can also easily be duplicate of bug #324697 . Bug filed upstream: https://svn.open-mpi.org/trac/ompi/ticket/2684 For reference, removing the graphite optimisation flags would make no difference to the output. I'd hardly call flags besides the '--param' ones "custom", as they are the recommended ones. I specify the architecture with the "-march" flag here as I'm using distcc. All these "custom" flags are used because this machine is being used for high-performance mathematical computations. Note that doesn't imply high-stability. Thanks and regards, Joshua Rich (In reply to comment #4) > Well, > > 1) This is not a gentoo bug. You should report this upstream. > 2) Why do you have to use all these custom cflags? unless you're doing some > exotic custom test case, you shouldn't. > > As a start, I don't want to bother our maintainers with this. I'll resolve it > as UPSTREAM. If you still insist that they should be notified for a reason, > you're free to reopen it. > I should add that --param $val=$arg has nothing to do with "unstable" or "unsafe" flags. There is no other way to use distcc to compile a program for the specific processor on hosts with a different CPU. You may consider that -m(32|64) -march=$arch --param $arg=$val ... is a replacement for -march=native. |