search for: addressrang

...>> + // an offset to the CIE (provided by parsing the FDE header). The CIE itself >> + // is obtained lazily once it's actually required. >> + FDE(DataExtractor D, uint64_t Offset, uint64_t Length, int64_t LinkedCIEOffset, >> + uint64_t InitialLocation, uint64_t AddressRange) >> + : FrameEntry(FK_FDE, D, Offset, Length), LinkedCIEOffset(LinkedCIEOffset), >> + InitialLocation(InitialLocation), AddressRange(AddressRange), >> + LinkedCIE(NULL) >> + {} >> + >> + void dumpHeader(raw_ostream &OS) const { >> + OS &...

..."\\/", 3)); "/\/\/\7\/\/\/" 7) Compilation failures if the type cannot be formatted. struct Foo {}; outs() << "{0}"_fmt.stream(Foo{}); // compilation failure. 8) Extensible format provider mechanism to allow formatting of your own types. struct AddressRange { uint64_t Begin; uint64_t End; } template<> class format_provider<AddressRange> { public: static void format(const AddressRange &R, raw_ostream &S, StringRef Style) { S << "[{0:X} - {1:X}]"_fmt.stream(R.begin(), R.end()); }...

On 12.10.2016 05:59, Mehdi Amini via llvm-dev wrote: >> If you change a const char * to a StringRef, it can silently succeed >> while passing your StringRef object to printf. It should fail to compile! > > llvm::format now fails to compile as well :) > > However this does not address other issues, like: `format(“%d”, float_var)` This may be a good time to point at

...ion) [0x97cb7] 1 _objc_msgSend + 31 (in libobjc.A.dylib) [0x9029368f] 1 -[VMUStabsExtractor readStabsFromMachOHeader:nsyms:nlist:stringTable:] + 3293 (in Symbolication) [0x9e4f7] 1 +[VMUSymbol symbolWithName:mangledName:addressRange:owner:flags:] + 63 (in Symbolication) [0x9f18b] 1 +[NSObject alloc] + 42 (in CoreFoundation) [0x942c0b4a] 1 +[NSObject allocWithZone:] + 156 (in CoreFoundation) [0x942c0bec] 1 __internal_class_createIns...