On Tue, 11 Nov 2008, Richard Sandiford wrote: > (Which I suppose raises the question: should > > -march=r10000 -mno-branch-likely > > be an error, or should it silently disable -mfix-r10000? My vote is > for "error". You can always write -march=r10000 -mno-branch-likely > -mno-fix-r10000 is that's really what you mean. > > The suggested change -- swapping these two blocks around -- should do that.) FWIW, my preference is for an error too. The main reason being to warn the user about the incompatibility of these options. For the opposite case a scenario where in a building system they come from different places each can be imagined. Or one could be buried somewhere down the Makefiles in a platform-specific section of an odd package. In the end the user might not be fully aware they are doing something wrong and the result would be broken packages would fail randomly on the affected processors at the run time. Always prefer a build error to a run-time error if possible. Maciej
