Displaying 3 results from an estimated 3 matches for "unkown_reloc".
Did you mean:
uknown_reloc
2012 Jun 19
2
[LLVMdev] object construction patterns and unique_ptr
...error_category : public llvm::_do_message {
> public:
> virtual std::string message(int ev) const {
> ...
> case uknown_reloc:
> return "uknown relocation % at %";
> ...
> }
> };
>
> // In the reader.
>
> setError(make_pair(blah_error::unkown_reloc,
> vector<string>{relocationumer, loc})); // loc could be calculated by
> backtracking, or just the current file address. (we could even pass
> the address as a stop address to obj2yaml).
>
> // Someplace else.
>
> if (File->error())
> o << File->getErro...
2012 Jun 18
0
[LLVMdev] object construction patterns and unique_ptr
...as:
// In the error_category stuff
class blah_reader_error_category : public llvm::_do_message {
public:
virtual std::string message(int ev) const {
...
case uknown_reloc:
return "uknown relocation % at %";
...
}
};
// In the reader.
setError(make_pair(blah_error::unkown_reloc,
vector<string>{relocationumer, loc})); // loc could be calculated by
backtracking, or just the current file address. (we could even pass
the address as a stop address to obj2yaml).
// Someplace else.
if (File->error())
o << File->getErrorMessage();
Which would do the string...
2012 Jun 18
6
[LLVMdev] object construction patterns and unique_ptr
On Jun 16, 2012, at 3:51 PM, Chris Lattner wrote:
> On Jun 15, 2012, at 3:48 PM, Nick Kledzik wrote:
>
>> In lld we have a Reader class which is a factory that takes .o file(s) and produces an in memory lld::File object(s). But in doing so, there could be I/O errors (file not readable) or file may be malformed. We are also using C++11 in lld, so we use std::unique_ptr for managing