| 3d747ba34a94525cec1cf70db244c7cf00a62de9 |
|
18-Jun-2013 |
Stephen Hines <srhines@google.com> |
.align behaves differently on ARM and x86.
Change-Id: I3eb4000689a61e030a3a1d50d44c87414e6cf15f
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| bec0ac6a8dd538a0304df970036ad8e5633b878b |
|
15-Jun-2013 |
Stephen Hines <srhines@google.com> |
Fix assembly directives for SHA data generation.
With ".align 8" placed after the symbolic label, the values end up being
placed at the wrong location, thus causing reads of 0 (unitialized) values.
Consider the following assembly code:
foo:
.align 8
.byte 0x1
bar:
.align 8
.byte 0x2
baz:
.align 8
.byte 0x3
This will result in the following sample memory layout:
foo -> 0x400 (with value 1 there)
bar -> 0x401 (with value 0 - uninitialized memory)
0x408 (with value 2)
baz -> 0x409 (with value 0 - uninitialized memory)
0x410 (with value 3)
This patch moves the ".align 8" directive before each label.
Change-Id: I0e0a2ea4b4d4a48a9fe660e86f8f0106f2ec7723
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| f290793bc65b8483332ac8b568962395c4a63927 |
|
13-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine SHA-1 related stuffs.
1. Introduce libbcc.sha1.so instead of raw file libbcc.so.sha1
* Now tools/build/gen-sha1-stamp.py generated assembly contains
symbols libbcc_so_SHA1 and libRS_so_SHA1 associated with their
SHA-1 digests.
* In that way, their SHA-1 information can be obtained via
dlopen().
2. Refine Sha1Helper to Sha1Util.
2. Remove unused tools/build/dataconvert.py by the way.
Change-Id: I345e1a09e6206748fb8dfabf891154de97a063ec
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| ddf5661793de8fb4e16906b7f7822972fcb13c6d |
|
12-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine the makefiles.
* Introduce libbcc.mk which defines the path for makefiles and libbcc
configuration.
* Introduce libbcc-{device,host}-build.mk which defines the build
flags for building libbcc itself and/or for building module using
libbcc.
* Add header guard for generated ConfigFromMk.h.
Change-Id: I892f6d3637f628ea6aa0116d92ebc54770ce3a47
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| b8ef690813bf3b32f996afb0ddc048c5bb23c8f5 |
|
03-May-2012 |
Stephen Hines <srhines@google.com> |
Revert "Refine the makefiles."
This reverts commit fa52e2083927dd4ea543528c557d52ab578ad34c.
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| 6975a6653f5c433ba2fc009b4400c1c8157b512f |
|
03-May-2012 |
Stephen Hines <srhines@google.com> |
Revert "Refine SHA-1 related stuffs."
This reverts commit 6378d8f50449d79b8937c238b968ceeb9dbd4ee1.
Conflicts:
Android.mk
Change-Id: Ib8988583a0b916d21e9314e919269f02c4dd600e
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| 6378d8f50449d79b8937c238b968ceeb9dbd4ee1 |
|
13-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine SHA-1 related stuffs.
1. Introduce libbcc.sha1.so instead of raw file libbcc.so.sha1
* Now tools/build/gen-sha1-stamp.py generated assembly contains
symbols libbcc_so_SHA1 and libRS_so_SHA1 associated with their
SHA-1 digests.
* In that way, their SHA-1 information can be obtained via
dlopen().
2. Refine Sha1Helper to Sha1Util.
2. Remove unused tools/build/dataconvert.py by the way.
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| fa52e2083927dd4ea543528c557d52ab578ad34c |
|
12-Apr-2012 |
Zonr Chang <zonr.net@gmail.com> |
Refine the makefiles.
* Introduce libbcc.mk which defines the path for makefiles and libbcc
configuration.
* Introduce libbcc-{device,host}-build.mk which defines the build
flags for building libbcc itself and/or for building module using
libbcc.
* Add header guard for generated ConfigFromMk.h.
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|
| b4db722b7e400d9ce93f41b3d4243fd4f20ef300 |
|
06-Feb-2012 |
Zonr Chang <zonr.net@gmail.com> |
Move the build-related script under tools/build.
/frameworks/compile/libbcc/tools/build/gen-sha1-stamp.py
|