search for: handlelateresolvedpoint

...bitcast it to a proper function pointer type before calling it. Shouldn't be too hard to implement. 3. There are other CodeGen tests that fail with assertion failures, which I haven't investigated. (I'm starting to wonder if I went too far when I ripped out all the PointersToResolve / HandleLateResolvedPointers() stuff from CodeGenTypes.cpp.) 4. A bunch of the CodeGen tests need adjusting because we're generating slightly different IR from what they expect. > Can you create a branch of the clang repo or send an updated version of the patch to the list? I'd be very surprised if I have the...

An update on the type-system-rewrite branch (http://llvm.org/viewvc/llvm-project/llvm/branches/type-system-rewrite/): It's now to the point where it passes all regression tests all of single source (and most of externals/multisource) when using an LLVM 2.9 version of clang to compile programs to a rbc file. I have what looks like one more subtle type mapping bug to track down, which will

...ction, and we bitcast all globals before use, so there's nothing else to change. > 3. There are other CodeGen tests that fail with assertion failures, > which I haven't investigated. (I'm starting to wonder if I went too > far when I ripped out all the PointersToResolve / > HandleLateResolvedPointers() stuff from CodeGenTypes.cpp.) Hmm... there shouldn't be anything you need to handle there, I think. > 4. A bunch of the CodeGen tests need adjusting because we're > generating slightly different IR from what they expect. > >> Can you create a branch of the clang repo o...