You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cdt-cpp --help has a few issues. It seems worthwhile to review and correct this text. While we are at it, it seems useful to review all the cdt tools: cdt-abidiff cdt-cc cdt-cpp cdt-init cdt-ld.
Here are some cpp-cdt problem examples:
OVERVIEW: cdt-cpp (Eosio C++ -> WebAssembly compiler) Should Eosio be replaced by AntelopeIO?
inconsistent termination: some help ends with a period while some does not
-O=<string> - Optimization level s, 0-3 - string could/should be s or something else? What about -O3? Is that valid? Evaluate this --flag=<string> for all similar options.
is --fnative always x86_64?
The text was updated successfully, but these errors were encountered:
cdt-cpp --help
has a few issues. It seems worthwhile to review and correct this text. While we are at it, it seems useful to review all the cdt tools:cdt-abidiff cdt-cc cdt-cpp cdt-init cdt-ld
.Here are some cpp-cdt problem examples:
OVERVIEW: cdt-cpp (Eosio C++ -> WebAssembly compiler)
Should Eosio be replaced by AntelopeIO?-O=<string> - Optimization level s, 0-3
-string
could/should bes
or something else? What about-O3
? Is that valid? Evaluate this--flag=<string>
for all similar options.--fnative
always x86_64?The text was updated successfully, but these errors were encountered: