search for: 118280

...> we’re quite ready to make the switch yet. There was a discussion last > October about what was left to be done. I’m sure it has been discussed > since then too. Here’s a link to the start of the October discussion. > > > > http://lists.llvm.org/pipermail/llvm-dev/2017-October/118280.html > Yes I have gone through that mail chain. One thing mentioned in that was Code Generation does not use new PM so I wanted to start working in that direction. > > > If you’d like to get involved, one possible area you could contribute is > adding optbisect/optnone support as me...

...ds on this topic? I don’t believe we’re quite ready to make the switch yet. There was a discussion last October about what was left to be done. I’m sure it has been discussed since then too. Here’s a link to the start of the October discussion. http://lists.llvm.org/pipermail/llvm-dev/2017-October/118280.html If you’d like to get involved, one possible area you could contribute is adding optbisect/optnone support as mentioned in this bug: https://bugs.llvm.org/show_bug.cgi?id=28316 If that looks like something you’re interested in I can offer some guidance with it. Thanks, Andy From: llvm-dev...

Hello LLVM-Devs, I am trying to get some starting points for working on following new pass manager related bugs: https://bugs.llvm.org/show_bug.cgi?id=28322 [PM] Remove use of old PM in the middle-end. https://bugs.llvm.org/show_bug.cgi?id=28323 [PM] Use new PM in production for Clang, LLD, libLTO, etc. middle-end https://bugs.llvm.org/show_bug.cgi?id=28321 [PM] Remove use of old PM in the

...o make the switch yet. There was a discussion last >> October about what was left to be done. I’m sure it has been discussed >> since then too. Here’s a link to the start of the October discussion. >> >> >> >> http://lists.llvm.org/pipermail/llvm-dev/2017-October/118280.html >> > Yes I have gone through that mail chain. One thing mentioned in that was > Code Generation does not use new PM so I wanted to start working in that > direction. > >> >> >> If you’d like to get involved, one possible area you could contribute is >>...

...ds on this topic? I don’t believe we’re quite ready to make the switch yet. There was a discussion last October about what was left to be done. I’m sure it has been discussed since then too. Here’s a link to the start of the October discussion. http://lists.llvm.org/pipermail/llvm-dev/2017-October/118280.html Yes I have gone through that mail chain. One thing mentioned in that was Code Generation does not use new PM so I wanted to start working in that direction. If you’d like to get involved, one possible area you could contribute is adding optbisect/optnone support as mentioned in this bug: htt...

...> we’re quite ready to make the switch yet. There was a discussion last > October about what was left to be done. I’m sure it has been discussed > since then too. Here’s a link to the start of the October discussion. > > > > http://lists.llvm.org/pipermail/llvm-dev/2017-October/118280.html > > Yes I have gone through that mail chain. One thing mentioned in that was > Code Generation does not use new PM so I wanted to start working in that > direction. > > > > If you’d like to get involved, one possible area you could contribute is > adding optbisect/op...

...o make the switch yet. There was a discussion last >> October about what was left to be done. I’m sure it has been discussed >> since then too. Here’s a link to the start of the October discussion. >> >> >> >> http://lists.llvm.org/pipermail/llvm-dev/2017-October/118280.html >> >> Yes I have gone through that mail chain. One thing mentioned in that was >> Code Generation does not use new PM so I wanted to start working in that >> direction. >> >> >> >> If you’d like to get involved, one possible area you could contri...

...t believe > we’re quite ready to make the switch yet. There was a discussion last > October about what was left to be done. I’m sure it has been discussed > since then too. Here’s a link to the start of the October discussion. > > http://lists.llvm.org/pipermail/llvm-dev/2017-October/118280.html > > If you’d like to get involved, one possible area you could contribute is > adding optbisect/optnone support as mentioned in this bug: > > https://bugs.llvm.org/show_bug.cgi?id=28316 > > If that looks like something you’re interested in I can offer some > guidance wi...