| Commit message (Collapse) | Author | Age | Files | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Implicit function declarations are much more dangerous on LP64 because
sizeof(int) != sizeof(void*), so any function that returns a pointer will
lose its top bits, leading to relatively hard to debug crashes.
Change-Id: Ia05beffb949ca747833c2e12c40daf896f7a60a5
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| | |
Implicit function declarations are much more dangerous on LP64 because
sizeof(int) != sizeof(void*), so any function that returns a pointer will
lose its top bits, leading to relatively hard to debug crashes.
Change-Id: Ib2570326dde1b1cde09c63c9b4c973d741528ee2
|
|/
|
|
|
|
|
|
|
|
|
| |
We don't support platform builds under CYGWIN and can safely
assume that all windows host builds are for MinGW32.
HAVE_WINSOCK2_H is currently unused. The only references to it
are in code that define it themselves or in application code that
by definition isn't compiled for windows.
Change-Id: I236d6e070df93f713cb716bb8a461c9c1d32a180
|
|
|
|
|
|
|
|
| |
The transitive symbol resolving causes build breakage when a binary
linked against NDK has indirect dependency on platform libraries, or
vice versa.
Change-Id: Idbfe76079c1db14eb1156d0f396e13d26f0ff582
|
|
|
|
|
| |
Bug: 19083585
Change-Id: I5be0d2f95c3c45e7f67de6a8daeb49709ef1f9e9
|
|
|
|
| |
Change-Id: Ice2d0f65eced4fb7dd209fb15610ba555dd45f2c
|
|
|
|
|
|
|
|
|
|
|
| |
We want to store the symbol information for all android binaries in a global database.
* We ingest unstripped binaries into the global database
* When we collect address data from device (e.g. instruction pointer address), we want to lookup its symbol information through the global database. The key of the mapping is a unique build id, which is the same between binaries on device (stripped) and unstripped binaries.
After applying this patch, the system.img size increases by 0.0047% (16.3KB).
Change-Id: Id92faf2951f43a30947e8d2b690c1af6bf7e3f54
|
|
|
|
| |
Change-Id: I685357292af45a048439f0df0ae45f513479841a
|
|
|
|
|
|
|
| |
In particular, no one has had the system property server since we
killed the sim-eng build...
Change-Id: If576ec546b0ba2ad3c5299876027ca9ac189cf4a
|
|
|
|
| |
Change-Id: Ide6f54f70bc5edda9ec1f1f05ebaa0acf58aaa77
|
|
|
|
| |
Change-Id: Ic58f8e4c0f749bbc19e5d14de8d99321e7cf833c
|
|
|
|
| |
Change-Id: I9ee38c603e3933b012da818b386cb374eec9fe21
|
|
|
|
|
|
|
| |
The only code that still references this is only built for arm, so this
should be a no-op.
Change-Id: I64f40fc68bb387b6309075d158f5bd12f398ef20
|
|
|
|
|
|
|
|
| |
The transitive symbol resolving causes build breakage when a binary
has indirect dependency on the NDK library.
We only observed such behaviour in the aarch64 toolchain.
Change-Id: I29e01f16bdfa3aa206cd42d6f07c764fd436873a
|
|
|
|
| |
Change-Id: I1308b90c4b33d0ab1a01de44bebba03687217f2b
|
|
|
|
| |
Change-Id: Ibaaf112c5a6bfe2084fe34e32e31bcd755e718a8
|
|\ |
|
| |
| |
| |
| | |
Change-Id: Id85c56452a478ea94bdb6ea2b990c3b46a81eed9
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: Iec9978e0bb69585dde69593402d53309e0ecb662
|
|/ /
| |
| |
| | |
Change-Id: Ifa48fab99d73fb532afc56d235b7397e05c0fc6a
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Change-Id: I832247bec22f23666f14dfb715192ada201ab097
|
|/ /
| |
| |
| | |
Change-Id: Ic3014aa01f82204b75c54ab3f7afa3a44890e02e
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Otherwise wrong set of memory/string functions is chosen when building atom
image (in Bionic we have libc/arch-x86/atom/atom.mk). Plus this naming is
consistent with other x86 architectures.
Change-Id: I21e899534e7ce10530474a22ceba770422b39d8d
Signed-off-by: Alexander Ivchenko <alexander.ivchenko@intel.com>
|
|/
|
|
|
|
|
|
|
|
| |
Bug: 18589470
__LP64__ is only defined for 64-bit compilation targets, so this macro
is evaluated as an implicit 0 in the original case. This change makes
it explicit that we only care whether this is actually defined.
Change-Id: I8c11b41fc0bde9477c5efeea0782d9741d9d827d
|
|
|
|
| |
Change-Id: I4f401900285e166486bb426ac02bc69fc5509a3c
|
|
|
|
| |
Change-Id: I0072847719566e9622ec9765673fdeb8be9eb5ef
|
|
|
|
| |
Change-Id: I6e4df2449b27d67f207fc53b19e49b21f9cee611
|
|
|
|
| |
Change-Id: Ie596af7460ec33d70d7327e629b38d641ef48ba2
|
|
|
|
| |
Change-Id: I40c63b8e7ae1174ac902b545555ddab65b3fef38
|
|
|
|
| |
Change-Id: If3ff83c475921d72936a19317e356549d1706fab
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add the build options to support the most recent versions of XCode and
add 10.9 to the list of OS X SDKs which the AOSP code can be built with.
Based on patch from https://groups.google.com/d/msg/android-building/kePgJmYBUdM/0C_d1OZflvcJ
Change-Id: I97ffe45d3c54a095952a4ac6accb938623b8fa1e
Signed-off-by: Al Sutton <al@funkyandroid.com>
|
| |
| |
| |
| |
| | |
Bug: 18397613
Change-Id: I0061f8080709449f13dc76ce61097a2671c799ff
|
| |
| |
| |
| |
| | |
Bug: 18397020
Change-Id: I6b9c7d30432858131379759e738d3e04bc8d5fb5
|
| |
| |
| |
| |
| |
| |
| | |
We have a lot of definitions around the tree, of which this is but one,
but we have no users.
Change-Id: Ic411505a0370be2b56150275fa9b8f5329241ce8
|
| |
| |
| |
| |
| |
| |
| | |
No one's using ARCH_AARCH64 or AARCH_MIPS64 yet, and ARCH_PPC was always more
aspirational than real.
Change-Id: I07c6cbad6eb0917c4c24848a98c3bc9a3fe72db6
|
| |
| |
| |
| |
| | |
Bug: 18398307
Change-Id: I54fc0235fbc40630f8024570b928dba115b1c39a
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Previously, there was one generic definition for each of the
transform-o-to-* functions in definitions.mk, and one target specific
one in each combo/TARGET_*.mk. The generic one was entirely unused,
and the target specific ones were all nearly identical.
Changing anything in these functions was tedious at best, and often
error prone. The differences between any 32-bit arch and its 64-bit
equivalent were restricted to the name of the linker, and the ARM and
MIPS definitions were identical. The few differences between ARM and
x86 looked to be compatibility for an old (ca. 2008) toolchain issue
with --gc-sections, and a bug (LDFLAGS coming first rather than
later).
To simplify things, I've moved the definitions for these out of
combo/TARGET_*.mk and back into definitions.mk. The differences
between ARM and x86 have been scrapped. Anything that really does
still need to be target specific can be handled as I have the linker:
add a TARGET_FOO variable to the given target and then add it to the
generic definition.
Change-Id: I54dc1bffc32ac39f27f0b87247dd6a6dbaf0b162
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18373609
Change-Id: Ia2c965fb86295858d9a97db2ec8d54d99e3d431f
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18317407
Change-Id: Idaff8a161305325dbb0a9e00764afe98b66e3312
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18361583
Change-Id: If76334a6e18893b65d9b526271620a460a75bf22
|
| | |
| | |
| | |
| | |
| | | |
Bug: 18363225
Change-Id: Ib34c094cd21b2221178755acdd9475a5bc2bf2c0
|