[LLVMdev] LLVMContext: Suggestions for API Changes

[Jeffrey Yasskin]

On Wed, Jul 15, 2009 at 2:24 PM, Albert Graef<Dr.Graef at t-online.de> wrote:
> Owen Anderson wrote:
>> On Jul 15, 2009, at 10:56 AM, Jean-Daniel Dupas wrote:
>>>
>>> You mean like this subject ?
>>>
>>> http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-June/023505.html
>>
>> Notice the sender line on that email... ;-)
>
> Yes, you indeed announced that change, but as John rightfully remarked,
> the announcement gave little detail. For LLVM users like me, who just,
> well, *use* LLVM, this wasn't enough. Maybe it's not time to document
> the changes yet, and maybe everybody but the LLVM developers should stop
> using LLVM from svn for a while until the API stabilizes again. That's
> fine with me. I can only politely ask that at some point someone please
> provide us with the information that we need to port our stuff to the
> new API so that we don't have to spend days digging through the LLVM
> source code. ;-)

See Owen's email about docs for the 2.6 release, but it's really not
that hard to keep up with trunk. I recently merged trunk LLVM into
Unladen Swallow, and the changes I needed to make are at
http://code.google.com/p/unladen-swallow/source/detail?r=724. You get
some compiler errors saying that an LLVMContext parameter is missing;
you grep the source for LLVMContext, finding
http://llvm.org/viewvc/llvm-project/llvm/trunk/include/llvm/LLVMContext.h?view=markup;
you read that and find the "/// FOR BACKWARDS COMPATIBILITY" line at
the bottom; and you pass getGlobalContext() all over the place until
the compiler's happy.

The InitializeNativeTarget() change was harder to discover, but it
wasn't that hard to search the list for.