When discussing optimization levels, don't put the compiler options in
.Op. None of the other manual pages do it when discussing options in the main text, so this one shouldn't, either. Also, use .Pq instead of another odd constructhyphenation isn't an issue here, since it's desireable to have the contents of that digression appear together, and it's already in another macro, anyway).
This commit is contained in:
parent
06a4bf789c
commit
d489ec12ce
@ -97,7 +97,8 @@ for things other than builds.
|
|||||||
.Pq Vt str
|
.Pq Vt str
|
||||||
Controls the compiler setting when compiling C code.
|
Controls the compiler setting when compiling C code.
|
||||||
Optimization levels above
|
Optimization levels above
|
||||||
.Oo Fl O ( O2 , No ...\& ) Oc
|
.Fl O
|
||||||
|
.Pq Fl O2 , No ...
|
||||||
are not supported.
|
are not supported.
|
||||||
.Va BDECFLAGS
|
.Va BDECFLAGS
|
||||||
is provided as a set of
|
is provided as a set of
|
||||||
|
Loading…
Reference in New Issue
Block a user