search for: nonport

Hey, I ran across this while building vorbis on the Mac: In libvorbis RC2, file info.c, line 65, there's a call to strdup(). strdup() isn't portable, and it looks like the code should use the internal memory functions to create the memory for the string anyway. Actually, on further inspection, it looks like the memory for the user comments is never actually freed. I'm not subscribed

Hi folks, I'd like to remind people with write access on the CVS mainline not to put any tools/libs/patches into the main build that are not portable... I'm getting not-very-pretty flames from NetBSD folks because libao fails to *configure* under NetBSD (let alone build), thus breaking building the build for the entire CVS mainline. Specifically: >checking size of int...

...; Nothing arguable about it, see C99 6.3.2.3 > it's not clear that the standard forbids the invocation of such a > function No such function can exist. I don't think the standard forbids you to call 0, but it makes calling 0 undefined behavior ("behavior, upon use of a nonportable or erroneous program construct or of erroneous data"), since there can't possibly be a valid function there. > nor does it seem like a good idea to silently strip any > such invocations especially if allowed to be specified; as to do so > would > seemingly only mask po...

> Dale Johannesen wrote: >> Marius Wachtler wrote: >> ... >> The call to address 0 gets removed. >> >> define i32 @t(i32 %a) noreturn nounwind readnone { >> entry: >> unreachable >> } >> >> How can I prevent that the call is removed, without making the >> function addr volatile? >> Does anyone know which optimization

...; va_list arg; va_start(arg, format); vsnprintf(buf, BUFSIZE, format, arg); va_end(arg); buf[BUFSIZE - 1] = '\0'; error(buf); } ----- end code snippet ----- But that's not portable because vsnprintf isn't. You've already made a big effort to work around nonportability of vsnprintf, but don't make it available in the API. Why not? If I could change vsnprintf to Rvsnprintf above, then I wouldn't have to do some horrible autoconf song and dance that probably wouldn't be completely portable anyway. Or is there a better solution I haven't se...

The installed Xen header files (/usr/include/xen/*) expect the U8, u16, u32, etc types to already be defined. Currently, xc.h provides this in a nonportable way. I''ve changed xc.h to use stdint.h, and fixed a few printf-style format strings to match. Thanks, Charles

New in flute directory. Telemann Methodical Sonatas > 1hour duration. I want arelatively cheap laptop to do portable recording. Any good choices available? .......Al --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project homepage: http://www.xiph.org/ogg/ To unsubscribe from this list, send a message to 'vorbis-request@xiph.org' containing only the word

...-version -funit-at-a-time # -fverbose-asm -fzero-initialized-in-bss -m128bit-long-double -m32 -m80387 # -maccumulate-outgoing-args -malign-stringops -matt-stubs # -mconstant-cfstrings -mfancy-math-387 -mfp-ret-in-387 -mieee-fp -mmmx # -mno-red-zone -mno-sse4 -mpush-args -msse -msse2 -msse3 # -mwarn-nonportable-cfstrings # Compiler executable checksum: 8b71d7bb9d5d18146938b09f1ac40213 from... touch t.cc llvm-gcc-4 -fverbose-asm t.cc -S

...ng an environment variable with the user's LDAP username, resulting in authorized_keys lines like: environment="LDAP_USER=jdoe" ssh-ed25519 ... This generates a log message like: bad key options: invalid environment string The attached patch is against the released openssh-7.7 nonportable release, however my testing took place on a portable (Linux) system. Given the simplicity of the patch I hope that is not an issue. I am happy to add a test case for this if that would be appropriate. Cross reference to Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/177101...

It is setting TZ and using tzset(). R is not multi-threaded so it is safe. Simon figure out the important settings from the config.log and config.h files on a musl system: /* #undef USE_INTERNAL_MKTIME */ #define HAVE_TM_GMTOFF 1 #define HAVE_TM_ZONE 1 Does this help anyone debug the issue? Simon just went on vacation. On Thu, Feb 4, 2016 at 7:32 PM, Rich Felker <dalias at libc.org>

...to fetch 64 bytes of random data at boot and at regular intervals. It is not a show-stopper, but better efficiency would be nice. I thought about this for a while and didn't come up with anything that wouldn't messy. We could fudge the MSR rax/rdx high bits to get 128 bits, but that's nonportable and awful to implement. We could return a random number directly from CPUID, but that's weird. In very informal benchmarking, rdmsr wasn't that bad. On the other hand, I wasn't immediately planning on using the msr on an ongoing basis on Linux guests except after suspend/resume....

Defining a standard way of transferring random numbers between the host and the guest is an excellent idea. As the person who writes the RNG code in Windows, I have a few comments: DETECTION: It should be possible to detect this feature through CPUID or similar mechanism. That allows the code that uses this feature to be written without needing the ability to catch CPU exceptions. I could be

Defining a standard way of transferring random numbers between the host and the guest is an excellent idea. As the person who writes the RNG code in Windows, I have a few comments: DETECTION: It should be possible to detect this feature through CPUID or similar mechanism. That allows the code that uses this feature to be written without needing the ability to catch CPU exceptions. I could be

...Not true at all. In particular, various data structures have different sizes based on their implementation (e.g. FILE), and many APIs may be different. C is not a language that is designed to be portable. *If* we controlled all of the header files, *and* restricted the C compiler to reject "nonportable" features, then we could provide portability for the C subset that is left. I actually think that this would be a very interesting project, but it's not something I'm even considering doing myself. > Why don't we have platform independence as an optional bytecode feature &...

...- Easiest to implement - Can express an arbitrary offset - Avoids taking up additional space in the GlobalVariable class, as we can just introduce an additional bitfield. Cons: - Not useful in portable IR -- but then again, if you're using this attribute you're probably doing something nonportable anyway. (3) Offset a list of GEP parameters: @vt = linkonce_odr global [3 x i8*] [i8* @rtti, i8* @f1, i8* @f2], symbol_offset (i32 0, i32 1) Similar to (1) but the symbol position for @vt is evaluated as though @vt were the first operand of a getelementptr constant, and the symbol_offset oper...

...to fetch 64 bytes of random data at boot and at regular intervals. It is not a show-stopper, but better efficiency would be nice. I thought about this for a while and didn't come up with anything that wouldn't messy. We could fudge the MSR rax/rdx high bits to get 128 bits, but that's nonportable and awful to implement. We could return a random number directly from CPUID, but that's weird. In very informal benchmarking, rdmsr wasn't that bad. On the other hand, I wasn't immediately planning on using the msr on an ongoing basis on Linux guests except after suspend/resume....

...to fetch 64 bytes of random data at boot and at regular intervals. It is not a show-stopper, but better efficiency would be nice. I thought about this for a while and didn't come up with anything that wouldn't messy. We could fudge the MSR rax/rdx high bits to get 128 bits, but that's nonportable and awful to implement. We could return a random number directly from CPUID, but that's weird. In very informal benchmarking, rdmsr wasn't that bad. On the other hand, I wasn't immediately planning on using the msr on an ongoing basis on Linux guests except after suspend/resume....

Hello, You know, I always worry about the precision and the float constants... and there is a large lookup table in the floor1.c ... and I figure out a way to keep the code size and speed, but to improve the precision at this lookup table. (the difference is small, but audible) Here is the modifications in the floor1.c: tatic unsigned long FLOOR_fromdB_LOOKUP[256]={

...- yes agreed, however: >> it's not clear that the standard forbids the invocation of such a >> function > > No such function can exist. I don't think the standard forbids you > to call 0, but it makes calling 0 undefined behavior ("behavior, upon > use of a nonportable or erroneous program construct or of erroneous > data"), since there can't possibly be a valid function there. - also yes, however ((void *) 0) need not have a storage representation being equivalent to ((int) 0), as for example may be represented as being equivalent to ((int)...

On Thu, 2004-09-16 at 23:45, Chris Lattner wrote: > On Thu, 16 Sep 2004, Andrew Lenharth wrote: > > So I propose that llvm-gcc not consider itself any type of x86-linux (or > > what ever it platform it was compiled on), but rather create a new > > architecture, say llvm (or perhaps 2, one for each bit and little > > endian). Thuse llvm-gcc -dumpmachine would return