Displaying 6 results from an estimated 6 matches for "levo".
Did you mean:
leo
2005 Oct 10
1
labels of a conditioning variable in xyplot
...ac g5 under Mac OS 10.4.2.
I have an xyplot with a single conditioning variable (8 levels) .
Here is the code for the conditioning variable used in the formula
argument of xyplot:
factor(
drugauthoryear,
levels = c(
'bupicapogna1999',
'levobenhamou2003',
'ropicapogna1999',
'ropipolley1999',
'bupipolley1999',
'levopolley2003',
'ropibenhamou2003',
'ropipolley2003'
),
labels = c(
'Bupi. Re...
2020 Feb 15
2
Have the debugger show an away with a dynamic size?
...] = 0
[76] = -8208
[77] = 32767
[78] = 4195290
[79] = 0
[80] = -8216
}
On Thu, Feb 13, 2020 at 3:53 PM Adrian Prantl <aprantl at apple.com> wrote:
> Take a look at the IR clang produces for C99 variable-length arrays.
>
> -- adrian
>
> On Feb 13, 2020, at 10:03 AM, Levo DeLellis via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
>
> Hi. I searched and the closest thing I could find was this
> http://lists.llvm.org/pipermail/llvm-dev/2018-February/121348.html
>
> Currently a known sized array looks and debugs as expected. I use
> llvm.db...
2019 Oct 16
2
Most efficient way for a function to return two types?
I apologize if this is the wrong list. I'm writing a language and
outputting llvm-ir instead of using the c api. I looked at clang's output a
few times but I'm a little unsure what to do in this case
As an example I have a function called itoa which takes an int and returns
a string. Strings in my language has 2 fields, the pointer and byte length.
On a 64bit machine it'd be
2018 Apr 18
1
[cfe-users] How to handle debug information not in source/How do I handle the error 'inlinable function call in a function with debug info must have a !dbg location'
+llvm-dev, Adrian
bcc:cfe-users
> On Apr 18, 2018, at 14:20, Levo DeLellis via cfe-users <cfe-users at lists.llvm.org> wrote:
>
> I'm having an issue with the error "inlinable function call in a function with debug info must have a !dbg location"
>
> My language will automatically call a destructor for you. LLVM is forcing me to...
win-xp guest after reboot: could not open disk image /dev/sr0: mo medium found and extreme sluggisch
2012 May 29
1
win-xp guest after reboot: could not open disk image /dev/sr0: mo medium found and extreme sluggisch
Hi,
win-xp won't boot after installation. The CD is needed to boot from. How can I
convince win-xp to boot?
That's what I did:
==================
I installed win-xp guest on debian squeeze:
# virt-install --connect qemu:///system --name winxp-prof --ram 1024 \
--disk path=/dev/vg-levo/winxp-kvm,size=10 \
--network bridge:br0 --vnc --os-variant winxp --cdrom /dev/sr0
/dev/vg-levo/winxp-kvm is a lvm (logical volume, 10GB)
Installation worked, but was extrem slow. Machine: Lenovo B560, core i3, 6 GB RAM.
WinXP made a normal reboot after installation, I ejected install cd, then:...
2020 Feb 13
3
Have the debugger show an away with a dynamic size?
Hi. I searched and the closest thing I could find was this
http://lists.llvm.org/pipermail/llvm-dev/2018-February/121348.html
Currently a known sized array looks and debugs as expected. I use
llvm.dbg.declare with DICompositeType tag: DW_TAG_array_type and the size
field. In my language arrays are always passed around with a pointer and
size pair. I'd like debugging to show up as nicely