search for: shrinkwrap

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. -- vjo...

...g fault when compiling the attached .ll file on AArch64. >>>>> >>>>> My command is >>>>> >>>>> llc -mcpu=cortex-a57 bug.ll >>>>> >>>>> Best, >>>>> >>>>> Haicheng > <0001-ShrinkWrap-Teach-ShrinkWrap-to-handle-targets-requir.patch>

...callee-saved register. The end effect is that placement of register save/restore code is such that along a certain path, the callee-saved registers and the stack pointer are restored, but then the stack pointer is overwritten with an incorrect value. I've "fixed" this by modifying `ShrinkWrap::useOrDefCSROrFI` to explicitly check for the stack pointer register (using `TLI.getStackPointerRegisterToSaveRestore`) and also to ignore tall call instructions (`isCall() && isReturn()`), since they implictly use SP (for AArch{32,64} at least). Does this look correct? Are there alternati...

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:

...> The end effect is that placement of register save/restore code is such that > along a certain path, the callee-saved registers and the stack pointer are > restored, but then the stack pointer is overwritten with an incorrect value. > > I've "fixed" this by modifying `ShrinkWrap::useOrDefCSROrFI` to explicitly check > for the stack pointer register (using > `TLI.getStackPointerRegisterToSaveRestore`) This part sounds ok to me. Can you put up a patch please? > and also to ignore tall call > instructions (`isCall() && isReturn()`), since they implictly...

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

...ot; + << getBasicBlockName(MBB) << "\n"; + } + // DEBUG Code like this should also be inside ifndef NDEBUG. 3. It can still use more refactoring. :-) 4. clearSets(). It's not clear what sets it's clearing. 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....

...his mail was PrologEpilogInserter. > However currently the only other pass we have disabled in WebAssemblyTargetMachine is MachineCopyPropagation. > Several passes (post-RA MachineLICM, StackSlotColoring) already only run if RA runs. > Everything else is running today. Currently that's ShrinkWrap, BranchFolder, ExpandPostRAPseudos, PostRAScheduler, GCMachineCodeAnalysis, MachineBlockPlacement, FuncletLayout, and StackMapLiveness. All of these run after our register coloring pass. I don’t know for the other passes, but I don’t think it makes sense to teach PrologEpilogInserter to work on vi...

...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 -----...

...es, etc? I stumbled across http://article.gmane.org/gmane.comp.compilers.llvm.devel/83858, for example Hal: the PowePC notes have a note saying "QPX - Hal, please say a few words" :-) Alex: I think MIR is new for 3.7. Do you want to add something to the notes? Quentin: How far did your shrinkwrap work get in 3.7? If it mostly landed after the branch, maybe add it to the 3.8 (trunk) notes. Alexey: Would you or someone of the OpenMP developers be willing to add a section on OpenMP to Clang's UsersManual.rst? It would be nice if the note in the release notes could point to this. Peter: 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...

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

...\n"; > > > + } > > > + // DEBUG > > Code like this should also be inside ifndef NDEBUG. > > 3. It can still use more refactoring. :-) > > 4. clearSets(). > It's not clear what sets it's clearing. Perhaps name it something like > clearShrinkWrapData()? > Agreed in toto, I will refactor further and try to get all remaining cleanups into the next patch. > 5 > +void PEI::placeSpillsAndRestores(MachineFunction &Fn) { > > > ... > > The shrink wrap version probably should go to its own function. Otherwise, > it...

...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...

...gt;> +      } >> >> >> +      // DEBUG >> Code like this should also be inside ifndef NDEBUG. >> 3. It can still use more refactoring. :-) >> 4.  clearSets(). >> It's not clear what sets it's clearing. Perhaps name it something like >> clearShrinkWrapData()? > > Agreed in toto, I will refactor further and try to get all remaining > cleanups into the next patch. > >> >> 5 >> +void PEI::placeSpillsAndRestores(MachineFunction &Fn) { >> >> >> ... >> The shrink wrap version probably should go...

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 >>> >>> >>...