[LLVMdev] [lld] Diagnostics

[Nick Kledzik]

I think we need a straw man proposal to start iterating on.  Clang’s diagnostics has lots of good features.  But is has lots that a linker does not need.  For instance, the line/column number does not make sense for a linker.  Clang errors/warnings are mostly about the source language which is pretty standard across different platforms.  Other than multiple-defined and undefined errors, most of the linker errors and warnings will be platform specific.  

Linker warnings and errors are also historically very cryptic.  Linker errors usually have a low level cause, and a high level action for the developer to take to resolve the issue.  For instance, the low level trigger would be a particular relocation kind is not expected.  The high level fix is to change the compiler options (e.g. -fno-pic) for a particular file.  It would be nice to capture the low and high level in lld’s diagnostics.  

-Nick


On Oct 7, 2013, at 3:36 PM, Rui Ueyama <ruiu at google.com> wrote:
> I think having diagnostics interface similar to Clang's would be good. I think the total number of defined warnings would be much smaller than Clang.
> 
> On Mon, Oct 7, 2013 at 3:19 PM, Shankar Easwaran <shankare at codeaurora.org> wrote:
> Ping ?
> 
> 
> On 10/4/2013 10:41 PM, Shankar Easwaran wrote:
> Hi,
> 
> lld doesnot have a Diagnostics interface, It uses llvm::errs() to display errors after linking has been done.
> 
> I think the Diagnostics interface follow similiar interface patterns as followed by clang (using Diagnostic td files).
> 
> What do you think ?
> 
> Thanks
> 
> Shankar Easwaran
> 
> 
> 
> -- 
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131007/9c3d1ebb/attachment.html>