Age | Commit message (Collapse) | Author |
|
It seems we can use it even for -static build with
-Wl,--whole-archive -lpthread -Wl,--no-whole-archive -ldl
|
|
Sticking to a single processor improves the performance while
we are running only a single thread.
|
|
It seems this is a fairly good choice even if we compare this
against string-specific algorithms, probably because our
strings are not usually very long.
|
|
and use stable_sort on Mac.
On Linux:
LCPMS: 0.627s, sort: 3.37s, stable_sort: 1.79s, qsort: 1.95s
On Mac:
LCPMS: 1.583s, sort: 1.33s, stable_sort: 1.19s, qsort: 1.80s
|
|
before: 0.668325s
after: 0.260734s
|
|
|
|
|
|
Android's build system uses -static to build ckati, and you
cannot use C++11's threading library with -static.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52590
|
|
Clang on Mac doesn't support thread_local keyword.
|
|
From ~1.5s to ~0.4s for an Android target.
|
|
|
|
|
|
Don't assume that kati is in a valid git directory.
Change-Id: I026fa07880924442f23fa4b1b8f40937fbd1afb8
|
|
|
|
As this feature is incomplete, this is enabled only with
--regen flag.
I decided not to use ninja's "generator" feature because we
cannot create appropriate regeneration rules for globs in
Android. There are some directory names which are also used
as target names (e.g., "cts"). Ninja tries to build such
targets to check if regeneration is necessary.
|
|
Allow Makefile.ckati to be included by another Makefile that
set KATI_CXX, KATI_INTERMEDIATES_PATH, and KATI_BIN_PATH.
Allows the kati build to be embedded into the Android build.
|
|
Rename CXX_* in Makefile.ckati to KATI_CXX_* to avoid collisions
when including Makefile.ckati from the Android build.
|
|
Split the makefiles so that the Android build can depend on C++
without pulling in the Go rules.
|