Displaying 6 results from an estimated 6 matches for "misneedschainedg".
Did you mean:
misneedschainedge
2013 Apr 16
2
[LLVMdev] alias analysis in backend
...e to for example get the result that two stack-accesses with different offsets (indexes), would return noAlias. However, I'm somewhat confused as there is no notion of offset for the Location object.
I would also like to call ScheduleDAGInstr::buildSchedGraph() with this AliasAnalysis and have MIsNeedsChainEdge() return false in this case.
What should I do? Adding a MemoryOperand to such an instruction seems right, but it doesn't seem to fit quite. What Value would be referenced? BasicAliasAnalysis returns MustAlias for the same Value, e g 'Stack'.
Should I implement a target AliasAnalysis,...
2013 Apr 16
0
[LLVMdev] alias analysis in backend
...hat two stack-accesses with different
> offsets (indexes), would return noAlias. However, I’m somewhat
> confused as there is no notion of offset for the Location object.
>
>
>
> I would also like to call ScheduleDAGInstr::buildSchedGraph() with
> this AliasAnalysis and have MIsNeedsChainEdge() return false in this
> case.
>
>
>
> What should I do? Adding a MemoryOperand to such an instruction seems
> right, but it doesn’t seem to fit quite. What Value would be
> referenced?
I think that they should have pseudo-source values, see: include/llvm/CodeGen/PseudoSou...
2013 Apr 17
2
[LLVMdev] alias analysis in backend
...t
> > offsets (indexes), would return noAlias. However, I'm somewhat
> > confused as there is no notion of offset for the Location object.
> >
> >
> >
> > I would also like to call ScheduleDAGInstr::buildSchedGraph() with
> > this AliasAnalysis and have MIsNeedsChainEdge() return false in this
> > case.
> >
> >
> >
> > What should I do? Adding a MemoryOperand to such an instruction seems
> > right, but it doesn't seem to fit quite. What Value would be
> > referenced?
>
> I think that they should have pseudo-sour...
2013 Apr 18
2
[LLVMdev] alias analysis in backend
...I'm somewhat
>>>> confused as there is no notion of offset for the Location object.
>>>>
>>>>
>>>>
>>>> I would also like to call ScheduleDAGInstr::buildSchedGraph()
>>>> with
>>>> this AliasAnalysis and have MIsNeedsChainEdge() return false in
>>>> this
>>>> case.
>>>>
>>>>
>>>>
>>>> What should I do? Adding a MemoryOperand to such an instruction
>>>> seems
>>>> right, but it doesn't seem to fit quite. What Value woul...
2013 Apr 17
0
[LLVMdev] alias analysis in backend
...oAlias. However, I'm somewhat
> > > confused as there is no notion of offset for the Location object.
> > >
> > >
> > >
> > > I would also like to call ScheduleDAGInstr::buildSchedGraph()
> > > with
> > > this AliasAnalysis and have MIsNeedsChainEdge() return false in
> > > this
> > > case.
> > >
> > >
> > >
> > > What should I do? Adding a MemoryOperand to such an instruction
> > > seems
> > > right, but it doesn't seem to fit quite. What Value would be
> > >...
2013 Apr 18
0
[LLVMdev] alias analysis in backend
...is no notion of offset for the Location
> >>>> object.
> >>>>
> >>>>
> >>>>
> >>>> I would also like to call ScheduleDAGInstr::buildSchedGraph()
> >>>> with
> >>>> this AliasAnalysis and have MIsNeedsChainEdge() return false in
> >>>> this
> >>>> case.
> >>>>
> >>>>
> >>>>
> >>>> What should I do? Adding a MemoryOperand to such an instruction
> >>>> seems
> >>>> right, but it doesn&...