similar to: [LLVMdev] What's the meaning of [0 x sbyte*]?

My pass has to call one function of a binary library. But when opt loads my pass, it tells me that the function is "undefined symbol". I copy the library to /usr/lib, and run ldconfig, but this is unuseful. Should I modify the Makefile? :( Thanks. Xia -------------------------------------------------------------------------------------AOC(冠捷)17寸液晶16ms￥2888

On 10/1/19 9:11 AM, Richard W.M. Jones wrote: > On Tue, Oct 01, 2019 at 08:24:33AM -0500, Eric Blake wrote: >>> +#else /* !HAVE_EXECVPE */ >>> + SET_NEXT_STATE (%.DEAD) >>> + set_error (ENOTSUP, "platform does not support socket activation"); >>> + return 0; >>> +#endif >> >> We probably ought to add a matching

Hi guys... Just wanted to see what is so different in BSD from Linux and had a quick look at the openbsd-compat directory (openssh-2.5.1p1). There is a REALLY obvious bug in bsd-misc.c, quoted below: #if !defined(HAVE_STRERROR) && defined(HAVE_SYS_ERRLIST) && defined(HAVE_SYS_NERR) const char *strerror(int e) { extern int sys_nerr; extern char *sys_errlist[];

Hello, I got a strange result when I used alias analysis DSAA, can you tell what is wrong? 1. The following is the primary body of my pass "fps.cpp": AliasAnalysis *AA = &getAnalysis<AliasAnalysis>(); AliasSetTracker AST(*AA); for (Module::iterator fi = M.begin(), fe = M.end(); fi != fe; ++fi ) for (Function::iterator bi = fi->begin(), be = fi->end(); bi

Dear R-help mailing list, I have a drawing problem with R: I need to draw an horizontal axis with date, here is the test code: > ticks <- c("2004-01-22","2005-01-22","2006-01-22","2007-01- 22","2008-01-22","2009-01-22","2010-01-22","2011-01-22","2012-01-22") > ats <-

Yes! I should have looked this some days before, but I forgot it just now :). thanks. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040817/95dd9fff/attachment.html>

Oh, your meaning is pointers in a aliasset have equal address logically? But I think that two pointers are alias means they point to a same memory object, so if pointers "p" and "q" are alias, it seem as p = q, not &p = &q. Another question is about "forwarding". "AliasSet[XXXX, 0] may alias, Mod/Ref forwarding to YYYY" (XXXX != YYYY) means the

perror is not fork-safe and so could deadlock. Instead open code a fork-safe version of perror. While this fixes the current behaviour, in the long term we'd like to capture the error message into the usual error mechanism, so this is not the full and final fix for this issue. Also this fixes the exit code to be 126/127 instead of 1. Thanks: Eric Blake --- TODO | 1

v1 was posted here: https://www.redhat.com/archives/libguestfs/2019-September/thread.html#00337 v2: - Drop the first patch. - Hopefully fix the multiple issues with fork-safety and general behaviour on error paths. Note this requires execvpe for which there seems to be no equivalent on FreeBSD, except some kind of tedious path parsing (but can we assign to environ?) Rich.

On 9/30/19 11:32 AM, Richard W.M. Jones wrote: > perror is not fork-safe and so could deadlock. Instead open code a > fork-safe version of perror. While this fixes the current behaviour, > in the long term we'd like to capture the error message into the usual > error mechanism, so this is not the full and final fix for this issue. > > Also this fixes the exit code to be

Hi. SunOS 4 is one system that relies on the strerror() in bsd-misc.[ch]. However, that replacement function does not have the right prototype. This is fixed in the patch below. There was also an error with sys_errlist not being explicitely declared. Also fixed. There was another weird link-time problem with bsd-misc.o being at the same time used by some *.o in libssh.a and using itself

On 9/30/19 11:32 AM, Richard W.M. Jones wrote: > This adds new APIs for running a local NBD server and connecting to it > using systemd socket activation (instead of stdin/stdout). > > This includes interop tests against nbdkit and qemu-nbd which I > believe are the only NBD servers supporting socket activation. (If we > find others then we can add more interop tests in

Hi, I have some problem with running testsuites for samba. I use the dejaGNU 1.4.2 and latest 2.2.4 samba sources. What's wrong with my settings ? When I running runtest in testsuites directory I got: WARNING: Couldn't find the global config file. WARNING: No tool specified Test Run By eugene on Thu Jun 6 18:37:13 2002 Native configuration is sparc-sun-solaris2.8 ===

Hi. Here are the relevant details about the setup: SunOS 4.1.4 gcc 2.7.2.2 tcp wrappers 7.5 egd 0.6 (doesn't really come into play at compile time) The following only pertains to the compilation (and linking) stage. Code and patches are SunOS specific. -- The following functions are missing in SunOS: strerror, atexit, memmove. I wrote simple replacements in term of on_exit and bcopy

Hi, as I saw someone today pointing to a solution for protected directories in the recycle dir (thanks Ben!), I wanted to compile the modified recycle.c. I'm using Mandrake 9.0, I have kernel-source, kernel-header and all basic development tools installed, including the libtool package; I downloaded the Samba 2.2.7a sources, applied the patch, but I cannot compile the library. Following

Thank you, Chris. The following is my comprehension about the AliasSetTracker, please correct me. 1. A aliasset "as" represents a memory object, and all pointer "p" in "as" represent values with the type of pointer that may/must point to the memory object "as". 2. If a aliasset is "forwarding", it has been merged to another aliasset and I

This adds new APIs for running a local NBD server and connecting to it using systemd socket activation (instead of stdin/stdout). This includes interop tests against nbdkit and qemu-nbd which I believe are the only NBD servers supporting socket activation. (If we find others then we can add more interop tests in future.) The upstream spec for systemd socket activation is here:

On 3/15/23 18:25, Eric Blake wrote: > On Wed, Mar 15, 2023 at 12:01:57PM +0100, Laszlo Ersek wrote: >> Don't try to test async-signal-safety, only that >> NBD_INTERNAL_FORK_SAFE_ASSERT() works similarly to assert(): >> >> - it prints diagnostics to stderr, >> >> - it calls abort(). >> >> Some unfortunate gymnastics are necessary to avoid

Hi, I have a number of issues compiling samba 3.4.0pre1 using makerpms.sh, under the RHEL folder in packaging. 1) samba.spec refers to 'source' when the folder has been renamed to 'source3' (easy enough to amend) which made it fail very early on. 2) Following that - (apologies in advance, if I have gone over the top in pasting output), it seems to be complaining about missing

Volodya, I think you may need to update your CFE and rebuild. I compiled the test using my local build and I didn't get the results you see below. I'm also very surprised to see this output. The first %tmp.11 should have been %tmp.1 .. not sure how it got corrupted. In any event, the attachment is obviously generated by code that runs quite differently because the virtual register names