search for: 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 co...

...39;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. > > > > I've not got any use of the existing code. Personally I've not come > across anyone wanting this...

...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. >>>> >>>> In general autolinking (https://en.wikipedia.org/wiki/Auto-linking) &...

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. >> >> In general autolinking (https://en.wikipedia.org/wiki/Auto-linking) >> allows developers to spe...

...ote: > Perhaps there's no one clean way to solve this issue, because previously > all libraries and object files are explicitly given to the linker via a > command line and the order of files in the command line matters. That > assumes human intervention to work correctly. Now, the autolinking feature > will add libraries implicitly. Since it's implicit, there will be only one > way how that works, so sometimes that works and sometimes doesn't. > > It feels to me that we should aim for making it work reasonably well for > reasonable use cases. By reasonable use cas...

Are you planning to add support for "-F" and "-framework" to ELF linkers? On Mon, Mar 25, 2019 at 12:51 AM Saleem Abdulrasool via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Sorry for the late chiming in. > > Yes, swift does use autolinking, and I would like to use that on all the > targets. The only target which does not support this functionality > currently are ELF based. That said, I think that `#pragma comment(link, > ...)` is insufficient for my needs. Building Foundation requires framework > style linking as well...

On Sun, Mar 24, 2019 at 9:51 PM Saleem Abdulrasool <compnerd at compnerd.org> wrote: > Sorry for the late chiming in. > > Yes, swift does use autolinking, and I would like to use that on all the > targets. The only target which does not support this functionality > currently are ELF based. That said, I think that `#pragma comment(link, > ...)` is insufficient for my needs. Building Foundation requires framework > style linking as well...

...worried about its use in a malicious manner: `--no-pie` being > embedded into the executable would disable ASLR, which really is why I > think that we would want a subset of options. > I'm not opposed to a linker options scheme; but, I think that it is important to separate this from autolinking (as we have proposed here). Rationale is upthread. We can support both if required. > On Mon, Mar 25, 2019 at 8:47 AM Rui Ueyama <ruiu at google.com> wrote: > >> On Sun, Mar 24, 2019 at 9:51 PM Saleem Abdulrasool <compnerd at compnerd.org> >> wrote: >> >>...

...roposed 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. >> >> In general autolinking (https://en.wikipedia.org/wiki/Auto-linking) >> allows developers to spe...

...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. >>> > >>> >>> I've not got any use of the existing code. Personally I've...

...manner: `--no-pie` being embedded into the executable would disable ASLR, >>> which really is why I think that we would want a subset of options. >>> >> >> I'm not opposed to a linker options scheme; but, I think that it is >> important to separate this from autolinking (as we have proposed here). >> Rationale is upthread. We can support both if required. >> > > I'm not sure I understand how the two are distinct. The linker options > scheme being discussed is in the context of autolinking - aka, how to drive > the autolinking. > I&...

...ages >>>>> 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. >>>>> > >>>>> >>>>> I've not got any use of...

Hi, Is there a way to have markdown automatically convert obvious (http, mailto) URL's to links? i.e: http://example.com -> <a href="http://example.com>http://example.com</a> Thanks, -- http://www.critikart.net

I am trying to do a tutorial improvement on the wiki but I am having some problems with the auto formatting. Using httdp.conf produces http://httpd.conf when filtered. Using *.so produces .so and bold text there after. Is there any shorthand for the user for making text appear as it should without the linking and re-writes? Or does the admin have to change the filters in Instiki? Tesla

Hi, folks. I was wondering if any of you could point me in the right direction. Using R 3.3.3 (and later), on an IBM Power LPAR, Red Hat 7 PPC64le, markdown build fails as below. > install.packages("markdown") trying URL 'https://cloud.r-project.org/src/contrib/markdown_0.8.tar.gz' Content type 'unknown' length 80583 bytes (78 KB)

Hi, This is more of a Ruby question than Rails. I want to autolink url''s in a given string. I''m not great with regular expressions and I wandered if anybody has an example. Thanks.

Hey everybody! -------------- webgen 0.5.11 has just been released! If you don''t know what webgen is, read the "What''s webgen?" section down below. This announcement is also available at http://webgen.rubyforge.org/news/release_0_5_11.html In this release there are two big changes regarding the internals of webgen: 1. The dependency on facets has been removed

I'm trying to add a new option to clang to enable my auto profile pass. I've added this to Options.td and Driver/Tools.cpp, but I'm not getting the option -auto-profile in cc1's invocation. I've checked that the code to push -auto-profile is executed, but if use -v, I don't see -auto-profile in the cc1 invocation. Can anyone point me to some document that explains how to

On 9 June 2015 at 07:55, Manuel Wolfshant <wolfy at nobugconsulting.ro> wrote: > <significant snippage> > > Call me picky but I'd rephrase > The CentOS Project ONLY provides updates or other changes for the > latest version of each major branch. > to > The CentOS Project provides updates or other changes ONLY for the > latest version of each major

Hello all. This is an update to PHP Markdown and PHP Markdown Extra correcting a couple of bugs that got reported since last release. I also decided to enable in this release shortcut-style reference links (as present in Markdown.pl 1.0.2 beta), as most implementations of Markdown accepts them by default. It's also because waiting for John to release officially version 1.0.2 as an