search for: shrinkwrapping

How can I get a FXMDIChild to shrinkwrap to its content? Here''s what I''m doing now: def create(*) self.height = maxChildHeight + 30 self.width = maxChildWidth + 10 super end This works, but I''m not crazy about manually adjusting for (apparently) frame and title bar sizes. -- vjoel : Joel VanderWerf : path berkeley edu : 510 665 3407

Hi Arnaud, Thanks for following up with that and sorry for the breakage. Couple of comments: MachineLoopInfo *MLI; + RegScavenger *RS; Would it make sense to use a unique_ptr here? That should eliminate the need of having explicit deletes. +; RUN: llc -mtriple=aarch64-linux-gnu -o - %s Add -enable-shrink-wrap=true and a second RUN line with -enable-shrink-wrap=false. Then add check lines

Hello, So, I have this testcase: void f(int n, int x[]) { if (n < 0) return; int a[n]; for (int i = 0; i < n; i++) a[i] = x[n - i - 1]; for (int i = 0; i < n; i++) x[i] = a[i] + 1; } that, compiled with -O1/-Os for AArch64 and X86, generates machine code, which fails to properly restore the stack pointer upon function return.

Hi Quentin, After shrink-wrapping was enabled as default on AArch64, llc has a seg fault when compiling the attached .ll file on AArch64. My command is llc -mcpu=cortex-a57 bug.ll Best, Haicheng -------------- next part -------------- A non-text attachment was scrubbed... Name: bug.ll Type: application/octet-stream Size: 8983 bytes Desc: not available URL:

Hello Momchil, (CC’ing more people that could correct me if I’m wrong) Thanks for looking into this. More answers below: > On 9 Apr 2018, at 17:57, Momchil Velikov via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello, > > So, I have this testcase: > > void f(int n, int x[]) { > if (n < 0) > return; > > int a[n]; >

Here is an updated patch for shrink wrapping with: - spills/restores done with stack slot stores/loads - stack adjustment removed - refactoring (but still in need of more) - spill/restore insertion code unified with spill/restore placement code Documentation available here<http://wiki.github.com/jdmdj/llvm-work/shrink-wrapping-work> illustrates shrink wrapping with loops and discusses a

On Mon, Mar 2, 2009 at 10:35 AM, Evan Cheng <echeng at apple.com> wrote: > > On Mar 1, 2009, at 2:57 PM, John Mosby wrote: > > Obviously, all of this applies only when spills are done with push/pop, > which is the case on x86. I used this issue to start looking at generalizing > how spills and restores are handled, before looking too closely at other > targets, and

...aring. Perhaps name it something like clearShrinkWrapData()? 5 +void PEI::placeSpillsAndRestores(MachineFunction &Fn) { + + DOUT << "Computing SAVE, RESTORE sets\n"; + + // If not shrink wrapping, all spills go into entry block, + // all restores in return blocks. + if (! ShrinkWrapping) { + // Do spills in the entry block. The shrink wrap version probably should go to its own function. Otherwise, it should exit early when the non-shrink wrapping version is done. That reduces nesting and please those of us who are a bit picky. 6. + // Save entry block, return block...

> On Dec 10, 2015, at 10:49 AM, Derek Schuff <dschuff at google.com> wrote: > > > > On Thu, Dec 10, 2015 at 10:13 AM Quentin Colombet <qcolombet at apple.com <mailto:qcolombet at apple.com>> wrote: > > I am tempted to think no, we don’t, but I don’t know the use cases. > What post-RA passes with want to run with virtual regs? > > The immediate

...on > splitting, function layout, function outlinling, profile driven size > optimization, induction variable optimization/strength reduction, stringOp > specialization/optimization/inlining, switch peeling/lowering etc. The > biggest profile user today include ralloc, BB layout, ifcvt, shrinkwrapping > etc, but there should be rooms to be improvement there too. > > > Thanks in advance! > > -- > Best Regards, > > Victor Leschuk | Software Engineer | Access Softek > > -- Best Regards, Victor Leschuk | Software Engineer | Access Softek ---------...

Dear everyone, The in-progress release notes for 3.7 [1,2] make it look like we didn't do very much over the past six months. Obviously that's not the case at all, so let's get them in shape! If you've been thinking "I should probably add this to the release notes at some point", now is the time :-) I have a list below of changes that might be worth mentioning. I

...on, inlining, function splitting, function layout, function outlinling, profile driven size optimization, induction variable optimization/strength reduction, stringOp specialization/optimization/inlining, switch peeling/lowering etc. The biggest profile user today include ralloc, BB layout, ifcvt, shrinkwrapping etc, but there should be rooms to be improvement there too. > Thanks in advance! > > -- > Best Regards, > > Victor Leschuk | Software Engineer | Access Softek > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pip...

Hello David! I have recently started acquaintance with PGO in LLVM/clang and found your e-mail thread: http://lists.llvm.org/pipermail/llvm-dev/2016-May/099395.html . Here you posted a nice list of optimizations that use profiling and of those which could be using but don't. However that thread is about 2 years old. Could you please kindly let me know if there were any significant changes in

...ion layout, function outlinling, profile driven size >> optimization, induction variable optimization/strength reduction, stringOp >> specialization/optimization/inlining, switch peeling/lowering etc. The >> biggest profile user today include ralloc, BB layout, ifcvt, shrinkwrapping >> etc, but there should be rooms to be improvement there too. >> >> >> Thanks in advance! >> >> -- >> Best Regards, >> >> Victor Leschuk | Software Engineer | Access Softek >> >> > > --...

> On Dec 10, 2015, at 9:39 AM, Hal Finkel <hfinkel at anl.gov> wrote: > > > > ----- Original Message ----- >> From: "Quentin Colombet" <qcolombet at apple.com> >> To: "Derek Schuff" <dschuff at google.com> >> Cc: "Hal Finkel" <hfinkel at anl.gov>, llvm-dev at lists.llvm.org >> Sent: Wednesday, December

...first. > 9. > + // If all uses of CSRegs are in the entry block, there is nothing > > > + // to shrink wrap: spills go in entry block, restores go in exiting > > > + // blocks, turn off shrink wrapping. > > > + if (allCSRUsesInEntryBlock) { > > > + ShrinkWrapping = false; > > > + DOUT << "All uses of CSRegs are in entry block, nothing to do.\n"; > > > + } > > > + // If we have decided not to shrink wrap, just return now. > > > + if (! ShrinkWrapping) > > > + return true; > > Why not...

...on > splitting, function layout, function outlinling, profile driven size > optimization, induction variable optimization/strength reduction, stringOp > specialization/optimization/inlining, switch peeling/lowering etc. The > biggest profile user today include ralloc, BB layout, ifcvt, shrinkwrapping > etc, but there should be rooms to be improvement there too. > > > >> Thanks in advance! >> >> -- >> Best Regards, >> >> Victor Leschuk | Software Engineer | Access Softek >> >> > > -- > Best Regards, > > Victor Leschuk | S...

...s are in the entry block, there is nothing >> >> >> +  // to shrink wrap: spills go in entry block, restores go in exiting >> >> >> +  // blocks, turn off shrink wrapping. >> >> >> +  if (allCSRUsesInEntryBlock) { >> >> >> +    ShrinkWrapping = false; >> >> >> +    DOUT << "All uses of CSRegs are in entry block, nothing to do.\n"; >> >> >> +  } >> >> >> +  // If we have decided not to shrink wrap, just return now. >> >> >> +  if (! ShrinkWrapping) &g...

I've paraphrased the OS X installer developer's comments: there's a bug in Installer that is preventing the archive from working right. Below is the fix for the problem. First (obviously) run the installer. Since the executables are in the archive.pax.gz file in the installer package, first do a "show package contents" on the package file, then unstuff the enclosed

...tting, function layout, function outlinling, profile driven size >> optimization, induction variable optimization/strength reduction, stringOp >> specialization/optimization/inlining, switch peeling/lowering etc. The >> biggest profile user today include ralloc, BB layout, ifcvt, shrinkwrapping >> etc, but there should be rooms to be improvement there too. >> >> >> >>> Thanks in advance! >>> >>> -- >>> Best Regards, >>> >>> Victor Leschuk | Software Engineer | Access Softek >>> >>> >> &gt...