I’m not saying it’s a bad suggestion - just pointing out that it likely wasn’t caused by carelessness.
Setting something up on odin would be tricky, but someone could look at that environment to see why it’s generating all these when we don’t see them elsewhere - maybe it would be simple to setup something elsewhere that gets the same result. > On Nov 11, 2015, at 7:15 AM, Dave Goodell (dgoodell) <dgood...@cisco.com> > wrote: > > On Nov 11, 2015, at 10:09 AM, Ralph Castain <r...@open-mpi.org> wrote: >> >> FWIW: I don’t think that’s the issue here. I don’t see these warnings on my >> CentOS7 box, for example. I think this is driven by the fact that odin has >> some very old compilers and a very different environment, and so it has >> historically generated more warnings. >> >> The warnings often are valid - they just don’t get issued by other >> compilers, or configure activates other code paths. > > Sure, but the automation could be set up to do builds on both Odin and newer > systems. I think it's easier to tend to this sort of warning cruft as it > happens, rather than big stomps later on, but that's just personal > preference. It would also hopefully reduce the amount of cherry picking that > needs to happen to release branches. > > *shrug* just a suggestion > > -Dave > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/11/18360.php
