Searched hist:"0067051 fe7ec2efffec5f50f52bbc5699f955d64" (Results 1 – 5 of 5) sorted by relevance
/freebsd/sys/sys/ |
H A D | linker.h | diff 0067051fe7ec2efffec5f50f52bbc5699f955d64 Mon Oct 20 19:04:03 CEST 2014 Marcel Moolenaar <marcel@FreeBSD.org> Fully support constructors for the purpose of code coverage analysis. This involves: 1. Have the loader pass the start and size of the .ctors section to the kernel in 2 new metadata elements. 2. Have the linker backends look for and record the start and size of the .ctors section in dynamically loaded modules. 3. Have the linker backends call the constructors as part of the final work of initializing preloaded or dynamically loaded modules.
Note that LLVM appends the priority of the constructors to the name of the .ctors section. Not so when compiling with GCC. The code currently works for GCC and not for LLVM.
Submitted by: Dmitry Mikulin <dmitrym@juniper.net> Obtained from: Juniper Networks, Inc.
|
/freebsd/sys/kern/ |
H A D | subr_prof.c | diff 0067051fe7ec2efffec5f50f52bbc5699f955d64 Mon Oct 20 19:04:03 CEST 2014 Marcel Moolenaar <marcel@FreeBSD.org> Fully support constructors for the purpose of code coverage analysis. This involves: 1. Have the loader pass the start and size of the .ctors section to the kernel in 2 new metadata elements. 2. Have the linker backends look for and record the start and size of the .ctors section in dynamically loaded modules. 3. Have the linker backends call the constructors as part of the final work of initializing preloaded or dynamically loaded modules.
Note that LLVM appends the priority of the constructors to the name of the .ctors section. Not so when compiling with GCC. The code currently works for GCC and not for LLVM.
Submitted by: Dmitry Mikulin <dmitrym@juniper.net> Obtained from: Juniper Networks, Inc.
|
H A D | link_elf_obj.c | diff 0067051fe7ec2efffec5f50f52bbc5699f955d64 Mon Oct 20 19:04:03 CEST 2014 Marcel Moolenaar <marcel@FreeBSD.org> Fully support constructors for the purpose of code coverage analysis. This involves: 1. Have the loader pass the start and size of the .ctors section to the kernel in 2 new metadata elements. 2. Have the linker backends look for and record the start and size of the .ctors section in dynamically loaded modules. 3. Have the linker backends call the constructors as part of the final work of initializing preloaded or dynamically loaded modules.
Note that LLVM appends the priority of the constructors to the name of the .ctors section. Not so when compiling with GCC. The code currently works for GCC and not for LLVM.
Submitted by: Dmitry Mikulin <dmitrym@juniper.net> Obtained from: Juniper Networks, Inc.
|
H A D | link_elf.c | diff 0067051fe7ec2efffec5f50f52bbc5699f955d64 Mon Oct 20 19:04:03 CEST 2014 Marcel Moolenaar <marcel@FreeBSD.org> Fully support constructors for the purpose of code coverage analysis. This involves: 1. Have the loader pass the start and size of the .ctors section to the kernel in 2 new metadata elements. 2. Have the linker backends look for and record the start and size of the .ctors section in dynamically loaded modules. 3. Have the linker backends call the constructors as part of the final work of initializing preloaded or dynamically loaded modules.
Note that LLVM appends the priority of the constructors to the name of the .ctors section. Not so when compiling with GCC. The code currently works for GCC and not for LLVM.
Submitted by: Dmitry Mikulin <dmitrym@juniper.net> Obtained from: Juniper Networks, Inc.
|
H A D | kern_linker.c | diff 0067051fe7ec2efffec5f50f52bbc5699f955d64 Mon Oct 20 19:04:03 CEST 2014 Marcel Moolenaar <marcel@FreeBSD.org> Fully support constructors for the purpose of code coverage analysis. This involves: 1. Have the loader pass the start and size of the .ctors section to the kernel in 2 new metadata elements. 2. Have the linker backends look for and record the start and size of the .ctors section in dynamically loaded modules. 3. Have the linker backends call the constructors as part of the final work of initializing preloaded or dynamically loaded modules.
Note that LLVM appends the priority of the constructors to the name of the .ctors section. Not so when compiling with GCC. The code currently works for GCC and not for LLVM.
Submitted by: Dmitry Mikulin <dmitrym@juniper.net> Obtained from: Juniper Networks, Inc.
|