search for: rl312926

...command line option determines the style of lld command-line interface when invoked. However, it looks like this option also determines the set of supported targets we are linking for. For example, lld -flavor gnu cannot link mach-o binaries, and could not link PE binaries either (well, not until rL312926). Is this really intended by the design of lld? It looks the flavours are merely legacy compatibility shims, but then why is there no universal lld driver that is able to link binary for any platform using a unified CLI?

...le of lld command-line interface when invoked. > > > > However, it looks like this option also determines the set of supported > targets we are linking for. For example, lld -flavor gnu > > cannot link mach-o binaries, and could not link PE binaries either > (well, not until rL312926). > > > > Is this really intended by the design of lld? It looks the flavours are > merely legacy compatibility shims, but then why is there no > > universal lld driver that is able to link binary for any platform using > a unified CLI? > > ____________________________...

...le of lld command-line interface when invoked. > > > > However, it looks like this option also determines the set of supported > targets we are linking for. For example, lld -flavor gnu > > cannot link mach-o binaries, and could not link PE binaries either > (well, not until rL312926). > > > > Is this really intended by the design of lld? It looks the flavours are > merely legacy compatibility shims, but then why is there no > > universal lld driver that is able to link binary for any platform using > a unified CLI? > > ____________________________...

...yle of lld command-line interface when invoked. >>> >>> However, it looks like this option also determines the set of supported targets we are linking for. For example, lld -flavor gnu >>> cannot link mach-o binaries, and could not link PE binaries either (well, not until rL312926). >>> >>> Is this really intended by the design of lld? It looks the flavours are merely legacy compatibility shims, but then why is there no >>> universal lld driver that is able to link binary for any platform using a unified CLI? >>> __________________________...

...n invoked. > >>>> > >>>> However, it looks like this option also determines the set of > supported targets we are linking for. For example, lld -flavor gnu > >>>> cannot link mach-o binaries, and could not link PE binaries either > (well, not until rL312926). > >>>> > >>>> Is this really intended by the design of lld? It looks the flavours > are merely legacy compatibility shims, but then why is there no > >>>> universal lld driver that is able to link binary for any platform > using a unified CLI? &g...

...> >>>> > > >>>> However, it looks like this option also determines the set of > supported targets we are linking for. For example, lld -flavor gnu > > >>>> cannot link mach-o binaries, and could not link PE binaries either > (well, not until rL312926). > > >>>> > > >>>> Is this really intended by the design of lld? It looks the flavours > are merely legacy compatibility shims, but then why is there no > > >>>> universal lld driver that is able to link binary for any platform > using a...

...>>> > > > >>>> However, it looks like this option also determines the set of > supported targets we are linking for. For example, lld -flavor gnu > > > >>>> cannot link mach-o binaries, and could not link PE binaries > either (well, not until rL312926). > > > >>>> > > > >>>> Is this really intended by the design of lld? It looks the > flavours are merely legacy compatibility shims, but then why is there no > > > >>>> universal lld driver that is able to link binary for any platfor...

...documented. [r312957](http://reviews.llvm.org/rL312957). * clangd gained support for snippet completions. [r313029](http://reviews.llvm.org/rL313029). ## Other project commits * LLD now has a GNU LD-style driver for COFF, to make it easier for MinGW toolchains. [r312926](http://reviews.llvm.org/rL312926). * LLD gained initial support for microMIPS code linking. [r313028](http://reviews.llvm.org/rL313028). * LLDB compatibility with OpenOCD has been improved. [r313442](http://reviews.llvm.org/rL313442).