Displaying 5 results from an estimated 5 matches for "exapndintegeroperand".
2009 Jan 16
2
[LLVMdev] PIC16 backend for llvm 2.5
...erm. But currently I suggest that "Results" be the last
argument to LowerOperation() which is defaulted to NULL. That way
LegalizeDAG and all targets will continue to work the current way, plus
targets like ours that want to use the last argument (i.e. "Results")
can use them in ExapndIntegerOperand().
Let me know if that sounds okay.
Regards,
Sanjiv
> Ciao,
>
> Duncan.
2009 Jan 16
0
[LLVMdev] PIC16 backend for llvm 2.5
...suggest that "Results" be the last
> argument to LowerOperation() which is defaulted to NULL. That way
> LegalizeDAG and all targets will continue to work the current way, plus
> targets like ours that want to use the last argument (i.e. "Results")
> can use them in ExapndIntegerOperand().
do you need this for operation legalization (LegalizeDAG) as well as
type legalization? If not, then you can introduce a new method like
ReplaceNodeResults for custom type legalization of operands (or just
use ReplaceNodeResults for this too - I don't immediately see any
reason why not), a...
2009 Jan 09
0
[LLVMdev] PIC16 backend for llvm 2.5
Hi Sanjiv,
> Well, the first email is here.
>
> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20081013/068667.html
thanks, I remember now (more or less). So would something like ReplaceNodeResults
solve the problem?
Ciao,
Duncan.
2009 Jan 09
3
[LLVMdev] PIC16 backend for llvm 2.5
Well, the first email is here.
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20081013/068667.html
-----Original Message-----
From: Duncan Sands [mailto:baldrick at free.fr]
Sent: Thu 1/8/2009 8:41 PM
To: Sanjiv Kumar Gupta - I00171
Cc: llvmdev at cs.uiuc.edu
Subject: Re: PIC16 backend for llvm 2.5
Hi Sanjiv,
> We are targetting a reasonably functional PIC16 backend for llvm
2009 Jan 18
2
[LLVMdev] PIC16 backend for llvm 2.5
...Results" be the last
> > argument to LowerOperation() which is defaulted to NULL. That way
> > LegalizeDAG and all targets will continue to work the current way, plus
> > targets like ours that want to use the last argument (i.e. "Results")
> > can use them in ExapndIntegerOperand().
>
> do you need this for operation legalization (LegalizeDAG) as well as
> type legalization? If not, then you can introduce a new method like
> ReplaceNodeResults for custom type legalization of operands (or just
> use ReplaceNodeResults for this too - I don't immediately s...