Displaying 3 results from an estimated 3 matches for "pr6758".
Did you mean:
16758
2010 Aug 04
0
[LLVMdev] Announcing: LLVM 2.8 Release Schedule
...I try to port our
bytecode compiler.
> Leading up to that date,
> please make sure that the tree is stable – no regressions, etc. If
> you have a major feature which must make it into 2.8, please check
> them in by this time; the sooner the better.
Only one for me is the patch to fix PR6758, since without it PPC JIT
doesn't work for long-running applications at all.
I have a new patch for it that I use in ClamAV, will try if it passes
LLVM's make check (and PR6902) and commit it.
> If you aren't certain
> whether your feature is necessary for 2.8, please ask the app...
2010 Aug 04
3
[LLVMdev] Announcing: LLVM 2.8 Release Schedule
Good news, everybody!
It's that time of year again. We are going to release LLVM 2.8! I'm taking over for Tanya to give her a much needed break. I can only hope to perform as well as she has. This is my first time as release manager, so bear with me if things don't go smoothly.
This message is mostly to give you an idea of the schedule we're planning on. It's an aggressive
2010 Aug 04
1
[LLVMdev] Announcing: LLVM 2.8 Release Schedule
...minding me!
>> Leading up to that date,
>> please make sure that the tree is stable – no regressions, etc. If
>> you have a major feature which must make it into 2.8, please check
>> them in by this time; the sooner the better.
>
> Only one for me is the patch to fix PR6758, since without it PPC JIT
> doesn't work for long-running applications at all.
> I have a new patch for it that I use in ClamAV, will try if it passes
> LLVM's make check (and PR6902) and commit it.
>
August 6th isn't the absolute last date for getting changes into the bran...