search for: mlinker

I'm seeing something similar. clang is using HOST_LINK_VERSION, obtained from ld64, as the default for -mlinker-version. This causes Darwin.cpp to add the arguments you are seeing, but not handled by lld. Perhaps -fuse-ld should be considered in addition to -mlinker-version when adding these arguments. As a workaround, you can try passing -mlinker-version. Looks like anything < 133 will work, includin...

...end that you use ld64 if you are intending to build MachO binaries. > On Jan 7, 2018, at 9:57 AM, Don Hinton via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > I'm seeing something similar. > > clang is using HOST_LINK_VERSION, obtained from ld64, as the default for -mlinker-version. This causes Darwin.cpp to add the arguments you are seeing, but not handled by lld. Perhaps -fuse-ld should be considered in addition to -mlinker-version when adding these arguments. > > As a workaround, you can try passing -mlinker-version. Looks like anything < 133 will work...

Looking at tools/clang/lib/Driver/Tools.cpp , there's this fragment of code: if (Args.hasArg(options::OPT_rdynamic) && Version[0] >= 137) CmdArgs.push_back("-export_dynamic"); I built LLVM 3.4.2 from a OS X 10.11 "El Capitan" but specifying a fat build (386+x86_64) and requesting support back up to 10.6. It went fine, and the build passes all tests when run

Hi. I'm using LLVM 5.0.1 on macOS 10.12. I have a very simple program (program.c): int main() {} When attempting to compile with LLD, I get this output: $ clang -fuse-ld=lld program.c /opt/llvm/5.0.1/bin/ld.lld: error: unknown argument: -no_deduplicate /opt/llvm/5.0.1/bin/ld.lld: error: unknown argument: -dynamic /opt/llvm/5.0.1/bin/ld.lld: error: unknown argument: -arch

...reworked, because then adding the section sounds much nicer. > > Wouldn't a special section type trigger an "unrecognized section type" error for linkers that don't support it? Yeah, that is possible. Compatibility problem exists with ld64, and are handled by means of `-mlinker-version`. I don’t know how others feel about bringing that flag over to other platforms. We could force the use of a new section and bring along `-mlinker-version` and base it on that or silently drop the flags (sounds slightly unexpected). Or we could abuse the notes and not have to worry about...

...lection for .gcc_except_table >From the review: jhenderson said: "This looks reasonable to me, but I don't know the surrounding code well enough to be comfortable LGTM-ing it. Sorry!" pcc said: "I agree with @MaskRay that this should be a binutils-specific option. The flag -mlinker-version seems to have been designed around macOS-specific assumptions i.e. there is a single linker (ld64) and that the linker and assembler are not version coupled. Having this option be binutils-specific seems like the best way to reflect the binutils-specific requirements." Both responses...

On Jan 6, 2018 12:05 PM, "Saleem Abdulrasool via llvm-dev" < llvm-dev at lists.llvm.org> wrote: On Jan 5, 2018, at 4:35 PM, Cary Coutant <ccoutant at gmail.com> wrote: In general I'm in favor of the proposal. Defining a generic way to convey some information from the compiler to the linker is useful, and it looks like it is just a historical reason that the ELF lacks

> On Jan 5, 2018, at 4:35 PM, Cary Coutant <ccoutant at gmail.com> wrote: > >>> In general I'm in favor of the proposal. Defining a generic way to convey >>> some information from the compiler to the linker is useful, and it looks >>> like it is just a historical reason that the ELF lacks the feature at the >>> moment. >>> >>>

In short: Perhaps we should switch lld to the bfd-style tombstoning behavior for a release or two, letting users opt-in to testing with the new -1/-2 tombstoning in the interim, before switching to the new tombstone by default (while still having the flag to switch back when users find surprise places that can't handle the new behavior). In long: https://reviews.llvm.org/D81784 and follow-on

...ermail/binutils/2020- >July/112415.html ). >> We may need a way to tell codegen about the used linker. >> >> pcc proposed -mbinutils-version= - This is nice in that some MC >> decisions related to -fno-integrated-as can use this option as well. >> jyknight proposed -mlinker-version= and syntax like -fuse-ld=bfd:2.34 >> >> This may get more complex if the generated object file want to be linked >> with more than one linker. This discussion probably deserves its own >> thread.     -- Alexey Lapshin   -------------- next part -------------- An HTM...

...> >> We may need a way to tell codegen about the used linker. > > >> > > >> pcc proposed -mbinutils-version= - This is nice in that some MC > > >> decisions related to -fno-integrated-as can use this option as well. > > >> jyknight proposed -mlinker-version= and syntax like -fuse-ld=bfd:2.34 > > >> > > >> This may get more complex if the generated object file want to be linked > > >> with more than one linker. This discussion probably deserves its own > > >> thread. > > > > > >...

...;July/112415.html ). > >> We may need a way to tell codegen about the used linker. > >> > >> pcc proposed -mbinutils-version= - This is nice in that some MC > >> decisions related to -fno-integrated-as can use this option as well. > >> jyknight proposed -mlinker-version= and syntax like -fuse-ld=bfd:2.34 > >> > >> This may get more complex if the generated object file want to be linked > >> with more than one linker. This discussion probably deserves its own > >> thread. > > > -- > Alexey Lapshin > _______...

...gen about the used linker. > > > > >> > > > > >> pcc proposed -mbinutils-version= - This is nice in that some MC > > > > >> decisions related to -fno-integrated-as can use this option as > well. > > > > >> jyknight proposed -mlinker-version= and syntax like > -fuse-ld=bfd:2.34 > > > > >> > > > > >> This may get more complex if the generated object file want to be > linked > > > > >> with more than one linker. This discussion probably deserves its > own > > &g...

...>>> > > > >> >>> > > > >> pcc proposed -mbinutils-version= - This is nice in that some MC >>> > > > >> decisions related to -fno-integrated-as can use this option as well. >>> > > > >> jyknight proposed -mlinker-version= and syntax like -fuse-ld=bfd:2.34 >>> > > > >> >>> > > > >> This may get more complex if the generated object file want to be linked >>> > > > >> with more than one linker. This discussion probably deserves its own &gt...

...; > >>> > > > >> pcc proposed -mbinutils-version= - This is nice in that > some MC > > >>> > > > >> decisions related to -fno-integrated-as can use this option > as well. > > >>> > > > >> jyknight proposed -mlinker-version= and syntax like > -fuse-ld=bfd:2.34 > > >>> > > > >> > > >>> > > > >> This may get more complex if the generated object file want > to be linked > > >>> > > > >> with more than one linker. This...

...t; > > >> > >>> > > > >> pcc proposed -mbinutils-version= - This is nice in that some MC > >>> > > > >> decisions related to -fno-integrated-as can use this option as well. > >>> > > > >> jyknight proposed -mlinker-version= and syntax like -fuse-ld=bfd:2.34 > >>> > > > >> > >>> > > > >> This may get more complex if the generated object file want to be linked > >>> > > > >> with more than one linker. This discussion probably deser...

...gt; > >>> > > > >> pcc proposed -mbinutils-version= - This is nice in that some MC >> > >>> > > > >> decisions related to -fno-integrated-as can use this option as well. >> > >>> > > > >> jyknight proposed -mlinker-version= and syntax like -fuse-ld=bfd:2.34 >> > >>> > > > >> >> > >>> > > > >> This may get more complex if the generated object file want to be linked >> > >>> > > > >> with more than one linker. Thi...

...>> pcc proposed -mbinutils-version= - This is nice in that >> some MC >> >> > >>> > > > >> decisions related to -fno-integrated-as can use this >> option as well. >> >> > >>> > > > >> jyknight proposed -mlinker-version= and syntax like >> -fuse-ld=bfd:2.34 >> >> > >>> > > > >> >> >> > >>> > > > >> This may get more complex if the generated object file >> want to be linked >> >> > >>> > >...

...rsion= - This is nice in that >> >> some MC >> >> >> > >>> > > > >> decisions related to -fno-integrated-as can use this >> >> option as well. >> >> >> > >>> > > > >> jyknight proposed -mlinker-version= and syntax like >> >> -fuse-ld=bfd:2.34 >> >> >> > >>> > > > >> >> >> >> > >>> > > > >> This may get more complex if the generated object file >> >> want to be linked >>...

...>> >> some MC > > >> >> >> > >>> > > > >> decisions related to -fno-integrated-as can use this > > >> >> option as well. > > >> >> >> > >>> > > > >> jyknight proposed -mlinker-version= and syntax like > > >> >> -fuse-ld=bfd:2.34 > > >> >> >> > >>> > > > >> > > >> >> >> > >>> > > > >> This may get more complex if the generated object file > > >&...