Adam Langley
5813c2c10c
This change switches nearly all of BoringSSL to use C++. The public functions still use the C ABI, and so code written in C can still use BoringSSL. Also the use of the C++ standard library is minimal and no run-time requirement for it is intended. Change-Id: I902d2f51a3c8d6bd0dc4aabe1b192a15d7b788e8 Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/72747 Commit-Queue: Adam Langley <agl@google.com> Reviewed-by: Bob Beck <bbe@google.com>
29 lines
629 B
Plaintext
29 lines
629 B
Plaintext
SECTIONS
|
|
{
|
|
.text : {
|
|
BORINGSSL_bcm_text_start = .;
|
|
*(.text)
|
|
*(.text.unlikely.*)
|
|
/* These sections shouldn't exist. But C++ `inline` symbols seem to be
|
|
* placed in function sections on Android even with
|
|
* -fno-function-sections. */
|
|
*(text.*)
|
|
BORINGSSL_bcm_text_end = .;
|
|
}
|
|
.rodata : {
|
|
BORINGSSL_bcm_rodata_start = .;
|
|
*(.rodata)
|
|
*(.rodata.*)
|
|
BORINGSSL_bcm_rodata_end = .;
|
|
}
|
|
|
|
/DISCARD/ : {
|
|
/* These sections shouldn't exist. In order to catch any slip-ups, direct
|
|
* the linker to discard them. */
|
|
*(.rela.dyn)
|
|
*(.data)
|
|
*(.rel.ro)
|
|
*(*.data.*)
|
|
}
|
|
}
|