Searched refs:relocs (Results 1 - 4 of 4) sorted by relevance

/device/google/contexthub/firmware/build/
H A Dapp_config.mk26 LOCAL_OBJCOPY_SECT_cortexm4 := .flash .data .relocs .dynsym
/device/google/contexthub/util/nanoapp_postprocess/
H A Dpostprocess_elf.c93 struct ElfAppSection relocs; member in struct:ElfNanoApp
172 fprintf(stderr, "Unaligned relocs are not possible!\n");
295 struct RelocEntry *relocs; local
305 //make buffer 50% bigger than bufUsed in case relocs grow out of hand
327 relocs = (struct RelocEntry*)(buf + sect->rel_start - FLASH_BASE);
346 fprintf(stderr, "Found %" PRIu32 " relocs and a %" PRIu32 "-entry symbol table\n", numRelocs, numSyms);
348 //handle relocs
356 uint32_t relocType = relocs[i].info & 0xff;
357 uint32_t whichSym = relocs[i].info >> 8;
366 i, relocs[
734 const Elf32_Rel *relocs = (const Elf32_Rel *) app->relocs.data; local
[all...]
/device/google/contexthub/firmware/os/platform/stm32/lkr/
H A Dapp.lkr25 * list of relocs
33 After this image is produced a nonoapp_postprocess unitily will process relocs and symbols and compress them to a small reloc table
34 while also modifying the app code itself potentially to adjust for new reloc format. This shrinks relocs a lot. GCC produces relocs at 8
36 from there into relocs and app image itself, generating 4 bytes per reloc of "nano reloc data"
110 .relocs : {
112 /* relocs */
/device/google/contexthub/firmware/app/
H A Dapp.mk179 LDFLAGS += -Wl,--emit-relocs
230 $(OBJCOPY) -j.relocs -j.flash -j.data -j.dynsym -O binary $< $@

Completed in 57 milliseconds