Displaying 5 results from an estimated 5 matches for "var_end".
Did you mean:
va_end
2012 Jul 05
0
[LLVMdev] Accessing Return Variable Names
...{
return "Return";
}
std::string name;
raw_string_ostream s(name);
s << *i; // string representation of an instruction
size_t var_start = name.find('%'); // var starts with a %
size_t var_end = name.find(" ", var_start+1); // till space
size_t var_comma = name.find(",", var_start+1); // or comma
return var_comma<var_end?
name.substr(var_start,var_comma-var_start) :
name.substr(var_start, var_...
2012 Jul 05
4
[LLVMdev] Accessing Return Variable Names
Hello,
I'm new to llvm development and I have a question which I think should
be straight forward, but I am having trouble figuring it out. I want to
be able to access the return variable name for an instruction. For some
instructions I can get this value through the "getName" method. For
example, with the instruction:
> %arg11 = bitcast i32* %arg1 to i8*, !dbg !42, !id
2008 Jun 20
1
Samba 4 alpha 4 with OpenLDAP
...names.serverdn
File "bin/python/samba/provision.py", line 185, in setup_modify_ldif
check_all_substituted(data)
File "bin/python/samba/__init__.py", line 227, in check_all_substituted
raise Exception("Not all variables substituted: %s" %
text[var_start:var_end+1])
Exception: Not all variables substituted: ${PREFIXMAP_B64}
Does anyone has any idea?
Thanks, chris
2023 Mar 25
4
[libnbd PATCH v5 0/4] pass LISTEN_FDNAMES with systemd socket activation
V4 was here (incorrectly versioned on the mailing list as v3):
<http://mid.mail-archive.com/20230323121016.1442655-1-lersek at redhat.com>.
See the Notes section on each patch for the v5 updates.
Laszlo Ersek (2):
socket activation: generalize environment construction
socket activation: set LISTEN_FDNAMES
Richard W.M. Jones (2):
common/include: Copy ascii-ctype functions from nbdkit
2023 Mar 23
20
[libnbd PATCH v3 00/19] pass LISTEN_FDNAMES with systemd socket activation
V3 was here:
<http://mid.mail-archive.com/20230215141158.2426855-1-lersek at redhat.com>.
See the Notes section on each patch for the v4 updates.
The series is nearly ready for merging: every patch has at least one R-b
tag, except "socket activation: avoid manipulating the sign bit".
The series builds, and passes "make check" and "make check-valgrind", at