search for: int64_t

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 defi...

...define DEST_FILE_FLAGS O_WRONLY|O_CREAT|O_TRUNC|O_NOCTTY|O_CLOEXEC, 0666 #define DEST_DEVICE_FLAGS O_WRONLY|O_CLOEXEC, 0 /* flags */ @@ -210,8 +209,13 @@ copy (const char *src, const char *src_display, int do_copy_device_to_device (const char *src, const char *dest, int64_t srcoffset, int64_t destoffset, int64_t size, - int sparse) + int sparse, int append) { + if ((optargs_bitmask & GUESTFS_COPY_DEVICE_TO_DEVICE_APPEND_BITMASK) && + append) { + reply_with_error ("the append flag cannot be se...

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...

.../include/test-tvdiff.c index abefb2e7..1bf6523b 100644 --- a/common/include/test-tvdiff.c +++ b/common/include/test-tvdiff.c @@ -46,7 +46,9 @@ #define TEST_TVDIFF(tv1, tv2, expected) \ do { \ - int64_t actual = tvdiff_usec (&(tv1), &(tv2)); \ + int64_t actual; \ + \ + tvdiff_usec (&(tv1), &(tv2), &actual);...

...============= --- src/tools/oggz_tools.c (revision 3827) +++ src/tools/oggz_tools.c (working copy) @@ -450,7 +450,7 @@ dg->pt = (iframe + pframe) >> 9; dg->dist = ((iframe & 0xff) << 8) | (pframe & 0xff); dg->delay = pframe >> 9; - dg->dt = (int64_t)dg->pt - dg->delay; + dg->dt = (ogg_int64_t)dg->pt - dg->delay; } int Index: src/liboggz/metric_internal.c =================================================================== --- src/liboggz/metric_internal.c (revision 3827) +++ src/liboggz/metric_internal.c (working...

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 wrong. > I only found %jd which doesn't give warnings on either: > > #include <stdio.h> > #include <stdint.h> > int main() > { > int64...

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 del...

...hey 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 %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 wrong. I only found %jd which doesn't give warnings on either: #include <stdio.h> #include <stdint.h> int main() { int64_t x=0; printf("%ld"...

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 *)arg0)->b_cont] whereas what I''d like to be able to do is: mblks[arg0] and mblk...

...tructure 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 *, hive_node_h) These two functions return the hive's last-modified time and a particular node's last-modified time, respectively. Credit to Richard Jones for the ABI suggestion, and for the tip on Microsoft's file...

...s(-) diff --git a/lib/disconnect.c b/lib/disconnect.c index bc43b4c..9706835 100644 --- a/lib/disconnect.c +++ b/lib/disconnect.c @@ -60,27 +60,17 @@ nbd_unlocked_shutdown (struct nbd_handle *h) int nbd_unlocked_aio_disconnect (struct nbd_connection *conn) { - struct command_in_flight *cmd; + int64_t id; - cmd = malloc (sizeof *cmd); - if (cmd == NULL) { - set_error (errno, "malloc"); + id = nbd_internal_command_common (conn, 0, NBD_CMD_DISC, 0, 0, NULL, + 0, NULL); + if (id == -1) return -1; - } - cmd->flags = 0; - cmd->type =...

...thout @@ -80,49 +80,78 @@ nbdkit_absolute_path (const char *path) return ret; } -/* XXX Multiple problems with this function. Really we should use the - * 'human*' functions from gnulib. +/* Parse a string with possible scaling suffix, or return -1 after reporting + * the error. */ int64_t nbdkit_parse_size (const char *str) { uint64_t size; - char t; + char *end; + uint64_t scale = 1; - if (sscanf (str, "%" SCNu64 "%c", &size, &t) == 2) { - switch (t) { - case 'b': case 'B': - return (int64_t) size; - case 'k...

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:

...REAT|O_TRUNC|O_NOCTTY|O_CLOEXEC, 0666 > #define DEST_DEVICE_FLAGS O_WRONLY|O_CLOEXEC, 0 > > /* flags */ > @@ -210,8 +209,13 @@ copy (const char *src, const char *src_display, > int > do_copy_device_to_device (const char *src, const char *dest, > int64_t srcoffset, int64_t destoffset, int64_t size, > - int sparse) > + int sparse, int append) > { > + if ((optargs_bitmask & GUESTFS_COPY_DEVICE_TO_DEVICE_APPEND_BITMASK) && > + append) { > + reply_with_error (&quo...

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).

...:http://bugs.opensuse.org> for instructions. make[4]: *** [test_lib-test-timing.o] Error 1 ---------------------------------------------- The lines that seem to be causing the problem are the following ( from src/lib/test-timing.c ) : 45: void test_timing(void) 46: { 47: static int64_t test_input1[] = { 48: 20, 19, 18, 1, 2, 3, 4, 5, 6, 7, 8, 49: 9, 10, 11, 12, 13, 14, 15, 16, 17, -1 50: }; This is the first time that any version of dovecot (the v2.2 branch) couldn't compile on my system, and I've literally compiled every single release...

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 } declare void @create_test(%struct.test* sret) #1 However, the function is defined in LLVM-IR as {i64,i64,i64} @create_test() Questions: 1) Is there any way to convince clang to genera...

...un (h, cmd_issue) == -1) debug (h, "option queued, ignoring state machine failure"); diff --git a/lib/rw.c b/lib/rw.c index 8b736d3..9f2909b 100644 --- a/lib/rw.c +++ b/lib/rw.c @@ -48,9 +48,9 @@ nbd_unlocked_pread (struct nbd_handle *h, void *buf, size_t count, uint64_t offset, uint32_t flags) { int64_t cookie; + nbd_completion_callback c = NBD_NULL_COMPLETION; - cookie = nbd_unlocked_aio_pread (h, buf, count, offset, - NBD_NULL_COMPLETION, flags); + cookie = nbd_unlocked_aio_pread (h, buf, count, offset, &c, flags);...

....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 'int64_t' of > greater > > size" warning may be annoying as it is issued for code like "int64_t x = > > ~<some-int32_t-var>". > > This sounds like something were the semantic of the code is not > obviously what was originally intended. > So you thought th...