[llvm-dev] questions about backport to 3.8/3.9/4.0
Hans Wennborg via llvm-dev
llvm-dev at lists.llvm.org
Mon Jul 17 08:35:55 PDT 2017
I think we generally don't plan for .2 releases unless some
particularly nasty bug shows up.
On Sat, Jul 15, 2017 at 12:38 AM, Y Song via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> Thanks. That is good suggestion. I will start to work on 4.0 now.
> It would be good to know the 4.0.x patch release schedule and how to
> I found this email containing backporting timeline for 4.0.1 (already done):
> From email, it is not clear to me whether we have upcoming
> 4.0.2 or not.
> On Fri, Jul 14, 2017 at 2:27 PM, 陳韋任 <chenwj.cs97g at g2.nctu.edu.tw> wrote:
>> I have no experience on backporting. However, the patches you want
>> only involves BPF backend itself,
>> I don't see any particular trouble of backporting. I would suggest you
>> start working on the latest LLVM
>> release, i.e., 4.0, then run the testsuite to make sure there is no regression.
>> 2017-07-15 1:36 GMT+08:00 Y Song via llvm-dev <llvm-dev at lists.llvm.org>:
>>> I want to backport the following three patches (currently in trunk 5.0)
>>> to 3.8/3.9/4.0:
>>> Some BPF users want them since their product needs to work on
>>> old linux distribution which has older versions of LLVM.
>>> Could somebody (maybe Tom Stellard or others) help clarify whether it
>>> is possible and what is the procedure/timeline for backporting?
>>> LLVM Developers mailing list
>>> llvm-dev at lists.llvm.org
>> Wei-Ren Chen (陳韋任)
>> Homepage: https://people.cs.nctu.edu.tw/~chenwj
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
More information about the llvm-dev