search for: physregtrack

...sting LLVM code). Usually, one does smth special with one register and some other thing for every aliased reg. Probably, register allocator would be broken or at least there would be one unnecessary action each time smth's done with alias set. For example, when you set some reg being used via a PhysRegTracker object, it automagically checks for every aliased reg and marks it being used, too. If the queried reg was included, PhysRegTracker could mark the specified reg twice and so on. Though the changes necessary to handle this don't seem too difficult at first glance. I know RegAllocLinearScan.cp...

I notice that in X86GenRegisterInfo.inc, the AliasSets do not include the register being queried. For example: const unsigned RAX_AliasSet[] = { X86::EAX, X86::AX, X86::AL, X86::AH, 0 }; const unsigned EAX_AliasSet[] = { X86::RAX, X86::AX, X86::AL, X86::AH, 0 }; This makes it hard to do set comparisons. RAX and EAX really have equivalent alias sets but one wouldn't know that from

...vePath="..\..\include\llvm\CodeGen\MachineInstrBuilder.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\CodeGen\Passes.h"> > > </File> > > <File > > RelativePath="..\..\lib\CodeGen\PhysRegTracker.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\CodeGen\SchedGraphCommon.h"> > > </File> > > <File > > RelativePath="..\..\include\llvm\CodeGen\SelectionDAG.h"> > >...

...t; <File > RelativePath="..\..\include\llvm\CodeGen\MachineInstrBuilder.h"> > </File> > <File > RelativePath="..\..\include\llvm\CodeGen\Passes.h"> > </File> > <File > RelativePath="..\..\lib\CodeGen\PhysRegTracker.h"> > </File> > <File > RelativePath="..\..\include\llvm\CodeGen\SchedGraphCommon.h"> > </File> > <File > RelativePath="..\..\include\llvm\CodeGen\SelectionDAG.h"> > </File> > <File >...