Displaying 3 results from an estimated 3 matches for "__frame_dummy_init_array_entry".
2010 Dec 14
3
[LLVMdev] __used__ attributes in llvm-gcc's crtstuff.c
...__used__, aligned(sizeof(func_ptr))))
#else
__attribute__ ((__unused__, aligned(sizeof(func_ptr))))
#endif
/* LLVM LOCAL end */
= { (func_ptr) (-1) };
Note that __unused__ just suppresses the warning that __CTOR_LIST__ is not
used.
My question is that why some global static variables, such as
__frame_dummy_init_array_entry
and __do_global_dtors_aux_fini_array_entry, are not given __used__
attributes.
It seems that llvm-gcc removes these variables and causes .init_array and
.fini_array section
to be empty. Linker complains about this as in "ld: warning: .init_array
section has zero size".
Also, I verified th...
2010 Dec 14
0
[LLVMdev] __used__ attributes in llvm-gcc's crtstuff.c
...les - one with the code with -fno-toplevev-reorder
and one - without. What should be done
in such case?
> I presume __used__ attribute is used instead.
This is correct, because this is what in fact the code should do here.
> My question is that why some global static variables, such as
> __frame_dummy_init_array_entry
> and __do_global_dtors_aux_fini_array_entry, are not given __used__
> attributes.
Just bug.
> it caused no problem for me so far.
> Would it be any problem in doing so?
Please prepare the patch and submit to llvm-commit. Thanks!
--
With best regards, Anton Korobeynikov
Faculty of Ma...
2016 Feb 03
2
lld dynamic relocation creation issue
Hi all,
Working on lld aarch64 support I came across an issue where I am not sure which
would be best design approach to solve.
The aarch64 R_AARCH64_ABS64 relocation for PIC/PIE build requires a dynamic
relocation (R_AARCH64_RELATIVE) with the value set as the addend of the
relocation. For instance, when linking the crtbeginS.o which contains:
Relocation section '.rela.init_array' at