================ @@ -46,6 +46,7 @@ static constexpr FormatInfo g_format_infos[] = { {eFormatHex, 'x', "hex"}, {eFormatHexUppercase, 'X', "uppercase hex"}, {eFormatFloat, 'f', "float"}, + {eFormatFloat128, '\0', "float128"}, ---------------- jasonmolenda wrote:
I'm not familiar with this part of lldb, but do we need an entry with a character code that can't be entered? I don't think there are commands which take the "long name" of these entries, do they? Vaguely relatedly, I wondered about `OptionGroupFormat::ParserGDBFormatLetter` which recognizes the gdb formatters (v. https://sourceware.org/gdb/current/onlinedocs/gdb.html/Output-Formats.html ) but I think just "f" for "float of undetermined size" is correct as-is? This is seen in commands like `x/2gx $fp` etc, which command aliases rewrite to a longer `memory read`. https://github.com/llvm/llvm-project/pull/98369 _______________________________________________ lldb-commits mailing list lldb-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits