search for: stdbool

...local/include -DHAVE_CONFIG_H -O2 -pipe -fno-strict-aliasing -o hashnameddir.o hashnameddir.c In file included from hashnameddir.c:52: /usr/include/rpcsvc/yp_prot.h:71:15: error: cannot combine with previous 'type-name' declaration specifier typedef u_int bool; ^ /usr/include/stdbool.h:37:14: note: expanded from macro 'bool' #define bool _Bool ^ 1 error generated. *** Error code 1 Stop. make[4]: stopped in /usr0/freebsd/ports/work/am/eastasia/usr0/freebsd/ports/ports/shells/zsh/work/zsh-5.0.2/Src *** Error code 1 Stop. make[3]: stopped in /usr0/free...

...ecution, but at the end it does create th visual studio projects. Based on the web guide, it should be successful. First question, is it really? Then, I open visual studio and run the solution compilation. But, after a long time, I got a lot of errors stating that it is not possible to find the stdbool.h file + a few others. Example: error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such file or directory (<my path>\llvm\projects\compiler-rt\lib\floatuntisf.c) <my path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt.x86_64 error C2061: errore di sint...

...create th visual studio projects. > Based on the web guide, it should be successful. > First question, is it really? > > Then, I open visual studio and run the solution compilation. > > But, after a long time, I got a lot of errors stating that it is not > possible to find the stdbool.h file + a few others. > Example: > error C1083: Impossibile aprire il file inclusione 'stdbool.h': No such > file or directory (<my > path>\llvm\projects\compiler-rt\lib\floatuntisf.c) <my > path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt....

> By the way i8 and trunc come from clang as clang represents a bool as i8  > in memory. of course it would > be a nice feature if I could tell clang to always use i1 for bool, this > would also remove the problem. > Is this possible? > > -Jochen #include <stdbool.h> ?

Am 29.12.2011 19:52, schrieb Reid Kleckner: > I think Chris is saying that the and is necessary because with your i1 > trunc you're ignoring all of the high bits. The and implements that. > If you don't want this behavior, don't generate the trunc in the > first place and just compare the full width to zero. But if a backend sees trunc from i8 to i1 it should know

...inux/types.h index 929938f426de..98d0cbcaa600 100644 --- a/tools/lib/lockdep/uinclude/linux/types.h +++ b/tools/include/linux/types.h @@ -1,8 +1,9 @@ -#ifndef _LIBLOCKDEP_LINUX_TYPES_H_ -#define _LIBLOCKDEP_LINUX_TYPES_H_ +#ifndef _TOOLS_LINUX_TYPES_H_ +#define _TOOLS_LINUX_TYPES_H_ #include <stdbool.h> #include <stddef.h> +#include <stdint.h> #define __SANE_USERSPACE_TYPES__ /* For PPC64, to get LL64 types */ #include <asm/types.h> @@ -10,10 +11,22 @@ struct page; struct kmem_cache; -typedef unsigned gfp_t; +typedef enum { + GFP_KERNEL, + GFP_ATOMIC, + __GFP_HIGHM...

...inux/types.h index 929938f426de..98d0cbcaa600 100644 --- a/tools/lib/lockdep/uinclude/linux/types.h +++ b/tools/include/linux/types.h @@ -1,8 +1,9 @@ -#ifndef _LIBLOCKDEP_LINUX_TYPES_H_ -#define _LIBLOCKDEP_LINUX_TYPES_H_ +#ifndef _TOOLS_LINUX_TYPES_H_ +#define _TOOLS_LINUX_TYPES_H_ #include <stdbool.h> #include <stddef.h> +#include <stdint.h> #define __SANE_USERSPACE_TYPES__ /* For PPC64, to get LL64 types */ #include <asm/types.h> @@ -10,10 +11,22 @@ struct page; struct kmem_cache; -typedef unsigned gfp_t; +typedef enum { + GFP_KERNEL, + GFP_ATOMIC, + __GFP_HIGHM...

v1 here: https://www.redhat.com/archives/libguestfs/2020-March/msg00099.html This one fixes most of the points picked up in review, and does not strdup the strings which should keep down memory usage if that is a concern. Rich.

...le changed, 14 insertions(+), 1 deletion(-) > >diff --git a/options/decrypt.c b/options/decrypt.c >index 8eb24bc..6b1c0a8 100644 >--- a/options/decrypt.c >+++ b/options/decrypt.c >@@ -25,6 +25,7 @@ > > #include <stdio.h> > #include <stdlib.h> >+#include <stdbool.h> > #include <string.h> > #include <libintl.h> > #include <error.h> >@@ -82,11 +83,23 @@ inspect_do_decrypt (guestfs_h *g, struct key_store *ks) > CLEANUP_FREE char *type = guestfs_vfs_type (g, partitions[i]); > if (type && > (STREQ...

On Thu, Apr 10, 2014 at 07:38:05PM +0200, Borislav Petkov wrote: > Rebased onto current acme/perf/core: > > -- > From: Borislav Petkov <bp at suse.de> > Date: Sun, 23 Feb 2014 12:04:53 +0100 > Subject: [PATCH] tools: Unify export.h > > So tools/ has been growing three, at a different stage of their > development export.h headers and so we should unite into one.

On Thu, Apr 10, 2014 at 07:38:05PM +0200, Borislav Petkov wrote: > Rebased onto current acme/perf/core: > > -- > From: Borislav Petkov <bp at suse.de> > Date: Sun, 23 Feb 2014 12:04:53 +0100 > Subject: [PATCH] tools: Unify export.h > > So tools/ has been growing three, at a different stage of their > development export.h headers and so we should unite into one.

...ons/decrypt.c b/options/decrypt.c >> >index 8eb24bc..6b1c0a8 100644 >> >--- a/options/decrypt.c >> >+++ b/options/decrypt.c >> >@@ -25,6 +25,7 @@ >> > >> >#include <stdio.h> >> >#include <stdlib.h> >> >+#include <stdbool.h> >> >#include <string.h> >> >#include <libintl.h> >> >#include <error.h> >> >@@ -82,11 +83,23 @@ inspect_do_decrypt (guestfs_h *g, struct key_store *ks) >> > CLEANUP_FREE char *type = guestfs_vfs_type (g, partitions[i]); >&gt...

This is what I've been playing with in response to my earlier question about what to do with 'nbdkit -s sh -' (https://www.redhat.com/archives/libguestfs/2020-April/msg00032.html) I'm still open to ideas on a better name, and/or whether adding <stdbool.h> to our public include files is a good idea (if not, returning int instead of bool is tolerable). Eric Blake (2): server: Add nbdkit_stdio_safe server: Sanitize stdin/out before running plugin code docs/nbdkit-plugin.pod | 23 +++++++++++++++++++- plugins/sh/nbdkit-sh-plugin.po...

Reid Kleckner <rnk at google.com> writes: > My initial impression was that still probably nobody uses python 3, so it's > not worth adding support that will break. But if users actually have > python 3, maybe it's worth it. I think that on this case the problem was not people who actually have python 3, but people who see Python as a requirement for building LLVM and go

Hi all, Consider this C code: #include <stdbool.h> bool func(int n1, int n2, bool b) { bool greater = n1 > n2; if (greater && b) { if (n1 == n2) { return false; // unreachable } } return true; } The line marked unreachable cannot be reached, however currently LLVM does not optimize it o...

...create th visual studio projects. > Based on the web guide, it should be successful. > First question, is it really? > > Then, I open visual studio and run the solution compilation. > > But, after a long time, I got a lot of errors stating that it is not > possible to find the stdbool.h file + a few others. > Example: > error C1083: Impossibile aprire il file inclusione 'stdbool.h': No > such file or directory (<my > path>\llvm\projects\compiler-rt\lib\floatuntisf.c) <my > path>\llvm\projects\compiler-rt\lib\int_lib.h 37 1 clang_rt....

On Wed, Jan 22, 2020 at 10:14:38AM +0100, Jan Synacek wrote: > -val inspect_decrypt : Guestfs.guestfs -> key_store -> unit > +val inspect_decrypt : Guestfs.guestfs -> ?allow_discards:bool -> key_store -> unit > > (** Simple implementation of decryption: look for any [crypto_LUKS] > partitions and decrypt them, then rescan for VGs. This only works > for

--- generator/c.ml | 2 -- 1 file changed, 2 deletions(-) diff --git a/generator/c.ml b/generator/c.ml index 055b683..963cf21 100644 --- a/generator/c.ml +++ b/generator/c.ml @@ -1213,9 +1213,7 @@ and generate_client_actions hash () = #include <stdlib.h> #include <stdint.h> #include <inttypes.h> -#include <sys/types.h> #include <sys/stat.h> -#include

...as far as possible to validate that the given init is executable. Signed-off-by: Ben Hutchings <ben at decadent.org.uk> --- --- a/usr/kinit/run-init/run-init.c +++ b/usr/kinit/run-init/run-init.c @@ -39,6 +39,7 @@ * - Spawns the specified init program (with arguments.) */ +#include <stdbool.h> #include <stdlib.h> #include <stdio.h> #include <unistd.h> @@ -51,7 +52,7 @@ static const char *program; static void __attribute__ ((noreturn)) usage(void) { fprintf(stderr, - "Usage: exec %s [-d caps] [-c consoledev] /real-root /sbin/init [args]\n", + &qu...

...substance of the APIs (I'm not expert in this area), just some style notes. Overall, the capitalization style is inconsistent with the bulk of the C bindings, which are more Carbon than GNU. On Feb 23, 2008, at 01:34, Nick Kledzik wrote: > #include <stdint.h> > #include <stdbool.h> Note that MSVC++ still doesn't support C99, and is a target for LLVM. I'd suggest bool -> int and uint8_t* -> void* to resolve the dependency. > #include <stddef.h> > > extern const char* > lto_get_error_message(); I've tried not to create thread-unsaf...