On Oct 18, 2010, at 9:22 PM, leledumbo wrote:> >> let me say that in general doing this is pointless. Due to SSA form, if %x > is >> set to 5 you can't set it to something else later. Thus everywhere that >> you >> use %x you might as well just directly use 5 there instead. > > My bad... I should've started thinking in SSA way all the time. I got it > mixed with common assembly language. So I must hold the initial value until > the first operation that deals with it has come, right?No, you could throw it into a global if you know you're going to want to use 5 at some point in the future randomly. -eric
> No, you could throw it into a global if you know you're going to want touse 5 at some point in the future randomly. OK, I guess that's the way I should treat it. Load from global to register, do operations, store it back. -- View this message in context: http://old.nabble.com/How-to-assign-a-constant-to-a-register--tp29987387p30007489.html Sent from the LLVM - Dev mailing list archive at Nabble.com.
On Oct 20, 2010, at 12:52 AM, leledumbo wrote:>> >> No, you could throw it into a global if you know you're going to want to > use 5 at some point in the future randomly. > > OK, I guess that's the way I should treat it. Load from global to register, > do operations, store it back.I suppose, it'd be no different than doing this in a C file: static const int five = 5; and then using "five" all over the place instead of 5. Why not just use ConstantInt::get() when you want the number 5? -eric