Displaying 4 results from an estimated 4 matches for "46649".
Did you mean:
4664
2020 Jul 24
3
New pass manager for optimization pipeline status and questions
Hi all,
The current plan is to prioritize enabling the NPM as soon as possible, and
that includes addressing any blockers that are known or arise. This means
prioritizing those blockers over other LLVM work. The current umbrella bug
is PR46649 <https://bugs.llvm.org/show_bug.cgi?id=46649>.
Philip's point is spot on that we are deficient now in the testing of the
LegacyPassManager, because so many have already made the switch (FWIW
Google switched more than 2 years ago).
It's not constructive for the LLVM community to just...
2020 Jul 28
2
New pass manager for optimization pipeline status and questions
...acyPassManager,
>
> I disagree because the LPM is still the default and I appreciated Hans'
> reply: "Defaults tend to be popular". But this is the direction I like:
>
> > This means prioritizing those blockers over other LLVM work. The current
> umbrella bug is PR46649 <https://bugs.llvm.org/show_bug.cgi?id=46649>.
>
> Just checking: do you accept both performance and code-size regressions as
> blockers here?
>
Yes, I think big performance and code-size regressions need to be
investigated. It will be hard to quantify what "big" is tho...
2017 May 01
3
lmtp segfault after upgrade
...error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000]
lmtp[46304]: segfault at 91 ip 00007f771ba64d11 sp 00007ffe830635a0
error 4 in libdovecot.so.0.0.0[7f771b9bf000+11c000]
lmtp[45775]: segfault at 21 ip 00007f206ed81d11 sp 00007ffd0f0daad0
error 4 in libdovecot.so.0.0.0[7f206ecdc000+11c000]
lmtp[46649]: segfault at 21 ip 00007ff4aa027d11 sp 00007ffc05841430
error 4 in libdovecot.so.0.0.0[7ff4a9f82000+11c000]
lmtp[45774]: segfault at 21 ip 00007ff1f3e0bd11 sp 00007ffe0ba00340
error 4 in libdovecot.so.0.0.0[7ff1f3d66000+11c000]
lmtp[45776]: segfault at 411 ip 00007f96ded95d11 sp 00007ffce6401870...
2020 Jul 23
2
New pass manager for optimization pipeline status and questions
FWIW I'm in favor of this direction while making sure that we keep focus on
removing the vestiges of the old pass manager for the code health impact to
the project.
-eric
On Wed, Jul 22, 2020 at 3:15 PM Philip Reames via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> (I'm probably going to derail your thread, sorry about that.)
>
> I think at this point, we should just