[LLVMdev] CallInst API Changes Ready [was: Re: llvm-gcc-4-2 development branch is open]

David Greene dag at cray.com
Mon Jul 16 09:57:51 PDT 2007


On Wednesday 11 July 2007 18:55, David Greene wrote:

> I ask because I'm ready to commit the CallInst interface changes and it
> will break llvm-gcc.  There is no way to preserve the interfaces llvm-gcc
> needs because there are three places in the llvm-gcc code where
> the old interface conflicts with the new one (passing two Value*'s vs.
> passing two iterators to a template function).
>
> Again: when I commit the CallInst changes it will break llvm-gcc, and
> there's no way to avoid that.
>
> I can send an llvm-gcc patch for someone to apply, or if the current
> llvm-gcc is going to be put under subversion soon I can wait for that and
> commit the changes myself.  Either way, we will want the CallInst and
> llvm-gcc changes to happen as close together in time as possible to
> minimize the chance of disrupting someone's work.

Haven't heard anything back on this.  I'd like to get these changes in
before they become bitrotted.

                                               -Dave



More information about the llvm-dev mailing list