Similarly to D85836, collapse all Scalar float types to a single enum
value, and use APFloat semantics to differentiate between. This
simplifies the code, and opens to door to supporting other floating
point semantics (which would be needed for fully supporting
architectures with more interesting float types such as PPC).
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
lldb/source/Utility/Scalar.cpp | ||
---|---|---|
68 | std::array or ArrayRef maybe? |
lldb/source/Utility/Scalar.cpp | ||
---|---|---|
68 | With a std::array, I'd have to explicitly specify the size, and I'm _really_ not sure what would happen with an ArrayRef (I think it would end up as a dangling pointer). Given that it has just one usage, I don't think this is an issue. Even with multiple usages, I think it'd be fine to declare the variable this way, but that have an accessor which would wrap it in an ArrayRef for easier manipulation. |
clang-tidy: error: 'lldb/Utility/LLDBAssert.h' file not found [clang-diagnostic-error]
not useful