Displaying 6 results from an estimated 6 matches for "explcitily".
Did you mean:
explicitily
2010 Jun 15
2
Unspecified [upper] xlim/ylim?
...n computing a "Ymax" to put in (say) ylim = c(0,Ymax). However,
for certain reasons, I would prefer not to have to do this.
(And it's just a preference ... ).
Whereas one can leave the whole issue of setting both plotting
limits to plot(), by not specifying ylim (or xlim), or one can
explcitily specify both the upper and lower limits by (say)
ylim=c(Ymin,Ymax), there seems to be no way of fixing one and
leaving the other floating so that plot() would do its own thing.
ylim requires two numbers to be given. Things like ylim=c(0,)
or ylim=c(0,NA) would generate an error.
Am I chasing a ph...
2009 Jan 27
3
[LLVMdev] Hitting assertion, unsure why
...ScheduleDAG::EmitNode has a FrameIndex as its second operand. This is
especially problematic because the code is either expecting a
VirtualRegister or a RegisterSDNode in this location. I've checked all
locations where I use the DAG.getCopyToReg function and none of them
pass in a frameindex. I explcitily check that I have a register before
passing in the value to Register number to CopyToReg, so this leads me
to believe that it is being generated somehow by LLVM.
In the case I sent earlier in this thread it only occurs when I turn
optimizations on, but the new case I hit with optimizations off bu...
2009 Jan 28
0
[LLVMdev] Hitting assertion, unsure why
...on't think anyone can help you until you can track
down what is creating the FrameIndex. Why not set a break point in
MachineFrameInfo::CreateFixedObject and CreateStackObject?
Evan
>
> locations where I use the DAG.getCopyToReg function and none of them
> pass in a frameindex. I explcitily check that I have a register before
> passing in the value to Register number to CopyToReg, so this leads me
> to believe that it is being generated somehow by LLVM.
>
> In the case I sent earlier in this thread it only occurs when I turn
> optimizations on, but the new case I hit wi...
2009 Jan 15
0
[LLVMdev] Hitting assertion, unsure why
Other than not using debugging ('-g' and the like), not really. :-( I
think that Devang is actively working on fixing this, though. It might
not be too much longer.
-bw
On Thu, Jan 15, 2009 at 3:26 PM, Villmow, Micah <Micah.Villmow at amd.com> wrote:
> This did not seem to work, any other ideas?
>
> Thanks,
>
> -----Original Message-----
> From: llvmdev-bounces at
2009 Jan 30
1
[LLVMdev] Hitting assertion, unsure why
...on't think anyone can help you until you can track
down what is creating the FrameIndex. Why not set a break point in
MachineFrameInfo::CreateFixedObject and CreateStackObject?
Evan
>
> locations where I use the DAG.getCopyToReg function and none of them
> pass in a frameindex. I explcitily check that I have a register before
> passing in the value to Register number to CopyToReg, so this leads me
> to believe that it is being generated somehow by LLVM.
>
> In the case I sent earlier in this thread it only occurs when I turn
> optimizations on, but the new case I hit wi...
2009 Jan 15
2
[LLVMdev] Hitting assertion, unsure why
This did not seem to work, any other ideas?
Thanks,
-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
On Behalf Of Bill Wendling
Sent: Thursday, January 15, 2009 2:26 PM
To: LLVM Developers Mailing List
Subject: Re: [LLVMdev] Hitting assertion, unsure why
Don't generate debug info at this time (you can use "opt
-strip-debug")?