Add moartools for optimization
Allow aosp to use optimizer as well
Optimization: use BSPEED if present to set concurrant threads
Bump to 4.4.4 in flash script
Revert "Add experimental flag to support OpenJDK builds."

This reverts commit b0df8f7519b7d32b5275e7183ccbbb5bb851370c.

Conflicts:
	core/combo/javac.mk
	core/main.mk
GCC Freedom (only)

.
.
This will allow you the freedom of using any custom toolchain of your choice,
provided you follow a few simple rules:

RULE #1: Both the androideabi and armeabi toolchain folders of your choice HAVE to
be named like the following:

for androideabi, the folder has to be prefixed with: arm-linux-androideabi-
and for arm-eabi, the folder has to be prefixed with: arm-eabi-

ex:

If you want to use GCC-4.8 as your toolchain of choice, both the androideabi and
armeabi folders have to look like this:

arm-linux-androideabi-4.8
arm-eabi-4.8

if you want them to be different, say, 4.8 for the arm-eabi and 4.9 for androideabi,
then they should look like this:

arm-eabi-4.8
arm-linux-androideabi-4.9

Take note, that if usining linaro, you will have to clone in the toolchain twice as
this method requires two different folders (the way it should be IMO). You would need
to rename one of the clones to arme-abi- and the other to arm-linux-androideabi-.

RULE #2: The source is configured to build with GCC 4.7 for androideabi and GCC 4.7 for
armeabi "by default" (in core/combo/TARGET_linux-arm.mk) unless you are to specify an alternate
target chain in build/core/TARGET_linux-arm.mk (lines 50 & 51). So if you want to use a different chain,
you'll need to change the chain number at the end of those two lines.

Say you wanted to use a 4.8 chain instead for armeabi and 4.9 for androideabi.. You would
just change the numbers at the end of both:

TARGET_GCC_VERSION_ARM := 4.8
TARGET_GCC_VERSION_AND := 4.9

Notice at the end of each line one is for ARM and one is for AND which hints at armeabi
and androideabi.

Remember, that this simple number change you specify at the end will decide
which toolchain you will use. So if you would rather use a 4.6 GCC, just change the
number to 4.6.

You also need to make sure rule number 1 is observed if you do this.. Can't build with
an alternate chain if one is not present ;)

RULE #3: Using higher than 4.7 GCC requires a few extra commits to source. These can be
found on my github account: https://github.com/IAmTheOneTheyCallNeo
If you have any questions or problems, feel free to message me and I will help if/when I can.
-Neo

Conflicts:
	core/tasks/kernel.mk

Conflicts:
	core/combo/TARGET_linux-arm.mk
GCC 4.8 Build Fix

Conflicts:
	core/combo/TARGET_linux-arm.mk
	core/combo/select.mk
Move Toolchain Define to Device Common files
Add Default Toolchain revision if not defined in BoardConfig.mk
Fix derp
Add GCC Variables to DumpVar

Conflicts:
	core/dumpvar.mk
Remove Default Defines for GCC in TARGET_linux-arm.mk - Moved to device BoardConfig.mk/BoardConfigCommon.mk
Display proper toolchain for kernel.
Add support for $TARGET_KERNEL_CUSTOM_TOOLCHAIN_PREFIX

Conflicts:
	core/tasks/kernel.mk
Fix small derp
Fix var being set to wrong line and add prefix to dumpvar
Add inclusion of optimized dalvik libs

Conflicts:
	core/config.mk
Fix derp
Change -Wno-error=unused-parameter to -Wno-unused-parameter
build: Add ro.oct.device

Some devices, such as n7100, report under another product name
in ro.product.name.
As this is breaking delta updater, we introduce another variable
to retrieve the actual device name as it was used to build.

Change-Id: I96ecd189453ea9929884d094a7b846365506c397

Conflicts:
	core/Makefile
	tools/buildinfo.sh