• State Not Answered
  • Locked Locked
  • Replies 3 replies
  • Subscribers 22 subscribers
  • Views 2744 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

L6440W warning after linking the project w/ ARMCC compiler 6.15

Zoltan Kakuk

Hello!

I am receiving the following warning at the end of linking process, and I would like to ask if anyone knows what causes it?

Warning: L6440W: Disabling merging for h1_valid.o(.conststring), unsupported relocation R_ARM_REL32 from h1_valid.o(.text) to STT_SECTION type symbol

I am using ARMCC compiler 6.15.

Regards,

Zoltan

Parents
  • 0

    Ok this warning is issued only if we call __heapvalid from the source code. In the map file I can see h1_valid.o added to the object files.

    ../clib/heap1.c 0x00000000 Number 0 h1_alloc.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_free.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_realloc.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_alloc_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_free_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_realloc_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_init.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_memalign.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_init_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_memalign_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_stats.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_valid.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_extend.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_extend_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_final.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_final_threads.o ABSOLUTE

    If we omit this call, the warning is not issued anymore.

Reply
  • 0

    Ok this warning is issued only if we call __heapvalid from the source code. In the map file I can see h1_valid.o added to the object files.

    ../clib/heap1.c 0x00000000 Number 0 h1_alloc.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_free.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_realloc.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_alloc_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_free_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_realloc_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_init.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_memalign.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_init_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_memalign_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_stats.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_valid.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_extend.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_extend_threads.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_final.o ABSOLUTE
    ../clib/heap1.c 0x00000000 Number 0 h1_final_threads.o ABSOLUTE

    If we omit this call, the warning is not issued anymore.

Children