similar to: [LLVMdev] df_ext_iterator in LiveIntervalAnalysis

On Thu, 21 Jun 2007, Fernando Magno Quintao Pereira wrote: > I would like to make a suggestion. In the LiveIntervalAnalysis class, > instead of numbering the instructions in the order in which basic blocks > are stored in the machine function, use the df_ext_iterator. It will order > the instruction according to the dominance tree (or it seems to be doing > so). There are many

Nice idea. Please also try using SmallPtrSet (with a sufficiently large size) instead of std::set for traversal after everything is working. Using std::set can really hurt compile time in case of large basic block numbers. Is there a way to dynamically adjust "SmallSize" based on number of basic blocks in the function? Evan On Jun 21, 2007, at 10:20 PM, Fernando Magno Quintao

Hi, Just my two cents: If I recall correctly, in some papers on the linear scan register allocation people described that they tried different orderings for instruction numbering, e.g. including DFS or based on the loop nesting levels, etc. There was no clear winner though. But let's see the numbers anyway. May be it really brings some improvements. -Roman Chris Lattner wrote: > On

Hi, In the LiveIntervalAnalysis::runOnMachineFunction, there is a code to compute the MBB2IdxMap, by remembering for each MBB its start and end instruction numbers: unsigned MIIndex = 0; for (MachineFunction::iterator MBB = mf_->begin(), E = mf_->end(); MBB != E; ++MBB) { unsigned StartIdx = MIIndex; for (MachineBasicBlock::iterator I = MBB->begin(), E =

Hi I'm seeing something probably related to this. I'm getting an assert from the lower_bound in LiveIntervals::findLiveinMBBs (from a checking std:: VS2005 implementation). Idx2MBBMap has two elements in it, both of which have a .first of 0. (I believe because of an empty MBB in the function below, so StartIndex doesn't advance). scott On Wed, Apr 16, 2008 at 2:52 AM, Roman

Can you file a bug so I don't forget? I'm a little occupied right now. But I'll take care of this soon. Evan On Apr 16, 2008, at 10:52 AM, Scott Graham wrote: > Hi > > I'm seeing something probably related to this. I'm getting an assert > from the lower_bound in LiveIntervals::findLiveinMBBs (from a checking > std:: VS2005 implementation). Idx2MBBMap has two

Hi, I am writing an llvm pass wherein I require to iterate MachineBasicBlocks in reverse. The ilist reverse_iterator is not functioning as expected. Nor is the ilist iterator working in reverse (although -- operator is overloaded to do so). for (MachineFunction::iterator MBBI = mf_->end(), E = mf_->begin();MBBI != E; --MBBI) { MachineBasicBlock *MBB = MBBI;

Hello, We have a number of systems running KM400 chipsets from VIA (Socket A/462). Two different models have produced the same results -- DFI KM400-MLV and MSI KM4M-V. When a /sbin/reboot or /sbin/shutdown -r now is issued, the system does everything you would expect from a reboot, but when it gets to Rebooting System, it hangs and requires a power cycle. The logs do not indicate anything

I need you help with this problem, I have a data-frame like this: BHID=c(43,43,43,43,44,44,44,44,44) FROM=c(50.9,46.7,44.2,43.1,52.3,51.9,49.3,46.2,42.38) TO=c(46.7,44.2,43.1,40.9,51.9,49.3,46.2,42.38,36.3) AR=c(45,46,0.0,38.45,50.05,22.9,0,25,9) DF<-data.frame(BHID,FROM,TO,VALUE) #add the length DF$LENGTH=DF$FROM-DF$TO where: + BHID: is the borehole

I've only recently started using R. One of the problems I come up against is after having extracted a large dataset (>5M rows) out of database, I realize I need another variable. In this case I have data frame with dates. I want to find the minimum date for each value of x1 and add that minimum date to my data.frame. > randomdf <- function(p) { data.frame(x1=sample(1:10^4, 10^p,

Chris Lattner wrote: > On Thu, 12 Apr 2007, David Greene wrote: >> As I work toward improving LLVM register allocation, I've >> come across the need to do some refactoring. > > cool. :) One request: Evan is currently out on vacation until Monday. > This is an area that he is very interested in and will want to chime in > on. Please don't start anything

Hi all, I am currently planning a new home file server on a gigabit network that will be utilizing ZFS (on SXDE). The files will be shared via samba as I have a mixed OS environment. The controller card I will be using is the SuperMicro SAT2-MV8 133MHz PCI-X card. I have two options for CPUs/motherboards: AMD Athlon64 3000+ (64 bit) DFI LanParty UT 250gb (NForce 3 based) motherboard 32 bit

On Mar 1, 2014, at 7:15 PM, Chandler Carruth <chandlerc at google.com> wrote: > On Sat, Mar 1, 2014 at 5:59 PM, Duncan P. N. Exon Smith <dexonsmith at apple.com> wrote: > The current guidelines [1] on the use of the struct keyword are too > restrictive and apparently ignored. They limit the use of struct to > PODs, citing broken compilers. > > The guidelines are

Hi, guys, sometimes it would be good if I could get the maximum instruction index from the set of live intervals. In my local version I have added this method to LiveIntervals: /// Return the maximum index among the instruction indices. inline unsigned getMaxInstrIndex() const { return i2miMap_.size() * InstrSlots::NUM; } Is there something like this already in LiveIntervals? Do you

On Thu, 12 Apr 2007, David Greene wrote: > As I work toward improving LLVM register allocation, I've > come across the need to do some refactoring. cool. :) One request: Evan is currently out on vacation until Monday. This is an area that he is very interested in and will want to chime in on. Please don't start anything drastic until he gets back :). > Specifically, I would

Hi again, 2009/1/13 Evan Cheng <evan.cheng at apple.com>: > > > On Jan 13, 2009, at 12:27 AM, Roman Levenstein <romix.llvm at googlemail.com> > wrote: > >> 2009/1/13 Evan Cheng <echeng at apple.com>: >>> >>> On Jan 7, 2009, at 2:48 AM, Roman Levenstein wrote: >>> >>>> bb368: 0x8fdad00, LLVM BB @0x8fc2c98, ID#1:

Hi Evan, Here is a patch for the LiveIntervalAnalysis that we discussed. --- Evan Cheng <evan.cheng at apple.com> schrieb: > > 1) What is the easiest way to understand which MBB a given > instruction index belongs to? All the required information is > available in the > > MBB2IdxMap of the LiveIntervalAnalysis class. Would it be useful > to add a small function

Hi list! I am running CentOS 4.1 x86_64 on an Athlon64. The box was installed only yesterday. Yesterday I was still able to compil stuff, yesterday even the tiniest and simplest programs fail to compile always with internal compiler error: Segmentation fault. For example: make -C /usr/src/linux-2.6 SUBDIRS=/tmp/bristuff-0.2.0-RC8n/qozap ZAP=-I/tmp/bristuff-0.2.0-RC8n/zaptel-1.0.9 modules

Hi all, As I work toward improving LLVM register allocation, I've come across the need to do some refactoring. Specifically, I would like to separate register coalescing from live interval analysis. Right now LiveIntervals handles both. The reason I want to separate them is that other types of register allocators might like to do coalescing differently (e.g. graph coloring does it by

On Apr 19, 2005, at 23:17, Vikram Adve wrote: > Have you looked at ExtractCodeRegion() and its siblings in > include/llvm/Transform/Utils/FunctionUtils.h? It seems to be what you > need. This is brilliant. In fact, it is nearly *exactly* what I need. On Apr 19, 2005, at 23:59, Chris Lattner wrote: > An Interval (and an Interval partition) is a concept with a lot of > compiler