[LLVMdev] Difficulties Getting a Bug Fix Committed

[Duncan Sands]

Hi Michael, don't forget that Eric made some comments that you never replied to.
Since his comments seemed pretty pertinent I wasn't prepared to apply your patch
without a satisfactory response from you.

Ciao, Duncan.

> I've been waiting for almost three months now to get a patch committed to LLVM
> that fixes what I consider to be a fairly significant bug in the JIT
> (http://llvm.org/bugs/show_bug.cgi?id=13678) but I've been having a hard time
> getting traction on it.  So far Duncan Sands is the only one who has given it
> any attention, but as of the last time I checked it still wasn't committed and
> the bug is still open.
>
> Right now we ship our code with a patch to fix this in 3.1, I really don't
> want to have to do that again for 3.2.
>
> I appreciate the difficulties in running a project as large as LLVM, and it
> looks like there are some recent structural changes that might decentralize
> some of the review/commit burden, but it doesn't speak well for your project
> when you have a bug with a fix and a unit test just ready to go that's not
> getting into the next release.
>
> Can anyone help me move this forward?
>
> =============================================================================
> michaelMuller = mmuller at enduden.com | http://www.mindhog.net/~mmuller
> -----------------------------------------------------------------------------
> If you are not willing to control your own mind, there are plenty of other
> people who are willing to do it for you.
> =============================================================================
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>