search for: strict

...mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: In > function ‘bool<unnamed>::isFPS16Immediate(llvm::ConstantFPSDNode*, > short int&)’: > /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: > 148: warning: dereferencing type-punned pointer will break strict- > aliasing rules > > > /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelLowering.cpp: In > function ‘llvm::SDOperand LowerBUILD_VECTOR(llvm::SDOperand, > llvm::SelectionDAG&)’: > /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelLowering.cpp: > 1690: warning: ‘...

...me: /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: In function ‘bool<unnamed>::isFPS16Immediate(llvm::ConstantFPSDNode*, short int&)’: /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelDAGToDAG.cpp: 148: warning: dereferencing type-punned pointer will break strict- aliasing rules /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelLowering.cpp: In function ‘llvm::SDOperand LowerBUILD_VECTOR(llvm::SDOperand, llvm::SelectionDAG&)’: /Volumes/mrs5/net/llvm/llvm/lib/Target/CellSPU/SPUISelLowering.cpp: 1690: warning: ‘val’ may be used uninitialized i...

...78.742174 10 is.unsorted(x.posixct.sort) 36.966654 37.031975 51.1228686 37.1235380 37.777319 153.270170 10 Since there do not appear to be any tests for is.unsorted() these are some tests to be added for some types. # integer sequence x <- -10L:10L stopifnot(!is.unsorted(x, na.rm = F, strictly = T)) stopifnot(!is.unsorted(x, na.rm = F, strictly = F)) # integer not strictly x <- -10L:10L x[2] <- x[3] stopifnot( is.unsorted(x, na.rm = F, strictly = T)) stopifnot(!is.unsorted(x, na.rm = F, strictly = F)) # integer with NA x <- -10L:10L x[2] <- NA stopifnot(!is.unsorted(x, na.r...

According to http://www.redhat.com/magazine/006apr05/features/selinux/ there is a package named selinux-policy-strict, which contains a series of rules for correctly handling many situations (software) when using strict policy. Does CentOS have this package available ? If not, can someone make it available through Centosplus or Addon, for example ? This package is not part of the upstream main release, but acco...

Hello to all LLVM Developers. The LLVM IR is in strict SSA form (i.e. every variable is defined before it is used along every path from the entry to exit point)? According to the documentation, currently the LLVM IR is in the SSA form, but I don't see additional information about *strict* SSA form. The strict SSA form provide opportunities of opti...

Intel would like to contribute a patch to implement support for these Intel- and Microsoft -fp options. This message is to describe the options and request feedback from the community. -fp-model=[precise|strict|fast|except[-]] and -fp-speculation=[fast|strict|safe] This contribution would dovetail with the llvm patch "Teach the IRBuilder about constrained fadd and friends" which is under review here, https://reviews.llvm.org/D53157/new/. I have a patch ready to review that works with D53157....

Under help(matrix) it is written: 'is.matrix' tests if its argument is a (strict) matrix. It is generic: you can write methods to handle specific classes of objects, see InternalMethods. Further down, under "Details", the meaning of "strict" is explained more explicitly: 'is.matrix' returns 'TRUE' if 'x' is a matrix...

...ng from version 1.3.12 unable to build Wine. I use /usr/sfw/bin/gcc compiler and gnu ld. For configure script I change only prefix. when i make gmake i get error. ........... gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_KERNEL32_ -D_NORMALIZE_ -D_REENTRANT -fPIC -Wall -pipe -fno-strict-aliasing -Wdeclaration-after-statement -Wstrict-prototypes -Wwrite-strings -Wpointer-arith -I/usr/sfw/include -I/usr/X11/include -I/usr/include -g -I/usr/sfw/include -I/usr/X11/include -I/usr/include -g -o actctx.o actctx.c gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_KERNEL32_...

...t; (OFFSET cmp 0), which is perfectly > fine when GEP is assumed to have undefined behavior on overflow, but > is > wrong if GEP is allowed to overflow > with well defined behavior (it wraps). > > Also will can the behavior of GEP be changed depending on llvm-gcc's > -fno-strict-aliasing/-fwrapv/-fno-strict-pointer-overflow flags? Yes. To implement -fwrapv, the front-end can omit any of the no-overflow flags, and choose the wrapping form of GEP, as appropriate. I'm not familiar with -fno-strict-pointer-overflow. Do you mean -fno-strict-overflow? I guess for LLVM that...

...ck-size validation would also make sense, especially given the recent addition of support for querying server minimum block size constraints (although I'd like to finish my work on getting nbdkit to advertise block constraints to make that easier to test...). Eric Blake (2): api: Add nbd_set_strict_mode api: Add STRICT_BOUNDS to nbd_set_strict_mode lib/internal.h | 3 + generator/API.ml | 67 ++++++++++- lib/disconnect.c | 18 +-- lib/handle.c | 16 +++ lib/rw.c | 289 ++++++++++++++++++++++++++++++----------------- tests/errors.c | 61 +++++++++- 6 files changed, 34...

...for integration purposes, it can be handy to coerce libnbd into sending something to see how the server will react (whether it be an extension libnbd has not yet learned, or an intentional bad request to test server error handling). Time to make this something the user can control, by adding a new strictness mode. A later patch will add another knob to the mode. --- Question: Should we split this into two knobs? Sending unknown flags is dangerous (in the future, a flag might be defined to alter the on-wire layout expected by either the client or server, and get things out-of-sync or even cause...

...w that would work, but it most likely wouldn't fit with the > design of llvm. If this is important, I'd rather fix the representational > issue. I agree. The option should control the kind of IR generated as Chris outlined in the document. We need to figure out exactly what "strict" means. Is it like "restrict" in C where it only has meaning with respect to other things marked "restrict" or is it more general? Can I reassociate a strict with a relaxed? Is it possible that "strict" will mean different things for different operations? We...

...net/llvm/llvm/llvm/lib/Target/CellSPU/ SPUISelDAGToDAG.cpp: In function 'bool<unnamed>::isFPS16Immediate(llvm::ConstantFPSDNode*, short int&)': /Volumes/mrs5/net/llvm/llvm/llvm/lib/Target/CellSPU/ SPUISelDAGToDAG.cpp:141: warning: dereferencing type-punned pointer will break strict-aliasing rules In file included from /Volumes/mrs5/net/llvm/llvm/llvm/lib/Target/ CellSPU/SPUISelDAGToDAG.cpp:312: /Volumes/mrs5/net/llvm/llvm/build/lib/Target/CellSPU/ SPUGenDAGISel.inc: In member function 'llvm::SDOperand SPUDAGToDAGISel::Transform_LO16_f32(llvm::SDNode*)': /Volumes/m...

...perfectly >> fine when GEP is assumed to have undefined behavior on overflow, but >> is >> wrong if GEP is allowed to overflow >> with well defined behavior (it wraps). >> >> Also will can the behavior of GEP be changed depending on llvm-gcc's >> -fno-strict-aliasing/-fwrapv/-fno-strict-pointer-overflow flags? >> > > Yes. To implement -fwrapv, the front-end can omit any of the no-overflow > flags, and choose the wrapping form of GEP, as appropriate. > > I'm not familiar with -fno-strict-pointer-overflow. Do you mean > -...

Hi Joshua, Thank you for that. From the code it kind of looks like STRICT_RTP_LEARN_TIMEOUT is a minimum, not a maximum: if (!ast_sockaddr_isnull(&rtp->strict_rtp_address) && STRICT_RTP_LEARN_TIMEOUT < ast_tvdiff_ms(ast_tvnow(), rtp->rtp_source_learn.start)) { ast_verb(4, "%p -- Strict RTP learning complete - Locking on source address %s\n&quot...

Yes, you’re probably right about this. I was originally thinking of FENV_ACCESS as a fully strict mode of operation, but what you’re suggesting aligns with what Cameron suggested and even some of my own reasoning on other points. So, let me amend my previous proposal to say: STDC FENV_ACCESS {ON|OFF} Patch in progress. I think ON should force the following: except_behavior { strict }...

...kely wouldn't fit with the >> design of llvm. If this is important, I'd rather fix the representational >> issue. > > I agree. The option should control the kind of IR generated as Chris outlined > in the document. > > We need to figure out exactly what "strict" means. Is it like "restrict" in C > where it only has meaning with respect to other things marked "restrict" > or is it more general? Can I reassociate a strict with a relaxed? Is it > possible that "strict" will mean different things for different o...

...--- a/src/share/grabbag/replaygain.c +++ b/src/share/grabbag/replaygain.c @@ -606,6 +606,8 @@ static FLAC__bool parse_double_(const FLAC__StreamMetadata_VorbisComment_Entry * FLAC__bool grabbag__replaygain_load_from_vorbiscomment(const FLAC__StreamMetadata *block, FLAC__bool album_mode, FLAC__bool strict, double *reference, double *gain, double *peak) { int reference_offset, gain_offset, peak_offset; + char *saved_locale; + FLAC__bool res = true; FLAC__ASSERT(0 != block); FLAC__ASSERT(0 != reference); @@ -618,20 +620,36 @@ FLAC__bool grabbag__replaygain_load_from_vorbiscomment(const FLAC__...

Hi, this patch fixes a problem with leading/trailing whitespace matching for FileCheck --strict-whitespace --match-full-lines. Consider a text file: ... $ cat DUMP bla1 bla2 bla3 bla4 bla5 ... with some leading and trailing spaces, made more visible like this: ... $ sed 's/ /_/g' DUMP bla1 bla2 _bla3 bla4_ _bla5_ ... and a FileCheck file CHECK to match DUMP: ... $ cat CHECK //...

...istent in that we let it through for read, write, and cache, but blocked it for trim, zero, and block_status. The NBD protocol also has documented rules on handling access beyond EOF, but we are currently wasting traffic to the server when we can give the same answer ourselves. Exposing this as a strictness knob gives the user finer-grained control over what behavior they want. --- Question: should this be split into two flags, one to prevent 0-length requests, and the other to prevent out-of-bounds requests? --- generator/API.ml | 7 ++++ lib/handle.c | 2 +- lib/rw.c | 87 ++++++...