[llvm-dev] Errors linking with LLVM 5.0 - dump() missing

[Daniel Berlin via llvm-dev]

None of these were removed.
lib/IR/AsmWriter.cpp:void Module::dump() const {
lib/IR/AsmWriter.cpp:void Value::dump() const { print(dbgs(),
/*IsForDebug=*/true); dbgs() << '\n'; }
lib/IR/AsmWriter.cpp:void Type::dump() const { print(dbgs(),
/*IsForDebug=*/true); dbgs() << '\n'; }

>It also seems strange that dump() implementation was removed - surely
>it would have been better ti stub it so that client code does not
>break?

LLVM explicitly does not guarantee API compatibility.


On Mon, Sep 25, 2017 at 11:40 AM, Dibyendu Majumdar via llvm-dev <
llvm-dev at lists.llvm.org> wrote:

> Hi,
>
> I am finding that my project that previously successfully built with
> versions 3.5 to 4.0 is now failing to link because of missing
> implementation for dump(). Errors I get are:
>
> Undefined symbols for architecture x86_64:
>
>   "llvm::Type::dump() const", referenced from:
>       ravi::LuaLLVMTypes::dump() in ravi_llvmtypes.cpp.o
>       dump_content(lua_State*) in ravi_llvmluaapi.cpp.o
>   "llvm::Value::dump() const", referenced from:
>       dump_content(lua_State*) in ravi_llvmluaapi.cpp.o
>   "llvm::Module::dump() const", referenced from:
>
> This appears to be a change that is not documented in the release
> notes of 5.0. Please can someone describe what the change is and how I
> can detect whether the dump() implementation is available or not?
>
> It also seems strange that dump() implementation was removed - surely
> it would have been better ti stub it so that client code does not
> break?
>
> Regards
> Dibyendu
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170925/16d71dd7/attachment.html>