search for: type_int

...quot;, + "SET_XATTR", + "REMOVE_XATTR", + "WRITE", + "CLONE", + "TRUNCATE", + "CHMOD", + "CHOWN", + "UTIMES", + "END" +}; +#define MAX_CMDS (sizeof(cmd_names) / sizeof(char *)) + +#define TYPE_UNDEF 0 +#define TYPE_INT 1 +#define TYPE_STRING 2 +#define TYPE_BINARY 3 +#define TYPE_TIME 4 +#define TYPE_HEX 5 +#define TYPE_OCTAL 6 +#define TYPE_LEN_ONLY 7 + +struct attr_types { + const char *name; + int type; +} attrs[] = { + { "UNSPEC", TYPE_UNDEF }, + { "UUID", TYPE_BINARY }, + { "CTRANSI...

...our > example, foo will have to treat its argument differently depending on > whether it is a GC pointer or not. In practice, this is not true of many functions that don't call other functions. Take the example of a simple "print" function that takes a void * to cast and print, type_int to determine what to cast to: why should it care about whether the pointer is GC'able or not? In the callsite, I have this information, and I accordingly emit statepoint/relocate information. But "print" doesn't call other functions, and doesn't need to emit statepoint/relocat...

Hello all, I'm trying to use the C API to initialize a global integer array with the address of another global, but ptrtoint yields an array instead of an integer. You can see a short program demonstrating the issue here (tested with LLVM 3.8.1 and 4.0.0svn-r280709 on Linux x86_64): https://raw.githubusercontent.com/dobyrch/dbc/master/llvm_bug/example.c Note that the use of ptrtoint in the

Hi, I just found out that it's not practical to mark only some pointers for GC. Consider: %a = i8 addrspace(1)* malloc(...) %b = i8* alloca(...) The issue then becomes that routine functions declared: declare i1 foo(i8 addrspace(1)*) have a choice of accepting either gc'able or non-gc'able pointers. Is there no way to have a reasonable mix of both? Ram

The following series implements libxl_domain_config_init as per the libxl API requirement that each type has an init function. The first function does this in an open coded manner and is proposed for Xen 4.2. The second function is RFC only since it moves the definition of this type into the IDL and makes the required infrastructure updates to enable this. I think this is more 4.3 material at

Hello, Third version of the NUMA placement series Xen 4.2. All the comments received during v2''s review have been addressed (more details in single changelogs). The most notable changes are the following: - the libxl_cpumap --> libxl_bitmap renaming has been rebased on top of the recent patches that allows us to allocate bitmaps of different sizes; - the heuristics for deciding