search for: bd1976

Displaying 19 results from an estimated 19 matches for "bd1976".

2019 Mar 27
4
RFC: ELF Autolinking
On Wed, Mar 27, 2019 at 2:03 AM Saleem Abdulrasool <compnerd at compnerd.org> wrote: > On Tue, Mar 26, 2019 at 11:13 AM bd1976 llvm <bd1976llvm at gmail.com> wrote: > >> Thanks Saleem/James. >> >> On Tue, Mar 26, 2019 at 5:15 AM Saleem Abdulrasool <compnerd at compnerd.org> >> wrote: >> >>> Yes, I don't think that supporting all options is entirely possible. >&gt...
2019 Mar 18
2
RFC: ELF Autolinking
On Fri, Mar 15, 2019 at 6:23 AM bd1976 llvm <bd1976llvm at gmail.com> wrote: > > > On Thu, Mar 14, 2019 at 6:43 PM bd1976 llvm <bd1976llvm at gmail.com> wrote: > >> >> >> On Thu, Mar 14, 2019 at 5:58 PM Rui Ueyama <ruiu at google.com> wrote: >> >>> On Thu, Mar 14, 2019 at 9...
2019 Mar 25
3
RFC: ELF Autolinking
...ay from the traditional Unix model, perhaps we can simplify it to > append the command line directives to the end of the command line. > > The other case that is interesting to think about is the autolinking > support in C++ (and clang) modules. > > On Thu, Mar 21, 2019 at 9:49 AM bd1976 llvm <bd1976llvm at gmail.com> wrote: > >> On Thu, Mar 21, 2019 at 12:06 AM Rui Ueyama <ruiu at google.com> wrote: >> >>> Perhaps there's no one clean way to solve this issue, because previously >>> all libraries and object files are explicitly given...
2019 Mar 21
3
RFC: ELF Autolinking
...enough to show that GNU-like linkers could implement this. At this point I will try to prototype this up so that people have an implementation to play with. I am keen to hear from Saleem (compnerd) on this, as he did the original .linker-options work. > > On Tue, Mar 19, 2019 at 11:02 AM bd1976 llvm <bd1976llvm at gmail.com> wrote: > >> On Mon, Mar 18, 2019 at 8:02 PM Rui Ueyama <ruiu at google.com> wrote: >> >>> On Thu, Mar 14, 2019 at 1:05 PM bd1976 llvm via llvm-dev < >>> llvm-dev at lists.llvm.org> wrote: >>> >>>>...
2019 Mar 26
2
RFC: ELF Autolinking
...modules. >>> >> When I started this work I looked at the C++ 20 modules proposal: http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2019/p1103r3.pdf. I didn't see anything about autolinking (or linking at all)! Can you explain more? >>> On Thu, Mar 21, 2019 at 9:49 AM bd1976 llvm <bd1976llvm at gmail.com> >>> wrote: >>> >>>> On Thu, Mar 21, 2019 at 12:06 AM Rui Ueyama <ruiu at google.com> wrote: >>>> >>>>> Perhaps there's no one clean way to solve this issue, because >>>>> previousl...
2019 Mar 25
2
RFC: ELF Autolinking
...ay from the traditional Unix model, perhaps we can simplify it to > append the command line directives to the end of the command line. > > The other case that is interesting to think about is the autolinking > support in C++ (and clang) modules. > > On Thu, Mar 21, 2019 at 9:49 AM bd1976 llvm <bd1976llvm at gmail.com> wrote: > >> On Thu, Mar 21, 2019 at 12:06 AM Rui Ueyama <ruiu at google.com> wrote: >> >>> Perhaps there's no one clean way to solve this issue, because previously >>> all libraries and object files are explicitly given...
2019 Mar 14
2
RFC: ELF Autolinking
On Thu, Mar 14, 2019 at 5:58 PM Rui Ueyama <ruiu at google.com> wrote: > On Thu, Mar 14, 2019 at 9:45 AM bd1976 llvm via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> On Thu, Mar 14, 2019 at 3:32 PM Peter Smith <peter.smith at linaro.org> >> wrote: >> >>> Hello, >>> >>> I've put some comments on the proposal inline. Having to had to de...
2019 Mar 19
2
RFC: ELF Autolinking
On Mon, Mar 18, 2019 at 8:02 PM Rui Ueyama <ruiu at google.com> wrote: > On Thu, Mar 14, 2019 at 1:05 PM bd1976 llvm via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> On Thu, Mar 14, 2019 at 6:27 PM Peter Collingbourne <peter at pcc.me.uk> >> wrote: >> >>> >>> >>> On Thu, Mar 14, 2019 at 6:08 AM bd1976 llvm via llvm-dev < >>> l...
2019 Mar 14
3
RFC: ELF Autolinking
...problems where all the libraries are visible on the > linker command line, I would prefer if people didn't embed difficult > to find directives in object files, but I'm guessing in some languages > this is the natural way of adding libraries. > > On Thu, 14 Mar 2019 at 13:08, bd1976 llvm via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > > > At Sony we offer autolinking as a feature in our ELF toolchain. We would > like to see full support for this feature upstream as there is anecdotal > evidence that it would find use beyond Sony. > > &gt...
2019 Mar 26
4
GSoC19: Improve LLVM binary utilities
(Adding just a bit to Jake's response) On Tue, Mar 26, 2019 at 11:31 AM Jake Ehrlich via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi Seiya, > > What should I prioritize? I suppose that improving llvm-objcopy is the >> most crucial work in this summer. > > > This is an opinion that will vary a lot from person to person. > +1! And don't forget that
2018 Apr 30
0
[RFC] Making .eh_frame more linker-friendly
...ons, larger inputs -> slower result. (I shared both reproduce sets used here: https://drive.google.com/open?id=15tGIypHOATiodxISRCAbg5iiGTBFXAtc).? Best regards, George | Developer | Access Softek, Inc ________________________________ От: George Rimar Отправлено: 28 марта 2018 г. 18:44 Кому: bd1976 llvm Копия: Cary Coutant; llvm-dev at lists.llvm.org; nd at arm.com; llvm-dev-request at lists.llvm.org Тема: Re: [llvm-dev] [RFC] Making .eh_frame more linker-friendly >@Grimar: Did you do any profiling of the code? Were the slowdowns >you were seeing fundamental (i.e. due to IO) or could...
2019 Mar 14
2
RFC: ELF Autolinking
On Thu, Mar 14, 2019 at 6:27 PM Peter Collingbourne <peter at pcc.me.uk> wrote: > > > On Thu, Mar 14, 2019 at 6:08 AM bd1976 llvm via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> At Sony we offer autolinking as a feature in our ELF toolchain. We would >> like to see full support for this feature upstream as there is anecdotal >> evidence that it would find use beyond Sony. >> &...
2018 Mar 28
0
[RFC] Making .eh_frame more linker-friendly
>@Grimar: Did you do any profiling of the code? Were the slowdowns >you were seeing fundamental (i.e. due to IO) or could a more optimal >implementation reduce the slowdown? Did you do any end to end >timings for compilation + link time? No, as far I remember I did not profile this. All results I had were about linker timing for linking clang (posted in this thread). I think the
2019 Mar 14
11
RFC: ELF Autolinking
At Sony we offer autolinking as a feature in our ELF toolchain. We would like to see full support for this feature upstream as there is anecdotal evidence that it would find use beyond Sony. In general autolinking (https://en.wikipedia.org/wiki/Auto-linking) allows developers to specify inputs to the linker in their source code. LLVM and Clang already have support for autolinking on ELF via
2018 Mar 28
2
[RFC] Making .eh_frame more linker-friendly
I am very interested in reviving this. Did anyone get any further with these ideas? @Grimar: Did you do any profiling of the code? Were the slowdowns you were seeing fundamental (i.e. due to IO) or could a more optimal implementation reduce the slowdown? Did you do any end to end timings for compilation + link time? The same issues arise for all metadata sections: .eh_frame
2018 May 31
0
Proposal for address-significance tables for --icf=safe
Hi Peter, This is a great proposal, thanks!. If you were worried about making the abi change have you thought about just going for an array of symbol names or hashes of symbol names where any matching symbol is considered address significant? This would sidestep the problem of keeping the symbol table indices in sync. It would be pessimistic for local symbols if the input SHT_ADDRSIG sections
2019 Mar 14
3
RFC: ELF Autolinking
...s can still be read by the loader even after the section table is stripped from an executable. For the proposed purpose, the note section header would not be useful or meaningful, so a plain section that just contains an ASCII string would be simpler. Reid > > On Thu, Mar 14, 2019 at 6:08 AM bd1976 llvm via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> At Sony we offer autolinking as a feature in our ELF toolchain. We would >> like to see full support for this feature upstream as there is anecdotal >> evidence that it would find use beyond Sony. >> &...
2018 May 22
7
Proposal for address-significance tables for --icf=safe
Hi all, Context: ld.gold has an --icf=safe flag which is intended to apply ICF only to sections which can be safely merged according to the guarantees provided by the language. It works using a set of heuristics (symbol name matching and relocation scanning). That's not only imprecise but it only works with certain languages and is slow due to the need to demangle symbols and scan
2020 Jun 24
2
[Debuginfo][DWARF][LLD] Remove obsolete debug info in lld.
Thanks for copying me in Paul! Sorry, for the late reply. I have had a personal interest in this subject for a long time and I have had discussions on linking DWARF with many of you in person at LLVM events. I don't have much to add to what's upthread and James Henderson has already answered the questions I was copied in for. However, I did want to make a general point about ELF that I