similar to: Start/end of .text section

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, Though not the correct mailing list for ld.gold Just in case if anyone knows ld.gold --verbose does not dump the linker script like ld.bfd or ld or llvm-ld Any idea? Thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180507/4837c8c0/attachment.html>

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 <

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>

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>

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>

You will want to look at the linkage and/or visibility attributes. On Mon, Apr 23, 2018 at 6:23 PM Sumonto Ghosh via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi > How do I know from a foo.ll (from foo.bc) which function has attribute > "Public" or "External" > > Thanks > _______________________________________________ > LLVM Developers

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, Is there a Stable Release version (release management) of lld or last-know-good? thanks -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180325/90b1ae29/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

On Thu, Aug 24, 2017 at 3:38 PM, Kostya Serebryany <kcc at google.com> wrote: > > > On Thu, Aug 24, 2017 at 3:35 PM, Peter Collingbourne <peter at pcc.me.uk> > wrote: > >> On Thu, Aug 24, 2017 at 3:21 PM, Kostya Serebryany via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> >>> >>> On Thu, Aug 24, 2017 at 3:20

Dean Michael Berris via llvm-dev <llvm-dev at lists.llvm.org> writes: > Just to close this out, I've updated http://reviews.llvm.org/D19904 to use > named ELF groups per-function, and have the runtime library use > __start_xray_instr_map and __stop_xray_instr_map as weak symbols from the > C++ side. In case you're not aware, the __start_/__stop_ trick isn't portable.

On Thu, Aug 24, 2017 at 6:30 PM, Justin Bogner <mail at justinbogner.com> wrote: > Peter Collingbourne <peter at pcc.me.uk> writes: > > On Thu, Aug 24, 2017 at 3:38 PM, Kostya Serebryany <kcc at google.com> > wrote: > > > >> > >> > >> On Thu, Aug 24, 2017 at 3:35 PM, Peter Collingbourne <peter at pcc.me.uk> > >> wrote:

Kostya Serebryany <kcc at google.com> writes: > Justin, > Calling appendToUsed has horrible complexity and if we call it in > every function clang consumes tons of memory (6Gb when compiling one > of the clang's source files). This killed my machine today :) > > The solution is to call appendToUsed once per module, instead of once > per function. Oh right,

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

Just to close this out, I've updated http://reviews.llvm.org/D19904 to use named ELF groups per-function, and have the runtime library use __start_xray_instr_map and __stop_xray_instr_map as weak symbols from the C++ side. I've sent a patch to make creating these COMDAT/Group sections easier when lowering through the MCStreamer interface ( http://reviews.llvm.org/D21743). Cheers On Fri,

On 2020-06-02, Moshtaghi, Alireza wrote: >Sorry for the cryptic code but I had to modify stuff from original >In the following example see the difference when you comment or uncomment the line in the linker script: >============ test.c ============= : >struct orphan_dummy_anno_s { > void (*func)(void); >}; > >static void dummy_export_dbg_log_init_f (void) __attribute__

Hi, I'm going to implement Mach-O support in llvm-objcopy. Before working on this, I'd like to hear your thoughts how llvm-objcopy should handle Mach-O section names. By convention, Mach-O section names are denoted by "<segment name>,<section name>". However, GNU objcopy renames them in the following rule [1]: - If the section name is well-known, rename it to an

Hi, Sorry for delay with reply. It looks like now thunks can be implemented as a synthetic sections. In that case we give flexible solution and will be able to put thunks before/after related sections, using different alignment etc. As far as I know BFD linker uses the same approach at least for MIPS thunks. I will try to implement this idea. On Thu, Sep 8, 2016 at 1:44 AM, Rui Ueyama <ruiu