search for: int64_ts

Sparc Solaris lacks an int64_t data type. I added a macro to detect/correct this problem. Jon Shiring Btw, in my quick tests, Vorbis successfully decodes ogg files on sparc solaris. The following should be added to configure.in after the calls to set SIZE64 ---------------------- dnl this is a test to see if int64_t is defined dnl this is because AC_CHECK_TYPE breaks on "long long"

This allows you to append one file to another: copy-file-to-file /input.txt /output.txt append:true will append the contents of /input.txt to /output.txt. --- daemon/copy.c | 38 +++++++++++++++++++++++++++++++------- generator/actions.ml | 29 +++++++++++++++++++++-------- 2 files changed, 52 insertions(+), 15 deletions(-) diff --git a/daemon/copy.c b/daemon/copy.c index

v2 was here: https://www.redhat.com/archives/libguestfs/2020-October/msg00019.html v3: * defence -> defense * Use int64_t instead of int. This compiles on Windows. * Add GC wrappers to OCaml bindings. * New FreeBSD patch. * Removed "pid:" example from the ip filter manual, and added a warning beside the pid documentation. Rich.

Hello, everyone, I encounter a strange problem about llvm type i64 and C++ type int64_t. I instrumented a program to call the function 'myFunction' in the C++ shared library. 'myFunction' is something like this: int64_t myFunction() { int64_t retValue; ... std::cout << "retValue: " << retValue << "\n"; return retValue; }

This commit adds a formal specification of tvdiff_usec and a partial specification of subtract_timeval. These may be proved using Frama-C. The existing functions ignored overflow, but it is possible to call the functions with parameters that will cause overflow. So to create a formal specification I had to modify the functions to signal overflow. Luckily GCC and Clang have convenient

A widely used platform doesn't bother to have C99 integer types, so this allows building with it. Reported by sirlemonhead on IRC. Index: src/tools/oggz_tools.c =================================================================== --- src/tools/oggz_tools.c (revision 3827) +++ src/tools/oggz_tools.c (working copy) @@ -450,7 +450,7 @@ dg->pt = (iframe + pframe) >> 9;

On Mar 26, 2008, at 12:23 PM, Török Edwin wrote: [...] >> 2) ISO C++ does not support %jd. x86_64 does not know about %lld? >> > > It does, but gcc gives a warning, if I use %lld I get a warning on > x86_64, if I %ld I get a warning on x86-32. > int64_t is long int on x86-64. However sizeof(long int) == sizeof(long > long int), so I don't know why gcc insists it is

Actual variable holding content length is int64_t, but it was assigned by explicit cast to size_t. On 32-bit systems it's a lossy conversion, so it was replaced by casting to int64_t instead. Signed-off-by: Adrian Ambro?ewicz <adrian.ambrozewicz at linux.intel.com> --- plugins/curl/curl.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/curl/curl.c

Nicolas Geoffray wrote: > Very nice Torok! I applied most of the patch. A few comments: > Thanks! > 1) What is your jni.h file? I can't compile the Jni.cpp file with your > changes. > Ouch, did they change 'const'-ness between gcj versions? I was using gcj-4.2.3, and jni.h is from libgcj8-dev. > 2) ISO C++ does not support %jd. x86_64 does not know about

With dtrace, I can use function arguments in the form of arg0, arg1, etc, as indices into an "associative" array. If all that an array takes as an index is an int64_t, is there any reason for dtrace to require me to have an explicit type conversion in there rather than having it do it for me automatically? At present I need to do: mblks[arg0] or mblks[(int64_t)((mblk_t

The infrastructure for modified-time reporting has been essentially unused. These changes report the registry time by treating the time fields as Windows filetime fields stored in little-Endian (which means they can be treated as a single 64-bit little-Endian integer). This patch adds to the hivex ABI: * int64_t hivex_last_modified (hive_h *) * int64_t hivex_node_timestamp (hive_h *,

Our construction of struct command_in_flight was ad hoc; most parameters were set in command_common(), but extent callbacks were done after the fact, and NBD_CMD_DISC was open-coding things. Furthermore, every caller was triggering nbd_internal_run() for the cmd_issue event; doing that in a central place makes it easier for the next patch to improve that logic without duplicating the fix at each

The existing implementation admitted that it was not very robust in the face of garbage input (including, but not limited to, the the fact that the scanf() family has undefined behavior on integer overflow). Tighten things up by reimplementing the function. The old comment mentioned the 'human*' interface from gnulib; we can't use that for licensing reasons; so my rewrite is done

This adds most of the hivex APIs directly to the libguestfs API, so that you can read and write Windows Registry hive files from libguestfs without needing to download and upload hive files from the guest. This is analogous to how Augeas APIs are exposed already (guestfs_aug_*) Also, inspection is now done using the new APIs, which fixes the following bug:

In data martedì 23 giugno 2015 13:25:28, Richard W.M. Jones ha scritto: > This allows you to append one file to another: > > copy-file-to-file /input.txt /output.txt append:true > > will append the contents of /input.txt to /output.txt. > --- > daemon/copy.c | 38 +++++++++++++++++++++++++++++++------- > generator/actions.ml | 29 +++++++++++++++++++++--------

Very nice Torok! I applied most of the patch. A few comments: 1) What is your jni.h file? I can't compile the Jni.cpp file with your changes. 2) ISO C++ does not support %jd. x86_64 does not know about %lld? Thanks! Nicolas Török Edwin wrote: > Nicolas Geoffray wrote: > >> Hi everyone, >> >> I've just checked in a JVM and a CLI for LLVM (called JnJVM and N3).

Hi, I am trying to compile a 64-build of the latest dovecot v2.2.19 on my SuSE Linux Enterprise Server 10 (x64) system. I've run ./configure with two parameters, the --prefix one and the --with-ssldir one. During the make stage, I am getting the following 'internal compiler error' message : --------------------------------------------- [...] gcc -DHAVE_CONFIG_H -I. -I../..

Hi List, is there any way to generate proper C header files for functions that are defined in LLVM-IR. My current attempts fail when clang does some fancy transformations (to adhere to some ABIs ??), e.g., for returning a struct. For example the declaration typedef struct {int64_t a; int64_t b;int64_t c;} test; test create_test(void);yields the LLVM code %struct.test = type { i64, i64, i64 }

We have a memory leak when a function with a closure exits early prior to registering that closure through some path that will guarantee cleanup. The easiest way to fix it is to guarantee that once a closure is passed into a public API, it will be cleaned regardless of whether that API succeeds or fails. But to avoid cleaning the closure more than once, we need to refactor our internal handling,

On Tue, Feb 9, 2016 at 3:03 PM, Joerg Sonnenberger via llvm-commits < llvm-commits at lists.llvm.org> wrote: > On Tue, Feb 09, 2016 at 02:40:06PM -0800, Rui Ueyama via llvm-commits > wrote: > > Tried to fix the warning, and I'm not now sure if the warning makes > sense. > > These "'~': zero extending '<smaller integer type>' to