search for: _flags

Hello. I would like to modify printing of help options in order to fix: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69840 I basically split all *_flags.inc options with new lines. Eventually, these string are printed to limit the output to 80 characters: https://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html That's my first patch request in the project, please advise if anything is missing. Thanks, Martin -------------...

There are few more things that could be cleaned up related to the coding style and other things, like explicitly specifying the abi style after "extern" (i.e. `extern "C" fn` instead of `extern fn`), but since those are configurable in rustfmt config, I'm not sure whether the config needs to be added or complying with the defaults should be the priority. But this was just

...Martin Liška <llvm-dev at lists.llvm.org > <mailto:llvm-dev at lists.llvm.org>> wrote: > > Hello. > > I would like to modify printing of help options in order to fix: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69840 > > I basically split all *_flags.inc options with new lines. > Eventually, these > string are printed to limit the output to 80 characters: > https://www.gnu.org/prep/standards/html_node/Command_002dLine-Interfaces.html > > That's my first patch request in the project, please advise if > a...

FYI, looks like support for Racoon is ending. Does anyone have any experience with the version in ipsec-tools ? ---Mike >Racoon users, > >This is the announcement that the kame project will quit providing >a key management daemon, the racoon, and that "ipsec-tools" will become >the formal team to release the racoon. >The final release of the racoon in the

The following case will make the incompat/compat flag of the super block be recovered. Task1 |Task2 flags = btrfs_super_incompat_flags(); | |flags = btrfs_super_incompat_flags(); flags |= new_flag1; | |flags |= new_flag2; btrfs_set_super_incompat_flags(flags); | |btrfs_set_super_incompat_flags(flags); the new_flag1 is recovered. In order to avoid this problem, we introduce a lock named super_lock into the btrfs...

...ture that takes uint32_t; if we wanted, we could pack > libnbd-specific flags in the upper bits that the NBD protocol would > never see. This is fine ACK. About the "guard" change: I probably would have put that change in a separate commit. Also you could consider having a default_flags parameter to avoid having to set guard = None everywhere, although you would still have to make a one-off change to every *_flags. It would look like this: let default_flags = { flag_prefix = ""; guard = None; flags = [] } ... let handshake_flags = { default_flags with f...

> What version of cmake are you using? I am getting the opposite > behavior: every binary is linked using -rdynamic :-( BTW, I reported llvm.org/pr15543 to track this. Cheers, Rafael

...anted, we could pack >> libnbd-specific flags in the upper bits that the NBD protocol would >> never see. > > This is fine ACK. > > About the "guard" change: I probably would have put that change in a > separate commit. Also you could consider having a default_flags > parameter to avoid having to set guard = None everywhere, although you > would still have to make a one-off change to every *_flags. It would > look like this: > > let default_flags = { flag_prefix = ""; guard = None; flags = [] } > ... > let handshake_fl...

...object prop types configure/freedreno: make KGSL support optional configure/freedreno: enable freedreno by default Thierry Reding (6): libdrm: Add NVIDIA Tegra support tegra: Add simple test for drm_tegra_open() tegra: Add GET/SET_TILING IOCTLs tegra: Add SET/GET_FLAGS IOCTLs tegra: Implement drm_tegra_bo_{get,set}_flags() tegra: Implement drm_tegra_bo_{get,set}_tiling() Thomas Meyer (1): intel: Fix SIGSEGV in libdrm for heigth = 0 and width = 0 Ville Syrjälä (1): modetest: Print newline for empty blobs Zhenyu Wang (1): intel: Fix...

On 21 August 2012 13:39, Stephen Checkoway <s at pahtak.org> wrote: > Attached is a patch that fixes it for the cmake build. I'm not positive this is the right place to put it and I really have no idea where the check should go when using the autotools. What version of cmake are you using? I am getting the opposite behavior: every binary is linked using -rdynamic :-( Cheers, Rafael

On Tue, Jan 27, 2015 at 10:02 AM, Mueller-Roemer, Johannes Sebastian <Johannes.Sebastian.Mueller-Roemer at igd.fraunhofer.de> wrote: > Adding -D__MSVCRT_VERSION__=0x900 (or higher) to CMAKE_CXX_FLAGS and > -lmsvcr90 (or higher) to CMAKE_CXX_STANDARD_LIBRARIES appears to work. > -lmsvcrt80 does not work, contrary to the comment on the MinGW bug tracker. > However, if you do not have the runtimes installed, errors will occur later > on in the build process, such as: > > [215/119...

....8.9 steve$ grep rdynamic rules.ninja |wc -l 0 Okay, yes that's it. ${prefix}/share/cmake/Modules/Platform/Linux-Intel.cmake: # We pass this for historical reasons. Projects may have # executables that use dlopen but do not set ENABLE_EXPORTS. set(CMAKE_SHARED_LIBRARY_LINK_${lang}_FLAGS "-rdynamic") I assume the CMAKE_SHARED_LIBRARY_LINK_C_FLAGS and CMAKE_SHARED_LIBRARY_LINK_CXX_FLAGS could be set empty initially and then for those that need it, set it (or something else) to -rdynamic. -- Stephen Checkoway

Hi, I have having hard time to let cmake configuration detect the zlib header in windows with "Visual Studio 12" generator. My cmake configuration goes like >> Set path, include and lib environment variables to point to zlib headers and libraries. Cmake version is 2.8.12.2 cmake -G "Visual Studio 12" -D LLVM_TARGETS_TO_BUILD:STRING=%TARG% -D

...< $VAR1 = bless( { 'onclose' => [ sub { "DUMMY" } ], 'g' => bless( { '_g' => 70645888, '_flags' => 0 }, 'Sys::Guestfs' ) }, 'Sys::VirtConvert::GuestfsHandle' ); If I tell the code to skip the section that calls 'die' the result becomes: virt-v2v: Failed to find a kernel_pkg.i686 package to install Any ideas on ho...

...C: Fn(guestfs::Event, EventHandle, &[u8], &[u64]), >+ { >+ extern "C" fn trampoline<C>( >+ _g: *const base::guestfs_h, >+ opaque: *const c_void, >+ event: u64, >+ event_handle: i32, >+ _flags: i32, >+ buf: *const c_char, >+ buf_len: usize, >+ array: *const u64, >+ array_len: usize, >+ ) where >+ C: Fn(guestfs::Event, EventHandle, &[u8], &[u64]), >+ { >+ // trampoline function...

There is no immediate support for this in the test-suite cmake buildsystem. There is something in the Makefile system indeed, but it lacks documentation and I'm not aware of any examples of how to use it. I would recommend to use `CMAKE_C_FLAGS=--save-temps=obj cmake ...` in the test-suite. The --save-temps=obj flag will make clang place a bitcode file next to each .o file. - Matthias > On Feb 26, 2018, at 9:42 AM, Gus Smith via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hello all. > > I'm in need of a...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:01.jail Security Advisory The FreeBSD Project Topic: Jail rc.d script privilege escalation Category: core Module: etc_rc.d Announced:

...Box::from_raw(h as *mut Handle) }; + drop (h); +} + +extern fn ramdisk_get_size (_h: *mut c_void) -> int64_t { + return DISK.lock().unwrap().capacity() as int64_t; +} + +extern fn ramdisk_pread (_h: *mut c_void, buf: *mut c_char, count: uint32_t, + offset: uint64_t, _flags: uint32_t) -> c_int { + let offset = offset as usize; + let count = count as usize; + let disk = DISK.lock().unwrap(); + unsafe { + ptr::copy_nonoverlapping (&disk[offset], buf as *mut u8, count); + } + return 0; +} + +extern fn ramdisk_pwrite (_h: *mut c_void, buf:...

Hello all. I'm in need of a benchmark that can be compiled to IR or bytecode. I found the test-suite project (https://llvm.org/docs/TestSuiteMakefileGuide.html) and thought a benchmark in that project might work. However, I'm having trouble figuring out how to actually compile any of the benchmarks to IR or bytecode. Using cmake and make I can compile them to binaries, but at no point do

This adds very rough support for writing nbdkit plugins in Rust. This is not very idiomatic -- essentially we're handling the direct C calls from nbdkit in Rust. We have to use ‘unsafe’ in a few places because there's no way to tell the Rust code that nbdkit satisfies guarantees (eg. around thread safety, always returning leaked pointers back to the close function, always doing bounds