search for: printfs

Displaying 20 results from an estimated 5979 matches for "printfs".

Did you mean: printf
2006 Oct 13
0
Wine release 0.9.23
...at warning fixes. Michael Stefaniuc (123): Add a WINE_NO_LONG_INT define to many makefiles to ease the transition of DWORD/LONG/ULONG from long to int. include: Make DWORD/LONG/ULONG an int to use the same type in Win32 and Win64. debug.h, test.h: Temporary add ifdefs around some printfs to avoid format. "One liners" printf format warning fixes for the migration of DWORD/LONG/ULONG from long to int. server: Win64 printf format warning fixes. wrc: Win64 printf format warning fixes. winedump: Win64 printf format warning fixes. user: Win64 print...
2007 May 25
0
Patch -- SVN revision in the version string
This is the patch to include SVN revision level in version number displays. There should be two enclosures; the patch itself and a new source file. common/upsversion.c. upversion.c defines a single function. upsversion(), that returns a version string for display. Some Makefile trickery ensures that this file will be recompiled whenever the project's SVN revision level has changed since it
2011 Dec 21
2
[PATCH] xenpm: assorted adjustments
- use consistent error values (stop mixing of [positive] errno values with literal -E... ones) - properly format output - don''t use leading zeros in decimal output - move printing of average frequency into P-state conditional (rather than a C-state one) - don''t print some C-state related info when CPU idle management is disabled in the hypervisor - use calloc() for array
2020 Oct 06
2
[PATCH libnbd] info: Write output atomically.
If the server fails, nbdinfo can write partial output before the error message (albeit on different channels). Here is an example: $ nbdkit eval open='echo EIO fail >&2; exit 1' --run 'nbdinfo --json "$uri"' { "protocol": "newstyle-fixed", "TLS": false, nbdkit: eval[1]: error: /tmp/nbdkitii3pZW/open: fail nbdkit: eval[1]:
2012 Mar 10
3
problem: The decoded frame is not as the original one
Hi All, i need your help in determining the problem in the following sample code (taken from speex manual) for fixed point encoding. i tested encoding a 160 sample frame and then decoding it back But The problem is that the decoded frame is totally different from the original frame(see output below).What is the possible reason for this?.thanks for any help #include<stdio.h>
2018 Aug 21
0
[PATCH 2/2] OCaml tools: add output selection for --machine-readable
Add an optional argument for --machine-readable to select the output, adding a new function to specifically write data to that output stream. The possible choices are: * --machine-readable: to stdout, like before * --machine-readable=file:name-of-file: to the specified file * --machine-readable=stream:stdout: explicitly to stdout * --machine-readable=stream:stderr: explicitly to stderr Adapt all
2009 Jun 30
2
[PATCH node] Make all yes/no prompts consistent. rhbz#508778
Added a new function, "ask_yes_or_no", to ovirt-functions. It contains a default prompt if none is provided. Changed all prompts that ask for yes, no and/or abort to use this new method. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-boot-wrapper | 8 ++--- scripts/ovirt-config-collectd | 39 +++++++++++++++-----------
2009 Sep 12
1
[PATCH] Let MEMDISK honor the quiet append option
When you add "quiet" to the append line, Syslinux doesn't display the file reading progress anymore. When you use this option to boot an image with MEMDISK, you still get a lot of text. ========================== LABEL mydisk LINUX memdisk INITRD mydisk.img APPEND raw quiet ========================== The following patch makes MEMDISK silent when the quiet keyword is passed to the
2017 Jan 19
4
[PATCH] Fix cppcheck warnings
--- src/libFLAC/bitreader.c | 4 ++-- src/libFLAC/bitwriter.c | 4 ++-- src/plugin_xmms/plugin.c | 2 +- src/share/utf8/charset.c | 1 + src/test_libFLAC++/encoders.cpp | 8 ++++---- src/test_libFLAC/decoders.c | 4 ++-- src/test_libFLAC/encoders.c | 8 ++++---- 7 files changed, 16 insertions(+), 15 deletions(-) diff --git a/src/libFLAC/bitreader.c
2013 Dec 03
2
[LLVMdev] Newbie question: LLVM IR, printf, and varargs
Hi, I am trying to print two strings using printf. I have tried various things, but keep getting this error: llc: printf.ll:4:11: error: '@printf' defined with type 'i32 (i8*, ...)*' %1 = call i32 @printf(i8* null, i8*, i8* null) The code is: declare i32 @printf(i8* nocapture readonly, ...) nounwind define i32 @main() nounwind { %1 = call i32
2013 Dec 03
2
[LLVMdev] Newbie question: LLVM IR, printf, and varargs
I just tried adding the cast but it didn't help. I have the feeling that I am overlooking something very obvious, but I can't seem to figure out what it is. Thanks for your suggestion, though. -- Mikael 2013/12/3 Eli Bendersky <eliben at google.com> > > > > On Tue, Dec 3, 2013 at 2:29 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > >> Hi,
2012 Apr 25
1
forwarding packets to service in same host without using loopback network
This question is not about linux usage. But still i think user list is a good crowd for linux programmer. So here it goes. I have this libnetfilter_queue application which receives packets from kernel based on some iptables rule. Before going straight to my problem, i'm giving a sample workable code and other tools to set up a test environment so that We problem definition and possible
2014 Nov 10
0
[PATCH] Update documentation for new compression presets
--- doc/html/documentation_tools_flac.html | 6 ++--- include/FLAC/stream_encoder.h | 42 +++++++++++++++++----------------- src/flac/main.c | 20 ++++++++-------- 3 files changed, 34 insertions(+), 34 deletions(-) diff --git a/doc/html/documentation_tools_flac.html b/doc/html/documentation_tools_flac.html index 9f85a25..0964cd2 100644 ---
2010 Mar 23
1
[PATCH] Ensures that persist and unpersist work with relative paths.
As they iterate through their list of arguments, both ovirt_storage_config and remove_config first convert each of them into a fully qualified path before processing. Related: rhbz#576239 Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-functions | 80 +++++++++++++++++++++++------------------------ 1 files changed, 39 insertions(+), 41 deletions(-) diff --git
2013 Dec 03
0
[LLVMdev] Newbie question: LLVM IR, printf, and varargs
This code: declare i32 @printf(i8* nocapture readonly, ...) nounwind define i32 @bar(i8* %c, i32 %i) #0 { entry: %call = tail call i32 (i8*, ...)* @printf(i8* %c, i8* %c) ret i32 %call } Is accepted without complaints by close-to-trunk llc on my Ubuntu machine. Eli On Tue, Dec 3, 2013 at 2:58 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > I just tried adding the cast but
2013 Dec 03
0
[LLVMdev] Newbie question: LLVM IR, printf, and varargs
On Tue, Dec 3, 2013 at 2:29 PM, Mikael Lyngvig <mikael at lyngvig.org> wrote: > Hi, > > I am trying to print two strings using printf. I have tried various > things, but keep getting this error: > > llc: printf.ll:4:11: error: '@printf' defined with type 'i32 (i8*, > ...)*' > %1 = call i32 @printf(i8* null, i8*, i8* null) > > The
2019 Jul 01
0
[PATCH 1/6] p2v: move kernel config to perl script
Instead of generating the p2v kernel config using the OCaml generator, create a Perl script to do this job, mostly at build time. This is done to rely less on the generator for p2v, and because the generation of these sources is quick enough that it can be done at build time (instead of shipping the generated sources in dist tarballs). The generate-p2v-config.pl mimics what
2013 Dec 03
2
[LLVMdev] Newbie question: LLVM IR, printf, and varargs
Whoops... Seems I forgot the asterisk (*) after the cast. Or something. Because I did insert the cast and it didn't work. But NOW it works. Thank you for spending some time on this - and also for presenting the solution. -- Mikael 2013/12/4 Eli Bendersky <eliben at google.com> > This code: > > declare i32 @printf(i8* nocapture readonly, ...) nounwind > > define
2013 Feb 20
4
[LLVMdev] [RFC] NoBuiltin Attribute
On 2/19/2013 11:11 PM, Chris Lattner wrote: > > I still really have no idea what problem you think you are solving. Dealing with different attributes on different functions. --- a.c --- void func_a() { printf(...); } --- b.c --- void func_b() { printf(...); func_a(); } a.c is compiled with no-builtin-printf, b.c has no such options. The prototype approach (no-builtin on the
2019 Jan 25
0
[klibc:update-dash] builtin: Reject malformed printf specifications with digits after '*'
Commit-ID: eaf105c1c16e2157ebce8c63a58acca75df65ca9 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=eaf105c1c16e2157ebce8c63a58acca75df65ca9 Author: Patrick Brown <opensource at whoopdedo.org> AuthorDate: Sun, 6 Dec 2015 15:09:42 +0100 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] builtin: Reject