en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-std-nullptr-t.ll#e29e30b1 [llvm-readobj] Change -long-option to --long-option in tests. NFCWe use both -long-option and --long-option in tests. Switch to --long-option for consistency.In the "llvm-readelf" mode, -long-option is discouraged as it conflicts with grouped short options and it is not accepted by GNU readelf.While updating the tests, change llvm-readobj -s to llvm-readobj -S to reduce confusion ("s" is --section-headers in llvm-readobj but --symbols in llvm-readelf).llvm-svn: 359649 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-std-nullptr-t.ll Wed, 01 May 2019 05:27:20 +0000 Fangrui Song <maskray@google.com> http://172.16.0.5:8080/history/llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-std-nullptr-t.ll#56a5a0c3 [CodeView] Emit the correct TypeIndex for std::nullptr_t.The TypeIndex used by cl.exe is 0x103, which indicates a SimpleTypeModeof NearPointer (note the absence of the bitness, normally pointers use amode of NearPointer32 or NearPointer64) and a SimpleTypeKind of void.So this is basically a void*, but without a specified size, which makessense given how std::nullptr_t is defined.clang-cl was actually not emitting *anything* for this. Instead, when weencountered std::nullptr_t in a DIType, we would actually just emit aTypeIndex of 0, which is obviously wrong.std::nullptr_t in DWARF is represented as a DW_TAG_unspecified_type witha name of "decltype(nullptr)", so we add that logic along with a test,as well as an update to the dumping code so that we no longer printvoid* when dumping 0x103 (which would previously treat Void/NearPointerno differently than Void/NearPointer64).Differential Revision: https://reviews.llvm.org/D53957llvm-svn: 345811 List of files: /llvm-project-15.0.7/llvm/test/DebugInfo/COFF/types-std-nullptr-t.ll Thu, 01 Nov 2018 04:02:41 +0000 Zachary Turner <zturner@google.com>