Review: back out LLVM pass changes

I've spent several days tracking down crashes in our LLVM-generated code, with little satisfaction.  I still don't know if this reveals bugs in LLVM or that we have subtly misused it, but in any case I think we need to back out the changes from about a week ago where I radically altered which optimization passes we were scheduling.

This patch takes us back to a place where we run without crashing, although MUCH slower than we'd like to be.  But now that we are correct, I'll work again on optimization, this time more slowly and carefully, to ensure that we identify exactly what changes bring us to dragon territory.

[aconty, 2010-08-11 18:40:16]

So this just reverts your previous commit? Go ahead and we'll take it from
there.

[ckulla, 2010-08-11 18:49:58]

LGTM

[lg_imageworks.com, 2010-08-11 19:42:50]

Effectively, yes.  But it's slightly more complex than a simple revert, as it
keeps the non-working newer version present but #ifdef-ed out, so I can refer it
as we move forward to reconstruct the most highly optimized set that continues
to work properly.


On Aug 11, 2010, at 11:40 AM, <aconty@gmail.com> <aconty@gmail.com> wrote:

> So this just reverts your previous commit? Go ahead and we'll take it
> from there.
> 
> http://codereview.appspot.com/1951042/show
> 
> -- 
> You received this message because you are subscribed to the Google Groups "OSL
Developers" group.
> To post to this group, send email to osl-dev@googlegroups.com.
> To unsubscribe from this group, send email to
osl-dev+unsubscribe@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/osl-dev?hl=en.
> 
> 

--
Larry Gritz
lg@imageworks.com