search for: libbar

...>>> If we want this to be compatible with GNU linkers, doesn't the >>> autolinked input need to appear at the point immediately after the object >>> file appears in the link? I'm imagining the case where you have a >>> statically linked libc as well as a libbar.a autolinked from a foo.o. The >>> link command line would look like this: >>> >>> ld foo.o -lc >>> >>> Now foo.o autolinks against bar. The command line becomes: >>> >>> ld foo.o -lc -lbar >>> >> >> Actually, I was...

...ries.cpp I still don't have a good solution to the problem of -L paths that include bytecode versions of the native libraries we're trying to link. Consider the following situation... A directory in our -L path has a libFoo.so native library that we need to link. It also contains a libBar.so bytecode library. Another directory in our -L path has a bytecode version of libFoo.so and a native version of libBar.so. What do we do? llvm-g++ -Wl,-native -shared -o libtest.so test.o -L/foobar -lfoo -L/barfoo -lbar /foobar libFoo.so --native libBar.so --bytecode /barfoo libFo...

...this to be compatible with GNU linkers, doesn't the >>>>> autolinked input need to appear at the point immediately after the object >>>>> file appears in the link? I'm imagining the case where you have a >>>>> statically linked libc as well as a libbar.a autolinked from a foo.o. The >>>>> link command line would look like this: >>>>> >>>>> ld foo.o -lc >>>>> >>>>> Now foo.o autolinks against bar. The command line becomes: >>>>> >>>>> ld foo.o...

...ith GNU linkers, doesn't the >>>>>>> autolinked input need to appear at the point immediately after the object >>>>>>> file appears in the link? I'm imagining the case where you have a >>>>>>> statically linked libc as well as a libbar.a autolinked from a foo.o. The >>>>>>> link command line would look like this: >>>>>>> >>>>>>> ld foo.o -lc >>>>>>> >>>>>>> Now foo.o autolinks against bar. The command line becomes: >>&gt...

...ith GNU linkers, doesn't the >>>>>>> autolinked input need to appear at the point immediately after the object >>>>>>> file appears in the link? I'm imagining the case where you have a >>>>>>> statically linked libc as well as a libbar.a autolinked from a foo.o. The >>>>>>> link command line would look like this: >>>>>>> >>>>>>> ld foo.o -lc >>>>>>> >>>>>>> Now foo.o autolinks against bar. The command line becomes: >>&gt...

...>> symbols. >> > > If we want this to be compatible with GNU linkers, doesn't the autolinked > input need to appear at the point immediately after the object file appears > in the link? I'm imagining the case where you have a statically linked libc > as well as a libbar.a autolinked from a foo.o. The link command line would > look like this: > > ld foo.o -lc > > Now foo.o autolinks against bar. The command line becomes: > > ld foo.o -lc -lbar > Actually, I was thinking that on a GNU linker the command line would become "ld foo.o -lc -...

...39;t the >>>>>>>>> autolinked input need to appear at the point immediately after the object >>>>>>>>> file appears in the link? I'm imagining the case where you have a >>>>>>>>> statically linked libc as well as a libbar.a autolinked from a foo.o. The >>>>>>>>> link command line would look like this: >>>>>>>>> >>>>>>>>> ld foo.o -lc >>>>>>>>> >>>>>>>>> Now foo.o autolinks against ba...

...;>>>>>>> autolinked input need to appear at the point immediately after the object >>>>>>>>>>> file appears in the link? I'm imagining the case where you have a >>>>>>>>>>> statically linked libc as well as a libbar.a autolinked from a foo.o. The >>>>>>>>>>> link command line would look like this: >>>>>>>>>>> >>>>>>>>>>> ld foo.o -lc >>>>>>>>>>> >>>>>>>>&gt...

...# works this time and everything is fine But, if restart my R session and do it "right" the second time there is a surprise: library(bar) dyn.load('foo.so') # fails library(bar) # just to be sure? dyn.load('foo.so) # fails again dyn.load('/usr/local/lib64/library/bar/lib/libbar.so') # just to be really sure? dyn.load('foo.so') In other words, it is possible to load foo.so, but only after a failed attempt. If I remember to load the required package bar I cannot load the depenent library foo.so. Any ideas? Thanks, Dominick [[alternative HTML version deleted...

> Yes, this is no problem. You can do something like > this: > > $ llvmgcc X.c -c -o X.bc > $ llc X.bc -o X.s > $ gcc Y.c -o Y.o -c > $ gcc X.s Y.o -o program > $ ./program Ok, fine, and what about the interpreter? It takes 100% llvm, doesn't it? Or is there some kind of import facility (perhaps as an specially interpreted call or as an extension to llvm which makes

...the list unresolved symbols. For example: foo.c: int main(void) { return bar() } bar.c: int bar() { return 123; } In the native case, you have three options to link these files. 1. Classic static linking: $ clang foo.c bar.c 2. Static linking with the archive. $ clang -c bar.c $ ar q libbar.a bar.o $ clang foo.c -lbar -L. 3. Dynamic linking: $ clang -c foo.c $ clang -shared bar.c -o libbar.so $ clang foo.c -lbar -L. $ nm a.out ... U bar ... ========================================== Currently, lib/Linker supports first two cases, but not the third. I would like to be able add thi...

...kages are for arch={i386,amd64,armhf}. They are not for > arch={stubdom-i386,stubdom-amd64} and there is no such arch in Debian (nor > CentOS nor Fedora I expect). > > For the qemu source package to be able build a runnable qemu-xenpv binary > it would need to get all the libFOO and libBAR which qemu needs from > somewhere, and they would need to be built for the stubdom-{i386,amd64} > arches, not for i386 or amd64. All the builddeps for qemu-pv need to come > from somewhere and the existing i386 or amd64 libraries do not satisfy the > build dep for a pv stubdom. > &g...

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

...t; @@ -1,5 +1,5 @@ > SUBDIRS = bar bus bios clock devinit fb fuse gpio i2c ibus instmem \ > - ltc mc mxm pwr therm timer vm volt > + ltc mc mxm pwr therm timer vm volt dvfs > > noinst_LTLIBRARIES = libsubdev.la > > @@ -22,4 +22,5 @@ libsubdev_la_LIBADD = bar/libbar.la \ > therm/libtherm.la \ > timer/libtimer.la \ > vm/libvm.la \ > - volt/libvolt.la > + volt/libvolt.la \ > + dvfs/dvfs.la > diff --git a/n...

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 debug > library selection 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

...lock devinit fb fuse gpio i2c ibus instmem \ >>> - ltc mc mxm pwr therm timer vm volt >>> + ltc mc mxm pwr therm timer vm volt dvfs >>> >>> noinst_LTLIBRARIES = libsubdev.la >>> >>> @@ -22,4 +22,5 @@ libsubdev_la_LIBADD = bar/libbar.la \ >>> therm/libtherm.la \ >>> timer/libtimer.la \ >>> vm/libvm.la \ >>> - volt/libvolt.la >>> + volt/libvolt.la \ >>> +...

Hi, This is a try to have some simple DVFS (Dynamic Voltage and Frequency Scaling) support for GK20A. Instead of relying on other existing frequency scaling framework, we create a simple subdev in Nouveau for the same purpose. That's because we don't want to make the DVFS implementation for GK20A far more than enough in the beginning and hinder the implementation for dGPU in the future.

...; autolinked inputs. OTOH why not allow command line options to affect the autolinked inputs? It gives developers some more control at no cost (apart form the possible confusion). > > The other option is to handle autolinked libraries as soon as we find > them, so that if foo.o autolinks libbar, the linker would act as if foo.o > in the command line is followed by -lbar. I'd think that's not too bad or > arguably more straightforward semantics than autolinking everything all at > once at the end. > So I played around with this idea a bit. Some background info: MSVC s...

...dev/Makefile.am +++ b/nvkm/subdev/Makefile.am @@ -1,5 +1,5 @@ SUBDIRS = bar bus bios clock devinit fb fuse gpio i2c ibus instmem \ - ltc mc mxm pwr therm timer vm volt + ltc mc mxm pwr therm timer vm volt dvfs noinst_LTLIBRARIES = libsubdev.la @@ -22,4 +22,5 @@ libsubdev_la_LIBADD = bar/libbar.la \ therm/libtherm.la \ timer/libtimer.la \ vm/libvm.la \ - volt/libvolt.la + volt/libvolt.la \ + dvfs/dvfs.la diff --git a/nvkm/subdev/dvfs/Makefile.am b/nvkm/subdev/dvfs/Makefile.am new file mode 100644 index 000000000000..c09d4ec4124d --- /dev/null +++ b/nvkm/subdev/dvfs/Makef...

...SUBDIRS = bar bus bios clock devinit fb fuse gpio i2c ibus instmem \ >> - ltc mc mxm pwr therm timer vm volt >> + ltc mc mxm pwr therm timer vm volt dvfs >> >> noinst_LTLIBRARIES = libsubdev.la >> >> @@ -22,4 +22,5 @@ libsubdev_la_LIBADD = bar/libbar.la \ >> therm/libtherm.la \ >> timer/libtimer.la \ >> vm/libvm.la \ >> - volt/libvolt.la >> + volt/libvolt.la \ >> + dvfs/...