https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58200
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- > With most portable compilers, code generation options are traditionally > used for variations in the target interface, and not to introduce > functionality. Worse, the top-level entry says: > > 2.9 Options for code generation conventions Looking at the content of the 2.9 section, I see (at least) three subsets of options: (1) those for code generation conventions (2) frontend optimizations (3) options enabling runtime diagnostics A quick and lazy fix would be to replace "Options for code generation conventions" with "Other options for code generation". IMO it would be better to add new sections for (2) and (3), put (2) after 2.3 and () after 2.5. Does this sound OK? If yes, I'ld like to also move -ffpe-trap=list, -ffpe-summary=list, and -fno-backtrace from 2.5 to the new section "options enabling runtime diagnostics". I'ld also like to move the options -fdefault*, -finteger* and -freal* to a new section "Options changing the kind of variables", after the new section "Frontend optimizations", and reverse their order: -finteger* and -freal* before -fdefault*. Comments welcomed.
