search for: reg_mapping

...// It was not possible to fold the spill into the // instruction: a register must be fond. if(seen_regs.find(v_reg) != seen_regs.end()) { continue; } else { seen_regs.insert(v_reg); } unsigned p_reg = reg_mapping->get_free_register(v_reg); if(p_reg != RegMapping_Fer::NO_REG) { this->reg_mapping->allocate_color(v_reg, p_reg); } else { // unused register may conflict with this virtual, because // they may be pre-colored, for instance....

...eg, KillingSites_Fer & ks, const MachineBasicBlock & mbb ) { // First, find a place to store this register. Of course, this will be done // by the implementation of vrm. We just have to ask it. int slot = vrm->assignVirt2StackSlot(v_reg); unsigned p_reg = this->reg_mapping->get_physical_location(v_reg); // Now, it is necessary to break the live range of the spilled register. // This is done by creating new virtual registers, and substituting the // spilled register by the new registers. MachineInstr * last_seen; std::vector< MachineInstr *...

...sible to fold the spill into the > // instruction: a register must be fond. > if(seen_regs.find(v_reg) != seen_regs.end()) { > continue; > } else { > seen_regs.insert(v_reg); > } > unsigned p_reg = reg_mapping->get_free_register(v_reg); > if(p_reg != RegMapping_Fer::NO_REG) { > this->reg_mapping->allocate_color(v_reg, p_reg); > } else { > // unused register may conflict with this virtual, because > // they may be pre-col...

So what addIntervalsToSpills returns are new intervals to allocate with infinite weights, right? And I need not to allocate the old interval. Should hasStackSlot return true on its register then? On 8/21/06, Fernando Magno Quintao Pereira <fernando at cs.ucla.edu> wrote: > > > Well, someone correct me if am wrong, but, you still have to allocate > physical registers to them,

On Aug 13, 2006, at 11:16 PM, Fernando Magno Quintao Pereira wrote: > > Dear LLVMers, > > I am trying to fold memory operands in the way that is done in > RegAllocLocal.cpp, or in LiveIntervalAnalysis.cpp, but I am getting > errors > that > I don't know how to fix. Could someone tell me which steps should I > take > in order > to correctly fold memory

Dear LLVMers, I am trying to fold memory operands in the way that is done in RegAllocLocal.cpp, or in LiveIntervalAnalysis.cpp, but I am getting errors that I don't know how to fix. Could someone tell me which steps should I take in order to correctly fold memory operands? The code that I am using is: const TargetMachine & target_machine = this->machine_function->getTarget();

...ks, > const MachineBasicBlock & mbb > ) { > // First, find a place to store this register. Of course, this will be > done > // by the implementation of vrm. We just have to ask it. > int slot = vrm->assignVirt2StackSlot(v_reg); > unsigned p_reg = this->reg_mapping->get_physical_location(v_reg); > > // Now, it is necessary to break the live range of the spilled > register. > // This is done by creating new virtual registers, and substituting > the > // spilled register by the new registers. > MachineInstr * last_seen; >...

The Wine development release 1.3.6 is now available. What's new in this release (see below for details): - Support for GStreamer filters. - Mapping of standard cursors to native desktop cursors. - Improved support for installers with services. - Many MSXML improvements. - Decoder for TGA-format images. - Translation updates. - Various bug fixes. The source is available from the

The Wine development release 1.3.9 is now available. What's new in this release (see below for details): - Beginnings of support for ActiveX in built-in browser. - Icons on Internet shortcut menu entries. - Standardization of code implementing COM interfaces. - New scheme for auto-generated DLL registrations. - OpenCL library wrapper. - Translation updates. - Various bug fixes.

The Wine development release 1.1.21 is now available. What's new in this release (see below for details): - Beginnings of shader model 4 support. - Support for copying/pasting images from X11 applications. - A number of GDIPlus improvements. - Various listview fixes. - 64-bit support in winemaker. - Support for building on Mac OS X Snow Leopard. - Various bug fixes. The source

The Wine development release 1.1.24 is now available. What's new in this release (see below for details): - Support for freedesktop file associations. - Support for exception handling on 64-bit. - Improved ARB shaders. - Fixes for the FBO mode. - Many listview improvements. - Various bug fixes. The source is available from the following locations:

The Wine development release 1.1.25 is now available. What's new in this release (see below for details): - A ton of translation updates. - Support for various Unicode file encodings in Notepad. - Improved memory management, especially for OpenGL. - Desktop menus now cleaned up automatically. - Beginnings of a windowscodecs DLL implementation. - Various bug fixes. The source is

The Wine development release 1.1.11 is now available. What's new in this release (see below for details): - Numerous fixes for IE7 support. - Support for 64-bit cross-compile using Mingw64. - User interface support for crypto certificates. - Better support for MSI installation patches. - Various Direct3D optimizations. - Various bug fixes. The source is available from the