Displaying 8 results from an estimated 8 matches for "type_block".
2016 Oct 13
2
Status of docs/BitCodeFormat.rst?
I think it just changed formats which prompted a change in ID -- the code now uses TYPE_BLOCK_ID_NEW (= 17). I haven’t looked deeply to see how different it is.
Ismail
> On Oct 13, 2016, at 2:02 PM, Mehdi Amini <mehdi.amini at apple.com> wrote:
>
>
>> On Oct 13, 2016, at 10:24 AM, Ismail Badawi (ibadawi) via llvm-dev <llvm-dev at lists.llvm.org> wrote:
>>...
2016 Oct 13
4
Status of docs/BitCodeFormat.rst?
...has been outdated for 5+ years.
Assuming there is an interest, I’m also wondering whether (or how) to approach fixing this incrementally. For example, in trying to document the new paramattr format, I noticed that the type format is also outdated, and there is a conflict in block ids (i.e. the old TYPE_BLOCK format which is documented used blockid=10, but blockid=10 is now used for PARAMATTR_GROUP_BLOCK), so that fixing the paramattr docs on their own might introduce inconsistencies. Would it be better to try & bring the whole document up to date at once, or would it be fine to do it incrementally...
2010 May 20
1
[LLVMdev] [PATCH] More BitCodeFormat.html improvements
The enclosed patch adds documentation for the PARAMATTR_BLOCK, TYPE_BLOCK,
and TYPE_SYMTAB_BLOCK records in the LLVM IR bitcode format.
I have started documenting CONSTANTS_BLOCK and FUNCTION_BLOCK and will send
patches when they are complete.
-Peter-
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermai...
2007 Oct 08
1
[LLVMdev] patch to docs/BitCodeFormat.html
I wrote in a few weeks ago about writing an independent
implementation of Bitcode and updating the docs to be more complete.
Attached is a patch to docs/BitCodeFormat.html that adds a lot of
information that was previously only available by reading the source
code. It also corrects some errors.
Josh
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Dec 21
1
[PATCH] snapshot: Explicitly remove unused disk source attribute
...t/v2v-snapshot.pl b/snapshot/v2v-snapshot.pl
index f089a77..e2cc33c 100755
--- a/snapshot/v2v-snapshot.pl
+++ b/snapshot/v2v-snapshot.pl
@@ -529,8 +529,10 @@ sub _commit_guest
# Update the domain XML with the location of the backing store
if($backing_type == Sys::Virt::StorageVol::TYPE_BLOCK) {
$source->setAttribute('dev', $backing_path);
+ $source->removeAttribute('file');
} else {
$source->setAttribute('file', $backing_path);
+ $source->removeAttribute('dev');
}
#...
2010 Mar 31
3
[PATCH] Remove v2v-snapshot
...g store isn't in a storage pool
- if($@) {
- # Guess based on path name
- # N.B. We could stat it, but that wouldn't work for a remote
- # connection
- if($backing_path =~ m{^/dev/}) {
- $backing_type = Sys::Virt::StorageVol::TYPE_BLOCK;
- } else {
- $backing_type = Sys::Virt::StorageVol::TYPE_FILE;
- }
- }
-
- # Update the domain XML with the location of the backing store
- if($backing_type == Sys::Virt::StorageVol::TYPE_BLOCK) {
- $source->setAttribute('...
2010 Sep 21
1
[PREVIEW ONLY] Refactor data transfer code
...olume/target/format/@type');
- $format = $format->getValue() if (defined($format));
- $format ||= 'auto';
-
- return $format;
-}
-
-sub is_block
-{
- my $self = shift;
-
- my $type = $self->{vol}->get_info()->{type};
- return $type == Sys::Virt::StorageVol::TYPE_BLOCK;
-}
-
-sub open
-{
- my $self = shift;
-
- my $path = $self->get_path();
-
- # We want to open the existing volume without truncating it
- sysopen(my $fd, $path, O_WRONLY)
- or die(user_message(__x("Error opening storage volume {path} ".
-...
2010 Mar 30
3
[PATCH 1/2] Refactor guest and volume creation into Sys::VirtV2V::Target::LibVirt
...olume/target/format/@type');
+ $format = $format->getValue() if (defined($format));
+ $format ||= 'auto';
+
+ return $format;
+}
+
+sub is_block
+{
+ my $self = shift;
+
+ my $type = $self->{vol}->get_info()->{type};
+ return $type == Sys::Virt::StorageVol::TYPE_BLOCK;
+}
+
+sub open
+{
+ my $self = shift;
+
+ my $path = $self->get_path();
+ open(my $fd, '>', $path)
+ or die(user_message(__x("Error opening storage volume {path} ".
+ "for writing: {error}", error => $!)));
+
+...