[avr-gcc-list] ELF R_AVR_13_PCREL Relocation

Hello, I'm working on a port of LLVM for AVR. I am currently adding AVR support to the linker, but I have a question about something that seems strange. This relocation is solely for the relative `jmp` and `call` instructions (if I'm not mistaken). Both of thes

Re: [avr-gcc-list] ELF R_AVR_13_PCREL Relocation

In `binutils/bfd/elf32-avr.c`, the line that actually computes the relocation: `x = (x & 0xf000) | (srel & 0xfff);` Is only modifying bits in the `0xfff` mask, a total of 12 bits. This makes it seem even more strange. On Thu, Feb 19, 2015 at 3:11 PM, Dylan McKay wrote: > Hel

Re: [avr-gcc-list] ELF R_AVR_13_PCREL Relocation

, HDL cave, simply left shifts the offset during the execute cycle? That way we save a bit in the instruction encoding that was always going to be the same? On Thu, Feb 19, 2015 at 3:59 PM, Jeff Barlow wrote: > On 02/18/2015 06:11 PM, Dylan McKay wrote: > >> >> This relocation

[avr-gcc-list] AVR C calling convention not matching spec

Hey all, I'm working on the AVR backend for LLVM. I'm looking into an issue where the current LLVM implementation of the AVR C calling convention is not matching the assembly of what GCC is generating. On top of that, when I run through the argument algorithm described on the Wiki (https://gcc.g

Re: [avr-gcc-list] AVR C calling convention not matching spec

pandi < pitchumani.sivanupa...@microchip.com> wrote: > On Sunday 11 December 2016 07:13 AM, Dylan McKay wrote: > >> Hey all, >> >> I'm working on the AVR backend for LLVM. >> >> I'm looking into an issue where the current LLVM implementation of the >> AVR C

Re: [avr-gcc-list] LLVM 4.0 AVR backend

h use of clang, but it's been good for gcc to have a bit of >> >> friendly competition. I think it will be interesting to see how >> >> clang/llvm differs from gcc for the AVR. >> > >> > I built it a while back when I added basic support for avr to clang

[avr-gcc-list] When does __do_copy_data get inserted

Hello all, I maintain the AVR LLVM backend, for which downstream users typically use avr-gcc to link, so they get the CRT, startup routines, and libgcc. I've noticed that AVR-GCC does not insert the __do_copy_data function for LLVM generated executables, but it does for GCC generated ones. In ca

Re: [avr-gcc-list] When does __do_copy_data get inserted

o initialized globals). > > Hope this helps. > > Regards > Senthil > > On Thu, Aug 24, 2017 at 7:54 PM, Dylan McKay wrote: > >> Hello all, >> >> I maintain the AVR LLVM backend, for which downstream users typically use >> avr-gcc to link, so they