similar to: [LLVMdev] [lld] Current ways to position memory sections (e.g. .text, .data, .bss) with lld?

Hi Ed, I wrote http://reviews.llvm.org/D10952 to address your last problem. There is also the related http://reviews.llvm.org/D10918 by Denis to address how you can directly assign sections to segments in the script. Both are in code review. Rafael auelr On Fri, Jul 3, 2015 at 12:29 AM, Rafael Auler <rafaelauler at gmail.com> wrote: > Hi Ed, > > It looks like lld is failing at

Hi Rui, Shankar, Do we really need empty TargetLayout class? No we have the following hierarchy: Layout <- DefaultLayout<> <- TargetLayout<> <- xxxTargetLayout<> I suggest to remove TargetLayout and rename DefaultLayout to TargetLayout. Thoughts? -- Simon Atanasyan

Good point. But I suggest to do that by two steps. First, remove TargetLayout and rename DefaultLayout to TargetLayout. Second, merge TargetLayout and Layout. The first step is easy, the second step generates large diff, requires reviewing etc. On Fri, Apr 3, 2015 at 10:40 PM, Rui Ueyama <ruiu at google.com> wrote: > I'm wondering if we even need TargetLayout. > > DefaultLayout

Thanks Nick. I've been pursuing Gao's technique but can't seem to get opt to remove obviously dead code from even the following trivial example: int mult(int a, int b){ return a*b; } int main(void){ return 0; } While mult is never called it still is not removed. I just can't seem to get opt to understand it's seeing the whole program so it can remove this

Hi All, Clang lacks support for the -fsingle-precision-constant flag. Are there specific reasons for this or is it just waiting to be implemented? This flag is especially important in the embedded world. From http://processors.wiki.ti.com/index.php/Floating_Point_Optimization#float_vs._double_vs._long_double : *Once all of your data is defined as float, there are still cases where you may

> > > Is there a reason why LLVM's link-time optimization won't work for you? > > http://llvm.org/docs/GoldPlugin.html > http://llvm.org/docs/LinkTimeOptimization.html > > Well the primary motivation to move to LLVM is licensing which is why we also ditched binutils since we can't package gcc for iOS due to the GPL. So in the end the gold plugin wouldn't

Hi, Thanks a lot for your answer. It seems lld is still the best solution, even if it does not work "right out of the box" for us today. We already have a solution for the "objcopy" part (added the required output format to llvm-objdump). The ScriptLayout class seems to be empty for now (on the master branch at least), but we do not need linker scripts today. All that is

Thanks for the response. If we add the support would you accept the patch? Seems like a pretty straightforward flag since it maps directly to NumericLiteralParser::NumericLiteralParser within LiteralSupport.cpp. I understand the maintenance concern with flags that affect multiple points in code though. Still trying to get the bottom of why we're crashing with double floating point literal.

Hi All, After the initial learning curve, we're excited to have put together a completely gcc/binutils-free toolchain based on LLVM. Now that we have things working, we desperately need to optimize the resulting binaries. Our bin files are up to 10x their fully optimized gcc equivalent (1.5k vs 16k). This is for a bare metal ARM based system so this is significant. We're using lld for

Just tried the latest release and found a minor bug. Have a UFD w/ SYSLINUX, which boots a simple .BSS image no problem. Launching exactly the same image on a ISOLINUX disc fails w/ the following error msg: Invalid image type for this media That's it for this msg. Later....Jet -- Powered by Outblaze

I have a 2gig usb drive FAT formatted with 32K cluster I used syslinux 3.06 to create a boot sector so that I could boot Damn Small Linux, INSERT and memtest86. They are all working fine. I have a DOS bootable CD and have been following this guy's instructions... http://fuzzymunchkin.dyndns.org/tdot/usbkeyfob/index.php3 I used a WinXP floppy formatted with the 'make ms-dos bootdisc'

Hello LLVM-Devs, Perhaps a pedantic question, but I'm wondering how __DATA,__common and __DATA,__bss symbols differ, and whether llvm-nm ought not classify the former as type "B" as it does the latter: $ cat bss.c int i; static int si __attribute__((used)); $ clang -fno-common -c bss.c $ nm bss.o 0000000000000000 S _i 0000000000000004 b _si $ nm -m bss.o 0000000000000000

I love syslinux, and loath to cry bug, but I think this might qualify. I found that using the chain loader in syslinux version 2.05 on a FreeDOS (ver. 2.30.1) boot floppy failed (locked after 'FreeDOS' is written to the screen). I tried other boot disks (dos 3.30, up to win98) with similar results. The good news is that version 1.40 (where it was originally implemented) works great !!

Hi, I'm sure this has been discussed before and probably ad-nauseaum, but I was unable to find anything in the mailing list archives or FAQ. So, I'm going to ask right out -- is there any way to create this file without resorting to using MS products? regards, Dan

Hi, OK, I solved the problem. Before calling "make installer", I first have to call "make spotless" and "make". Then I can call "make installer". Is that documented, somewhere? -- Regards, Igor

On Thu, 11 Jul, at 03:33:11PM, H. Peter Anvin wrote: > On 07/11/2013 01:38 PM, Igor Sverkos wrote: > > Hi, > > > > OK, I solved the problem. Before calling "make installer", I first > > have to call "make spotless" and "make". Then I can call "make > > installer". > > > > Is that documented, somewhere? > >

Basic support for Small bss and data. The rest is implemented with target specific logic and will be commited as soon as it's ok to commit this patch. -- Bruno Cardoso Lopes http://www.brunocardoso.cc "When faced with untenable alternatives, you should consider your imperative." -------------- next part -------------- A non-text attachment was scrubbed... Name: smallsections.patch

Hello, I noticed that the SPU assembly printer prints just ".bss", when gas requires ".section .bss". Now the gas prints out: Assembler messages: Error: expected symbol name Attached is a test case and a patch to fix this. (This time 'make check' passes also ;) kalle -------------- next part -------------- A non-text attachment was scrubbed... Name: spu_bss.patch

Hi, On SPU, variables in the .bss section that are allocated with the .lcomm directive are not aligned on 16 byte boundaries. This causes misaligned loads, as the generated assembly assumes this "default" alignment. A patch to disable .lcomm in favour of '.local .comm' is attached. kalle P.s. As an example, the following function returns '3', when '5' is

Is this an extension to what cctools' assembler provides or a missing feature in MC? On 28 September 2013 18:48, Nicholas White <n.j.white at gmail.com> wrote: > Hi - I've attached a patch to make the assembly parser recognise the > .bss directive on Darwin targets as a switch to the (__DATA,__bss) > section. The ELF & COFF assembly parsers already recongnise the .bss