search for: conisd

...f newcomers think {} is LLVM's spelling for C's void, they might be tempted to use {}* for C's void*, and nothing will stop them except mysterious bugs if they do arithmetic. On the purity side, replacing void with {} has the side effect of emphasising an odd asymmetry in the language. Conisder the return types of functions returning 0, 1, 2, and 3 etc. values: 0: {} 1: i32 2: {i32,i32} 3: {i32,i32,i32} etc. Why is 1 special-cased? Argument lists don't have a corresponding special case, after all. Dan

Hi! I need to convert a KVM virtual machine from LVM to a qcow2 image, and wonder if this is the best way to do it (*1): [$] qemu-img convert -O qcow2 /dev/vg_name/lv_name/ /var/lib/libvirt/images/image_name.qcow2 If this is the best way to do this, will this keep the information on: /dev/vg_name/lv_name/ untouched? Thanks, and please point me towards another mailing list if this it not right

Hello all, I am willing to do "eliminating the void type" project. Is there anyone working on it? === Overview === The general concept is to replaced void with {}. And 'ret void' is a synonym of 'ret {} {}.' === Further Implementation Details === 1. Deleting VoidTyID 2. Deleting LLVMVoidTypeKind (one-to-one relation between VoidTyID and LLVMVoidTypeKind) 3. Use

...ed? As long as you also reconfigure the VM to use /var/lib/libvirt/images/image_name.qcow2 after this point the old logical volume will not be used. The above approach is good if you are okay with some downtime on the VM while the image is converted over. There are a few other approaches you can conisder when you want to do it live or for example save some space in the qcow2 image by using fstrim first. For a live conversion, you can do an external disk-only snapshot first which creates a qcow2 overlay file: virsh snapshot-create-as $VMNAME --no-metadata --disk-only --diskspec $DISK,file=/path/...

...ly discover that there is a problem. Anyway, conceptually the idea is not to replace void with {}, it's to remove void because there are alternatives such as {}, {{}} etc. > On the purity side, replacing void with {} has the side effect of > emphasising an odd asymmetry in the language. Conisder the return > types of functions returning 0, 1, 2, and 3 etc. values: > > 0: {} > 1: i32 > 2: {i32,i32} > 3: {i32,i32,i32} > etc. > > Why is 1 special-cased? Argument lists don't have a corresponding > special case, after all. You could return one value as {i32}...