[Samsung Galaxy Nexus] MWisBest:
Well I've been hard at work on this LTO stuff, but it might take me an extra day or two longer than I thought. I ended up being swamped with homework for most of the time I had planned out for development which slowed me down, not to mention how sleep-deprived I am! >.< Figured I'd at least give you guys a heads up that I'm running later than expected.

One thing to note however, is that even when this LTO stuff is done and enabled and everything, I'm probably going to end up with some stability issues in the ROM itself as a result that I'll need to iron out. Like I had mentioned in the first post, in some respects this is even more experimental than a "Beta." I want to be innovative with things like this, but with all new things there's always going to be kinks to iron out.

The good news is that with things like this, there's a switch of sorts I throw in to just turn it off temporarily if needed. Initially I might put up two builds: An "Experimental" version with things like LTO enabled, meant for those who would like to help by reporting any issues that come up with it or just want to be on the bleeding-edge of development, and a "Stable" version with things like LTO disabled, meant for those who need the stability of a daily driver. If this takes much longer, I'll at the very least try to get a "Stable" build with LTO disabled uploaded.

EDIT: I'm going to just get a non-LTO build up tonight and then transfer over all the changes I've made so far with CM to AOKP and try to have a FML AOKP build done in a few days. I did come a long way with LTO, but the compilers just aren't doing me any favors in tracking down some of the final issues. The errors they're spitting out don't tell me at all where any issues are... (Note: the rest of this post is going to be kinda technical and you might not understand it, just FYI) it seems like an issue pops up when it links libc, which should mean that the issue is somewhere in bionic, but the functions it complains about having issues aren't in bionic (at least according to a quick recursive grep search)... codefireXperiment uses LTO from what I can tell but I wasn't able to find a change made by them related to this, so it might be fixed in AOSP's latest code (what they're based on) but I couldn't find anything specific pertaining to it. I did try to merge in AOSP's latest code myself but there were just too many conflicts and whatnot for me to fix. Maybe when KitKat (4.4) comes around I'll have an easier time with LTO. At the very least I learned a lot of new things from this, which is part of why I do projects like this, so I did accomplish something good. :)

Oh also, some of the things I did while working on LTO will still be useful with improving the ROM even without LTO, so it's not a total loss.

EDIT2: Wasn't able to get a build started last night, but the good news is that my sleep schedule finally makes sense... fell asleep at about 12AM and was awake at 8AM. I usually do my best dev work in the mornings so now I'll end up being awake before I leave for school to get some stuff done before school! :D Well I'm getting a build of CM going now, and while I wait on it I'll be working on an AOKP build. Hopefully I'll have a fresh CM build up in 4 or 5 hours (that includes testing time and whatnot, CM has made some changes to areas that concern me with mobile data related code so I'm going to keep an eye on it and really try to push mobile data through it's paces).

Something else I thought of regarding LTO is the possibility of enabling or disabling it on a section-by-section basis. It wouldn't have the full benefit of enabling it for everything, but it could result in an actually usable build and could allow for more stability overall. I'll put this idea on the back-burner for now though and continue focus on AOKP and then CMKP.

EDIT3: Ran into some issues while building CM and now once I was finally able to test it, it just bootlooped. So I'll be working on tracking this down for the time being I guess...