Displaying 5 results from an estimated 5 matches for "register_s".
Did you mean:
registers
2005 Sep 07
1
[LLVMdev] LiveIntervals invalidates LiveVariables?
On 08/09/05, Alkis Evlogimenos <evlogimenos at gmail.com> wrote:
> to those coalesced registers, it is logical that noone will ever query
> the liveness of those registers (unless there is a bug somewhere in the
Indeed the coalesced registers may logically not be queried since they
do not appear in any operand list of the machine code, but the
VarInfo::DefInst in VirtRegInfo of the
2005 Sep 07
0
[LLVMdev] LiveIntervals invalidates LiveVariables?
On Wed, 2005-09-07 at 18:24 +0800, Tzu-Chien Chiu wrote:
> I though LiveVariables may be invalidated by LiveIntervals, but it's
> declared not:
>
> void LiveIntervals::getAnalysisUsage(AnalysisUsage &AU) const
> {
> AU.addPreserved<LiveVariables>();
> AU.addRequired<LiveVariables>();
> ...
>
> LiveInterval may coalesce virtual registers and
2005 Sep 07
3
[LLVMdev] LiveIntervals invalidates LiveVariables?
I though LiveVariables may be invalidated by LiveIntervals, but it's
declared not:
void LiveIntervals::getAnalysisUsage(AnalysisUsage &AU) const
{
AU.addPreserved<LiveVariables>();
AU.addRequired<LiveVariables>();
...
LiveInterval may coalesce virtual registers and remove identity moves
instructions:
bool LiveIntervals::runOnMachineFunction(MachineFunction &fn) {
2018 Apr 10
1
How to finalize instruction lowering after register allocation.
Hi,
I've some problems/questions while implementing the BUILD_VECTOR primitive for a SIMD microcontroller...
This microcontroller has two FPU units: UnitA and UnitB.
UnitA has a bank of 512 registers named RegisterA_0 .. RegisterA_511.
UnitB has a bank of 512 registers named RegisterB_0 .. RegisterB_511.
The FPU instruction format has a 2 bits operand indicating which units are involved:
2013 Nov 05
1
[LLVMdev] Multimedia IO instructions & partial backend implementations for simple CPUs
On 3 November 2013 05:44, Sean Silva <chisophugis at gmail.com> wrote:
> LLVM doesn't provide a runtime or "VM". You basically do these things the
> same way that you do them in C. Yes, this unfortunately requires knowing
> your target platform's system libraries and how to link to them and such;
> LLVM doesn't paper over this.
OK. So to be specific, I am