similar to: lld stable release

Thanks Rafael, wondering as of what is the level of support for ARM and is it close to production quality? Thanks On Mon, Feb 26, 2018 at 2:06 PM, Rafael Avila de Espindola < rafael.espindola at gmail.com> wrote: > Not sure there is an official POC, you are probably better off asking > whatever question you have directly on the list. > > Cheers, > Rafael > > Sumonto

I think ARM ELF is pretty good. I was able to link clang with it some time ago and it now has support for thunks. Cheers, Rafael Sumonto Ghosh <sumonto.ghosh at gmail.com> writes: > Thanks Rafael, wondering as of what is the level of support for ARM and is > it close to production quality? > > Thanks > > On Mon, Feb 26, 2018 at 2:06 PM, Rafael Avila de Espindola <

Is there a regression bot with a list of tests or alike Thanks On Mon, Feb 26, 2018 at 4:19 PM Rafael Avila de Espindola < rafael.espindola at gmail.com> wrote: > I think ARM ELF is pretty good. I was able to link clang with it some > time ago and it now has support for thunks. > > Cheers, > Rafael > > > Sumonto Ghosh <sumonto.ghosh at gmail.com> writes: >

Hi, Could someone please connect me to the POC for ARM support on LLD Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180226/828ef332/attachment.html>

Not sure there is an official POC, you are probably better off asking whatever question you have directly on the list. Cheers, Rafael Sumonto Ghosh via llvm-dev <llvm-dev at lists.llvm.org> writes: > Hi, > Could someone please connect me to the POC for ARM support on LLD > > > Thanks > _______________________________________________ > LLVM Developers mailing list >

Hi While cross compiling on Mac Host: Mac Target: Linux on ArmV7 How can I force clang to use the non-system linker But use llvm-lld (i.e. ld.lld) or any other non standard linker Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180326/d86e1601/attachment.html>

Yeah, it seems that the time the mirror was created there were no release branches and therefore nothing was exported :) On Fri, Nov 20, 2015 at 8:13 PM, Hans Wennborg <hans at chromium.org> wrote: > On Thu, Nov 19, 2015 at 2:38 PM, Martell Malone via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi All, >> >> I am currently trying to test out a few things

Hello Sumonto, There are several upstream build bots that run the Arm specific LLD tests. You can find these tests in the lld/test/ELF directory, they all start with arm. At Linaro we are planning to set up a build-bot, modelled on the equivalent AArch64 one that does a 2 stage build of clang with LLD as the linker, this will also include running the test suite. For the ELF port; the major Arm

Hi All, I am currently trying to test out a few things with the 3.7branch and i noticed that lld git mirror does not contain the branches like the other repositories. If anyone knows who I should ping to fix this please CC them. Kind Regards Martell -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, Is there a way to retrieve the start/end of .text section (at runtime) without having to add additional PROVIDE() variables to the linker script? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180508/db4636fc/attachment.html>

The option -fuse-ld is the closest option that I can think of. In its most common form it accepts bfd, gold or lld, clang will then invoke ld.bfd, ld.gold or ld.lld respectively. On many systems ld is a symlink to an executable of the form ld.suffix. Alternatively the full path to the linker can be given -fuse-ld=/full/path/to/linker/executable Peter On 27 March 2018 at 00:40, Sumonto Ghosh via

+Rui and Peter On Wed, Jul 25, 2018 at 8:34 AM, Andrew Kelley via llvm-dev <llvm-dev at lists.llvm.org> wrote: > Here's a fix: > > --- a/lld/COFF/Driver.cpp > +++ b/lld/COFF/Driver.cpp > @@ -72,6 +72,9 @@ bool link(ArrayRef<const char *> Args, bool CanExitEarly, > raw_ostream &Diag) { > exitLld(errorCount() ? 1 : 0); > > freeArena(); > +

Hi How do I know from a foo.ll (from foo.bc) which function has attribute "Public" or "External" Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180423/e4f0ae18/attachment.html>

LLD got its own release notes document earlier this year, but it's almost empty. They have a note about initial support for LTO and some MIPS stuff (which are also mentioned in LLVM's release notes). Is there something that should be added to the notes, can they be fleshed out a bit, should we drop them as they're almost empty, or ship as-is? Cheers, Hans

I see in that code review page that LLD is built in the test-release script. Happy to see that. Now I'm thinking about package maintainers such as Debian, and hoping that they will pick up LLD and make it available with this next release. What is different about this release that will clue Debian developers and other package managers that they should include LLD with this release? How can we

On 4 February 2017 at 02:58, Sean Silva via llvm-dev <llvm-dev at lists.llvm.org> wrote: > I think that LLD is going to be included in the 4.0 release. At least, we've > been cherry-picking fixes into the release branch. I've CC'd some others > that will know the details. The test-release.sh script still doesn't have it and I believe it's just because we never

On Fri, Oct 28, 2016 at 9:17 AM, Renato Golin via cfe-dev <cfe-dev at lists.llvm.org> wrote: > I'm creating a bootstrap buildbot on AArch64 with LLD and I just > realised the "accepted" way to make clang call lld is to "symlink lld > -> ld". I understand that's how every Linux system "chooses" the > linker, but that makes deployment and

On 28 October 2016 at 16:54, Renato Golin via llvm-dev <llvm-dev at lists.llvm.org> wrote: > On 28 October 2016 at 17:41, Hans Wennborg <hans at chromium.org> wrote: >> There's also -fuse-ld= >> >> That's how I usually do it. > > Right, that gets rid of the override flag. Thanks! :) > > But the arguments about the default and the

Dear everyone, It's time for the release notes nagging email. We have release notes for LLVM, Clang, clang-tools-extra, lld, and Polly. (If there are more, please let me know.) Most of these are pretty empty files; see e.g. the LLVM one at [1]. The internet does read these notes when we release, so please help make them informative! If you made any interesting changes during the past six

As a front end developer I would like to start experimenting with using LLD for a linker, especially because I could cross-compile without requiring the target's system linker being installed. However, currently it is not straightforward to depend on LLD, because it is not by default included in LLVM releases, and this means that it is absent from the various package managers. If users were