------- Comment #10 from joseph at codesourcery dot com 2010-04-15 21:30 ------- Subject: Re: Unexpected error message for bad command line argument
On Thu, 15 Apr 2010, manu at gcc dot gnu dot org wrote: > ------- Comment #9 from manu at gcc dot gnu dot org 2010-04-15 20:52 ------- > (In reply to comment #8) > > > > We have not yet begun implementation. For the semantics of group options, > > see Appendix 1 in my proposal (if -Wx implies -Wy and -Wz, then -Wno-y -Wx > > and -Wx -Wno-y both should disable -Wy but enable -Wz). > > Fair enough this is what i was planning to implement. But my question is how > you plan to implement this? We haven't determined who will end up implementing the proposal or produced an implementation design at that level of detail, but personally I would envisage that the .opt files would contain information about what options imply what sets of other options (and what options are exact aliases of other options) and that the awk scripts would generate appropriate datastructures to be used by code shared by the driver and cc1 etc.; certainly any code specific to a particular option, that is needed to determine the set of enabled features that are potentially relevant to multilib selection, must go somewhere that can be linked into both the driver and cc1. As well as back ends contributing code to be linked in both places, it's possible that front ends will also contribute such code (linked into all of cc1, cc1plus etc.), but generic descriptions in .opt files are preferred where possible. (There are certainly complications such as the implications of options from -On depending on both target and optimization level; I was imagining those would be resolved in the course of implementation rather than producing a detailed design for every patch in a long series up front. I should also point out that the focus of the planned work is the improvements to multilib selection, so some cleanups may end up not being implemented if they end up proving not to be relevant to sharing option-processing and feature-calculation code between the driver and cc1 and creating options structures that can be compared in the driver for multilib selection.) -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43687
