search for: relocatable

Hi, i''m searching to insert a relocatable image into a my plugin, but i don''t want to reimplement what was already done... i saw that in the gallery plugin there''s something like: <img src=\"{relocatable: #{imgname}}\"/> but i wasn''t able to reproduce this behavior.... How can i make this work?...

A Toshiba CB35 Chromebook running Google's stock SeaBIOS reboots after selecting a relocatable kernel from extlinux 6.03. This is a regression caused by commit 8f470e7b movebits: Add syslinux_memmap_find() which factors syslinux_memmap_find() out of bios_boot_linux(). Prior to the refactoring, prot_mode_size was passed as the length in the first call to syslinux_memmap_type(). After...

..._bfd_get_gp_value (input_bfd); rel->r_addend -= _bfd_get_gp_value (output_bfd); But I think we can escape to implement the same adjustments in LLD if we do not support non-zero gp-value in the .reginfo / .MIPS.options sections in input object files. We can get such files if somebody produce a relocatable object file by bfd/gold linkers and attempt to link this file using lld. It seems to be an uncommon case. To notify a user lld might show an error in that case. BTW it looks like there is another problem with relocation addend adjustment in case of relocatable object generation. I did not investig...

I've asked a question in the BioConductor list about package management. My solution depends on your answer to the following question. Are installed R packages "relocatable"? I mean relocatable in the same sense that files in a RedHat RPM file might be "relocatable" after compiling (http://www.rpm.org/max-rpm/ch-rpm-reloc.html). This allows one to build a package as the ordinary user and then the root user can take the result and put it wherever it fi...

> A Toshiba CB35 Chromebook running Google's stock SeaBIOS reboots after > selecting a relocatable kernel from extlinux 6.03. > > This is a regression caused by commit 8f470e7b > movebits: Add syslinux_memmap_find() > > which factors syslinux_memmap_find() out of bios_boot_linux(). Prior to > the refactoring, prot_mode_size was passed as the length in the first call &gt...

...ith a clone of the git repo on kernel.org I run > make spotless bios; make bios > ./bios/extlinux/extlinux -i {target mounted partition} > > The extlinux partition contains both kernels, ldlinux.sys, ldlinux.c32 and > extlinux.conf, which is > PROMPT 1 > LABEL 1 > LINUX {relocatable vmlinuz} > APPEND root={target partition} > LABEL 2 > LINUX {nonrelocatable vmlinuz} > APPEND root={target partition} > > I've heard that the SeaBIOS on these machines may report an incorrect > amount of memory, requiring (at least older versions of) syslinux to &g...

.../ kernels > (versions)? Hi Ady, With a clone of the git repo on kernel.org I run make spotless bios; make bios ./bios/extlinux/extlinux -i {target mounted partition} The extlinux partition contains both kernels, ldlinux.sys, ldlinux.c32 and extlinux.conf, which is PROMPT 1 LABEL 1 LINUX {relocatable vmlinuz} APPEND root={target partition} LABEL 2 LINUX {nonrelocatable vmlinuz} APPEND root={target partition} I've heard that the SeaBIOS on these machines may report an incorrect amount of memory, requiring (at least older versions of) syslinux to use/pass "mem=1500m" or som...

...et of 0 so the addends need updating. So I think the two > approaches are equivalent. > > Have I misunderstood? > > Peter > > On 27 September 2016 at 08:28, Simon Atanasyan via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> Hi, >> >> Now in case of relocatable object generation LLD merges and copies >> REL/RELA sections as is and does not touch any addends. But it is >> incorrect. If we have a relocation which targets a section, we have to >> adjust the relocation's addend to take in account that the section >> might be merged...

Hi, Now in case of relocatable object generation LLD merges and copies REL/RELA sections as is and does not touch any addends. But it is incorrect. If we have a relocation which targets a section, we have to adjust the relocation's addend to take in account that the section might be merged with other ones. Here is the repro...

...age and zImage files > _ memdisk > _ grldr, plop(bm)... > _ memtest (and alternatives), DBAN, several hardware testers... > _ gPXE/iPXE... > _ Older kernels and/or kernels for older machines (e.g. PuppyLinux and > family and derivatives; I could mention several others) > _ Non-relocatable and relocatable kernels > _ Linux kernels prior to version 3.3 and/or with similar "older > (EFISTUB) standards", "supposedly" bootable in BIOS and/or (U)EFI > systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL > 6.x / 7 ) > _ BIOS and/or (U...

...he application I'm working on because a) a single thread > manages all compilations sequentially, and b) the compiled methods > don't make direct calls to other methods (so stubs will never be > generated). > > What I need to know is, is the native code generated by LLVM > relocatable such that it could be copied to another location in memory > like this?  Also, does LLVM do anything to the native code after it is > first emitted?  Does it try rewriting it, for example? That's a good question, and I wish I knew the answer, because if that were the case the entire memo...

...namicNoPIC and > full PIC ? >From TargetMachine.cpp (actually this is show in llc --help): cl::values( clEnumValN(Reloc::Default, "default", "Target default relocation model"), clEnumValN(Reloc::Static, "static", "Non-relocatable code"), clEnumValN(Reloc::PIC_, "pic", "Fully relocatable, position independent code"), clEnumValN(Reloc::DynamicNoPIC, "dynamic-no-pic", "Relocatable external references, non-relocatable code"), clEnumValEnd));...

This example generates the following error: .Ltmp3: .Ltmp5: .Ltmp13: .word (.Ltmp5-.Ltmp3)-.Ltmp13 ./llvm-mc ex.s -filetype=obj LLVM ERROR: expected relocatable expression when using: -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation

....org > <mailto:sidneym at codeaurora.org>> wrote: > > > This example generates the following error: > .Ltmp3: > .Ltmp5: > .Ltmp13: > .word (.Ltmp5-.Ltmp3)-.Ltmp13 > > ./llvm-mc ex.s -filetype=obj > LLVM ERROR: expected relocatable expression when using: > > > Umm, isn't this equivalent to the following? What do you expect LLVM to > do with it? > > .Ltmp13: > .word -.Ltmp13 I removed the target specific assembly to produce a simple generic example. It was derived from eh_frame code the compil...

...ut it might be possible for the application I'm working on because a) a single thread manages all compilations sequentially, and b) the compiled methods don't make direct calls to other methods (so stubs will never be generated). What I need to know is, is the native code generated by LLVM relocatable such that it could be copied to another location in memory like this? Also, does LLVM do anything to the native code after it is first emitted? Does it try rewriting it, for example? Cheers, Gary -- http://gbenson.net/

...nxboot.img initrd=core.img) _ bzImage and zImage files _ memdisk _ grldr, plop(bm)... _ memtest (and alternatives), DBAN, several hardware testers... _ gPXE/iPXE... _ Older kernels and/or kernels for older machines (e.g. PuppyLinux and family and derivatives; I could mention several others) _ Non-relocatable and relocatable kernels _ Linux kernels prior to version 3.3 and/or with similar "older (EFISTUB) standards", "supposedly" bootable in BIOS and/or (U)EFI systems at the time (e.g. Slackware 14.0 / 14.1, Debian 7 Wheezy, RHEL 6.x / 7 ) _ BIOS and/or (U)EFI systems As a remain...

...ackware-14/%5Bann%5D-syslinux-6-03-has-been-released-4175521209/#post5270515 leaded to this message: "Cannot relocate kernel, bailing out" That leaded me to this post in the ML: http://www.zytor.com/pipermail/syslinux-commits/2013-July/002381.html The kernel in the image file being not relocatable. I'll replace it with one with CONFIG_RELOCATABLE=Y to confirm the issue. But meanwhile, is there some other thing I can do, like moving the kernel elsewhere in the image? Currently the tree is: . |-- EFI | `-- BOOT | |-- bootx64.efi | |-- bzImage | |-- f2.txt | |-- initrd.img | |-- ldlinux....

...mp of section 'somedata': NOTE: This section has relocations against it, but these have NOT been applied to this dump. 0x00000000 64003c00 28000000 d.<.(... ^^^^ (Calculated properly too!) With clang/llvm-mc $ llvm-mc -filetype=obj x.s -o x.o LLVM ERROR: expected relocatable expression Looks like llvm-mc is more restrictive ? Thanks Shankar Easwaran -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/...

...-released-4175521209/#post5270515 > > leaded to this message: > > "Cannot relocate kernel, bailing out" > > That leaded me to this post in the ML: > http://www.zytor.com/pipermail/syslinux-commits/2013-July/002381.html > > The kernel in the image file being not relocatable. I'll replace it > with one with > CONFIG_RELOCATABLE=Y to confirm the issue. With CONFIG_RELOCATABLE=Y (only change to the kernel) the installer bow boots OK, > But meanwhile, is there some other thing I can do, like moving the > kernel elsewhere in the image? Stupid idea, of cou...

On Sat, 7 Feb 2015, Ady via Syslinux wrote: > Thank you for this meaningful report. Ideally, I would suggest > performing a similar test (at least with the same kernel built with all > the above "config_*=y" settings) with official pre-built Syslinux > versions 4.07 and 3.86 (remembering that all Syslinux-related files, > including c32 modules, if being used, shall