Searched defs:Not (Results 1 - 25 of 37) sorted by relevance

12

/external/deqp/framework/delibs/decpp/
H A DdeMeta.hpp43 struct Not struct in namespace:de::meta
/external/mockito/src/main/java/org/mockito/internal/matchers/
H A DNot.java13 public class Not implements ArgumentMatcher<Object>, Serializable { class in inherits:ArgumentMatcher,Serializable
17 public Not(ArgumentMatcher<?> matcher) { method in class:Not
/external/easymock/src/org/easymock/internal/matchers/
H A DNot.java22 public class Not implements IArgumentMatcher, Serializable { class in inherits:IArgumentMatcher,Serializable
28 public Not(IArgumentMatcher first) { method in class:Not
/external/clang/include/clang/Analysis/Analyses/
H A DThreadSafetyLogical.h28 Not enumerator in enum:clang::threadSafety::lexpr::LExpr::Opcode
83 class Not : public LExpr { class in namespace:clang::threadSafety::lexpr
87 Not(LExpr *Exp) : LExpr(LExpr::Not), Exp(Exp) {} function in class:clang::threadSafety::lexpr::Not
92 static bool classof(const LExpr *E) { return E->kind() == LExpr::Not; }
/external/python/cpython3/Lib/test/
H A Dtest_sundry.py50 import tty # Not available on Windows namespace
/external/skia/src/core/
H A DSkRecordPattern.h79 struct Not { struct in namespace:SkRecords
/external/skqp/src/core/
H A DSkRecordPattern.h79 struct Not { struct in namespace:SkRecords
/external/guice/core/src/com/google/inject/matcher/
H A DMatchers.java66 return new Not<T>(p);
69 private static class Not<T> extends AbstractMatcher<T> implements Serializable { class in class:Matchers
72 private Not(Matcher<? super T> delegate) { method in class:Matchers.Not
81 return other instanceof Not
82 && ((Not) other).delegate.equals(delegate);
/external/libmojo/third_party/jinja2/
H A Dnodes.py781 class Not(UnaryExpr): class in inherits:UnaryExpr
/external/llvm/include/llvm/MC/
H A DMCExpr.h335 Not, ///< Bitwise negation. enumerator in enum:llvm::MCUnaryExpr::Opcode
359 return create(Not, Expr, Ctx);
/external/python/cpython2/Lib/compiler/
H A Dast.py997 class Not(Node): class in inherits:Node
1009 return "Not(%s)" % (repr(self.expr),)
/external/llvm/lib/Target/WebAssembly/
H A DWebAssemblyFastISel.cpp126 unsigned getRegForI1Value(const Value *V, bool &Not);
365 unsigned WebAssemblyFastISel::getRegForI1Value(const Value *V, bool &Not) { argument
369 Not = ICmp->isTrueWhenEqual();
374 Not = true;
378 Not = false;
719 bool Not; local
720 unsigned CondReg = getRegForI1Value(Select->getCondition(), Not);
732 if (Not)
891 bool Not = false; local
913 Not
1095 bool Not; local
[all...]
/external/swiftshader/third_party/LLVM/include/llvm/MC/
H A DMCExpr.h233 Not, ///< Bitwise negation. enumerator in enum:llvm::MCUnaryExpr::Opcode
257 return Create(Not, Expr, Ctx);
/external/llvm/lib/Transforms/InstCombine/
H A DInstCombineAndOrXor.cpp421 /// The Part "Not" means, that in above descriptions "==" should be replaced
1188 Value *Not = Builder->CreateNot(LogicOp); local
1189 return CastInst::CreateZExtOrBitCast(Not, I.getType());
1285 // Canonicalize SExt or Not to the LHS
1346 // Not masking anything out for the LHS, move to RHS.
1353 // Not masking anything out for the RHS, move to LHS.
1942 // If RHSCst is [us]MAXINT, it is always false. Not handling
1962 // If RHSCst is [us]MAXINT, it is always false. Not handling
2366 Value *Not = Builder->CreateNot(B, B->getName()+".not"); local
2367 return BinaryOperator::CreateOr(Not, Op
2370 Value *Not = Builder->CreateNot(A, A->getName()+".not"); local
2384 Value *Not = Builder->CreateNot(NotOp, NotOp->getName()+".not"); local
[all...]
H A DInstCombineCompares.cpp2414 // Not an extension from the same type?
3207 Value *Not = Builder->CreateNot(Op0, I.getName() + "tmp"); local
3208 return BinaryOperator::CreateAnd(Not, Op1);
3214 Value *Not = Builder->CreateNot(Op1, I.getName() + "tmp"); local
3215 return BinaryOperator::CreateAnd(Not, Op0);
3221 Value *Not = Builder->CreateNot(Op0, I.getName() + "tmp"); local
3222 return BinaryOperator::CreateOr(Not, Op1);
3228 Value *Not = Builder->CreateNot(Op1, I.getName() + "tmp"); local
3229 return BinaryOperator::CreateOr(Not, Op0);
/external/python/cpython2/Include/
H A DPython-ast.h22 typedef enum _unaryop { Invert=1, Not=2, UAdd=3, USub=4 } unaryop_ty; enumerator in enum:_unaryop
/external/swiftshader/third_party/LLVM/lib/Transforms/InstCombine/
H A DInstCombineAndOrXor.cpp131 // Not expecting FCMP_FALSE and FCMP_TRUE;
470 /// The Part "Not" means, that in above descriptions "==" should be replaced
651 mask >>= 1; // treat "Not"-states as normal states
1065 // Not masking anything out for the LHS, move to RHS.
1072 // Not masking anything out for the RHS, move to LHS.
1596 // If RHSCst is [us]MAXINT, it is always false. Not handling
1616 // If RHSCst is [us]MAXINT, it is always false. Not handling
1975 Value *Not = Builder->CreateNot(B, B->getName()+".not"); local
1976 return BinaryOperator::CreateOr(Not, Op0);
1979 Value *Not local
1993 Value *Not = Builder->CreateNot(NotOp, NotOp->getName()+".not"); local
[all...]
H A DInstCombineCompares.cpp1554 // Not an extension from the same type?
1807 Value *Not = Builder->CreateNot(Op0, I.getName()+"tmp"); local
1808 return BinaryOperator::CreateAnd(Not, Op1);
1814 Value *Not = Builder->CreateNot(Op1, I.getName()+"tmp"); local
1815 return BinaryOperator::CreateAnd(Not, Op0);
1821 Value *Not = Builder->CreateNot(Op0, I.getName()+"tmp"); local
1822 return BinaryOperator::CreateOr(Not, Op1);
1828 Value *Not = Builder->CreateNot(Op1, I.getName()+"tmp"); local
1829 return BinaryOperator::CreateOr(Not, Op0);
/external/google-breakpad/src/testing/include/gmock/
H A Dgmock-matchers.h719 // to write Not(A<bool>()). However we cannot completely rule out
1204 // Implements the Not(...) matcher for a particular argument type T.
1232 // Implements the Not(m) matcher, which matches a value that doesn't
1239 // This template type conversion operator allows Not(m) to be used
2763 // This is convenient as Not(NULL) doesn't compile (the compiler
3025 inline internal::NotMatcher<InnerMatcher> Not(InnerMatcher m) { function in namespace:testing
3099 // EXPECT_THAT(page_ids, Not(Contains(4)));
3116 // Each(m) is semantically equivalent to Not(Contains(Not(m))). Only
3127 // EXPECT_THAT(page_ids, Not(Eac
[all...]
/external/python/cpython3/Include/
H A DPython-ast.h22 typedef enum _unaryop { Invert=1, Not=2, UAdd=3, USub=4 } unaryop_ty; enumerator in enum:_unaryop
/external/tensorflow/tensorflow/compiler/xla/client/
H A Dcomputation_builder.cc440 // Not collapsing anything, trivially we can return the operand versus
871 ComputationDataHandle ComputationBuilder::Not( function in class:xla::ComputationBuilder
/external/googletest/googlemock/include/gmock/
H A Dgmock-matchers.h159 // Not()).
866 // to write Not(A<bool>()). However we cannot completely rule out
1439 // Implements the Not(...) matcher for a particular argument type T.
1467 // Implements the Not(m) matcher, which matches a value that doesn't
1474 // This template type conversion operator allows Not(m) to be used
3801 // This is convenient as Not(NULL) doesn't compile (the compiler
4124 inline internal::NotMatcher<InnerMatcher> Not(InnerMatcher m) { function in namespace:testing
4289 // EXPECT_THAT(page_ids, Not(Contains(4)));
4306 // Each(m) is semantically equivalent to Not(Contains(Not(
[all...]
/external/llvm/lib/Target/AMDGPU/
H A DAMDGPUISelLowering.cpp1675 SDValue Not = DAG.getNOT(SL, Shr, MVT::i64); local
1676 SDValue Tmp0 = DAG.getNode(ISD::AND, SL, MVT::i64, BcInt, Not);
/external/llvm/lib/Target/Mips/
H A DMipsISelLowering.cpp2186 SDValue Not = DAG.getNode(ISD::XOR, DL, MVT::i32, Shamt, local
2190 SDValue ShiftRightLo = DAG.getNode(ISD::SRL, DL, VT, ShiftRight1Lo, Not);
2224 SDValue Not = DAG.getNode(ISD::XOR, DL, MVT::i32, Shamt, local
2228 SDValue ShiftLeftHi = DAG.getNode(ISD::SHL, DL, VT, ShiftLeft1Hi, Not);
3552 // Fixme: Not triggering the use of both hi and low
/external/python/cpython2/Lib/pydoc_data/
H A Dtopics.py14 'bltin-file-objects': u'\nFile Objects\n************\n\nFile objects are implemented using C\'s "stdio" package and can be\ncreated with the built-in "open()" function. File objects are also\nreturned by some other built-in functions and methods, such as\n"os.popen()" and "os.fdopen()" and the "makefile()" method of socket\nobjects. Temporary files can be created using the "tempfile" module,\nand high-level file operations such as copying, moving, and deleting\nfiles and directories can be achieved with the "shutil" module.\n\nWhen a file operation fails for an I/O-related reason, the exception\n"IOError" is raised. This includes situations where the operation is\nnot defined for some reason, like "seek()" on a tty device or writing\na file opened for reading.\n\nFiles have the following methods:\n\nfile.close()\n\n Close the file. A closed file cannot be read or written any more.\n Any operation which requires that the file be open will raise a\n "ValueError" after the file has been closed. Calling "close()"\n more than once is allowed.\n\n As of Python 2.5, you can avoid having to call this method\n explicitly if you use the "with" statement. For example, the\n following code will automatically close *f* when the "with" block\n is exited:\n\n from __future__ import with_statement # This isn\'t required in Python 2.6\n\n with open("hello.txt") as f:\n for line in f:\n print line,\n\n In older versions of Python, you would have needed to do this to\n get the same effect:\n\n f = open("hello.txt")\n try:\n for line in f:\n print line,\n finally:\n f.close()\n\n Note: Not all "file-like" types in Python support use as a\n context manager for the "with" statement. If your code is\n intended to work with any file-like object, you can use the\n function "contextlib.closing()" instead of using the object\n directly.\n\nfile.flush()\n\n Flush the internal buffer, like "stdio"\'s "fflush()". This may be\n a no-op on some file-like objects.\n\n Note: "flush()" does not necessarily write the file\'s data to\n disk. Use "flush()" followed by "os.fsync()" to ensure this\n behavior.\n\nfile.fileno()\n\n Return the integer "file descriptor" that is used by the underlying\n implementation to request I/O operations from the operating system.\n This can be useful for other, lower level interfaces that use file\n descriptors, such as the "fcntl" module or "os.read()" and friends.\n\n Note: File-like objects which do not have a real file descriptor\n should *not* provide this method!\n\nfile.isatty()\n\n Return "True" if the file is connected to a tty(-like) device, else\n "False".\n\n Note: If a file-like object is not associated with a real file,\n this method should *not* be implemented.\n\nfile.next()\n\n A file object is its own iterator, for example "iter(f)" returns\n *f* (unless *f* is closed). When a file is used as an iterator,\n typically in a "for" loop (for example, "for line in f: print\n line.strip()"), the "next()" method is called repeatedly. This\n method returns the next input line, or raises "StopIteration" when\n EOF is hit when the file is open for reading (behavior is undefined\n when the file is open for writing). In order to make a "for" loop\n the most efficient way of looping over the lines of a file (a very\n common operation), the "next()" method uses a hidden read-ahead\n buffer. As a consequence of using a read-ahead buffer, combining\n "next()" with other file methods (like "readline()") does not work\n right. However, using "seek()" to reposition the file to an\n absolute position will flush the read-ahead buffer.\n\n New in version 2.3.\n\nfile.read([size])\n\n Read at most *size* bytes from the file (less if the read hits EOF\n before obtaining *size* bytes). If the *size* argument is negative\n or omitted, read all data until EOF is reached. The bytes are\n returned as a string object. An empty string is returned when EOF\n is encountered immediately. (For certain files, like ttys, it\n makes sense to continue reading after an EOF is hit.) Note that\n this method may call the underlying C function "fread()" more than\n once in an effort to acquire as close to *size* bytes as possible.\n Also note that when in non-blocking mode, less data than was\n requested may be returned, even if no *size* parameter was given.\n\n Note: This function is simply a wrapper for the underlying\n "fread()" C function, and will behave the same in corner cases,\n such as whether the EOF value is cached.\n\nfile.readline([size])\n\n Read one entire line from the file. A trailing newline character\n is kept in the string (but may be absent when a file ends with an\n incomplete line). [6] If the *size* argument is present and non-\n negative, it is a maximum byte count (including the trailing\n newline) and an incomplete line may be returned. When *size* is not\n 0, an empty string is returned *only* when EOF is encountered\n immediately.\n\n Note: Unlike "stdio"\'s "fgets()", the returned string contains\n null characters ("\'\\0\'") if they occurred in the input.\n\nfile.readlines([sizehint])\n\n Read until EOF using "readline()" and return a list containing the\n lines thus read. If the optional *sizehint* argument is present,\n instead of reading up to EOF, whole lines totalling approximately\n *sizehint* bytes (possibly after rounding up to an internal buffer\n size) are read. Objects implementing a file-like interface may\n choose to ignore *sizehint* if it cannot be implemented, or cannot\n be implemented efficiently.\n\nfile.xreadlines()\n\n This method returns the same thing as "iter(f)".\n\n New in version 2.1.\n\n Deprecated since version 2.3: Use "for line in file" instead.\n\nfile.seek(offset[, whence])\n\n Set the file\'s current position, like "stdio"\'s "fseek()". The\n *whence* argument is optional and defaults to "os.SEEK_SET" or "0"\n (absolute file positioning); other values are "os.SEEK_CUR" or "1"\n (seek relative to the current position) and "os.SEEK_END" or "2"\n (seek relative to the file\'s end). There is no return value.\n\n For example, "f.seek(2, os.SEEK_CUR)" advances the position by two\n and "f.seek(-3, os.SEEK_END)" sets the position to the third to\n last.\n\n Note that if the file is opened for appending (mode "\'a\'" or\n "\'a+\'"), any "seek()" operations will be undone at the next write.\n If the file is only opened for writing in append mode (mode "\'a\'"),\n this method is essentially a no-op, but it remains useful for files\n opened in append mode with reading enabled (mode "\'a+\'"). If the\n file is opened in text mode (without "\'b\'"), only offsets returned\n by "tell()" are legal. Use of other offsets causes undefined\n behavior.\n\n Note that not all file objects are seekable.\n\n Changed in version 2.6: Passing float values as offset has been\n deprecated.\n\nfile.tell()\n\n Return the file\'s current position, like "stdio"\'s "ftell()".\n\n Note: On Windows, "tell()" can return illegal values (after an\n "fgets()") when reading files with Unix-style line-endings. Use\n binary mode ("\'rb\'") to circumvent this problem.\n\nfile.truncate([size])\n\n Truncate the file\'s size. If the optional *size* argument is\n present, the file is truncated to (at most) that size. The size\n defaults to the current position. The current file position is not\n changed. Note that if a specified size exceeds the file\'s current\n size, the result is platform-dependent: possibilities include that\n the file may remain unchanged, increase to the specified size as if\n zero-filled, or increase to the specified size with undefined new\n content. Availability: Windows, many Unix variants.\n\nfile.write(str)\n\n Write a string to the file. There is no return value. Due to\n buffering, the string may not actually show up in the file until\n the "flush()" or "close()" method is called.\n\nfile.writelines(sequence)\n\n Write a sequence of strings to the file. The sequence can be any\n iterable object producing strings, typically a list of strings.\n There is no return value. (The name is intended to match\n "readlines()"; "writelines()" does not add line separators.)\n\nFiles support the iterator protocol. Each iteration returns the same\nresult as "readline()", and iteration ends when the "readline()"\nmethod returns an empty string.\n\nFile objects also offer a number of other interesting attributes.\nThese are not required for file-like objects, but should be\nimplemented if they make sense for the particular object.\n\nfile.closed\n\n bool indicating the current state of the file object. This is a\n read-only attribute; the "close()" method changes the value. It may\n not be available on all file-like objects.\n\nfile.encoding\n\n The encoding that this file uses. When Unicode strings are written\n to a file, they will be converted to byte strings using this\n encoding. In addition, when the file is connected to a terminal,\n the attribute gives the encoding that the terminal is likely to use\n (that information might be incorrect if the user has misconfigured\n the terminal). The attribute is read-only and may not be present\n on all file-like objects. It may also be "None", in which case the\n file uses the system default encoding for converting Unicode\n strings.\n\n New in version 2.3.\n\nfile.errors\n\n The Unicode error handler used along with the encoding.\n\n New in version 2.6.\n\nfile.mode\n\n The I/O mode for the file. If the file was created using the\n "open()" built-in function, this will be the value of the *mode*\n parameter. This is a read-only attribute and may not be present on\n all file-like objects.\n\nfile.name\n\n If the file object was created using "open()", the name of the\n file. Otherwise, some string that indicates the source of the file\n object, of the form "<...>". This is a read-only attribute and may\n not be present on all file-like objects.\n\nfile.newlines\n\n If Python was built with *universal newlines* enabled (the default)\n this read-only attribute exists, and for files opened in universal\n newline read mode it keeps track of the types of newlines\n encountered while reading the file. The values it can take are\n "\'\\r\'", "\'\\n\'", "\'\\r\\n\'", "None" (unknown, no newlines read yet) or\n a tuple containing all the newline types seen, to indicate that\n multiple newline conventions were encountered. For files not opened\n in universal newlines read mode the value of this attribute will be\n "None".\n\nfile.softspace\n\n Boolean that indicates whether a space character needs to be\n printed before another value when using the "print" statement.\n Classes that are trying to simulate a file object should also have\n a writable "softspace" attribute, which should be initialized to\n zero. This will be automatic for most classes implemented in\n Python (care may be needed for objects that override attribute\n access); types implemented in C will have to provide a writable\n "softspace" attribute.\n\n Note: This attribute is not used to control the "print"\n statement, but to allow the implementation of "print" to keep\n track of its internal state.\n',
42 'id-classes': u'\nReserved classes of identifiers\n*******************************\n\nCertain classes of identifiers (besides keywords) have special\nmeanings. These classes are identified by the patterns of leading and\ntrailing underscore characters:\n\n"_*"\n Not imported by "from module import *". The special identifier "_"\n is used in the interactive interpreter to store the result of the\n last evaluation; it is stored in the "__builtin__" module. When\n not in interactive mode, "_" has no special meaning and is not\n defined. See section The import statement.\n\n Note: The name "_" is often used in conjunction with\n internationalization; refer to the documentation for the\n "gettext" module for more information on this convention.\n\n"__*__"\n System-defined names. These names are defined by the interpreter\n and its implementation (including the standard library). Current\n system names are discussed in the Special method names section and\n elsewhere. More will likely be defined in future versions of\n Python. *Any* use of "__*__" names, in any context, that does not\n follow explicitly documented use, is subject to breakage without\n warning.\n\n"__*"\n Class-private names. Names in this category, when used within the\n context of a class definition, are re-written to use a mangled form\n to help avoid name clashes between "private" attributes of base and\n derived classes. See section Identifiers (Names).\n',
43 'identifiers': u'\nIdentifiers and keywords\n************************\n\nIdentifiers (also referred to as *names*) are described by the\nfollowing lexical definitions:\n\n identifier ::= (letter|"_") (letter | digit | "_")*\n letter ::= lowercase | uppercase\n lowercase ::= "a"..."z"\n uppercase ::= "A"..."Z"\n digit ::= "0"..."9"\n\nIdentifiers are unlimited in length. Case is significant.\n\n\nKeywords\n========\n\nThe following identifiers are used as reserved words, or *keywords* of\nthe language, and cannot be used as ordinary identifiers. They must\nbe spelled exactly as written here:\n\n and del from not while\n as elif global or with\n assert else if pass yield\n break except import print\n class exec in raise\n continue finally is return\n def for lambda try\n\nChanged in version 2.4: "None" became a constant and is now recognized\nby the compiler as a name for the built-in object "None". Although it\nis not a keyword, you cannot assign a different object to it.\n\nChanged in version 2.5: Using "as" and "with" as identifiers triggers\na warning. To use them as keywords, enable the "with_statement"\nfuture feature .\n\nChanged in version 2.6: "as" and "with" are full keywords.\n\n\nReserved classes of identifiers\n===============================\n\nCertain classes of identifiers (besides keywords) have special\nmeanings. These classes are identified by the patterns of leading and\ntrailing underscore characters:\n\n"_*"\n Not imported by "from module import *". The special identifier "_"\n is used in the interactive interpreter to store the result of the\n last evaluation; it is stored in the "__builtin__" module. When\n not in interactive mode, "_" has no special meaning and is not\n defined. See section The import statement.\n\n Note: The name "_" is often used in conjunction with\n internationalization; refer to the documentation for the\n "gettext" module for more information on this convention.\n\n"__*__"\n System-defined names. These names are defined by the interpreter\n and its implementation (including the standard library). Current\n system names are discussed in the Special method names section and\n elsewhere. More will likely be defined in future versions of\n Python. *Any* use of "__*__" names, in any context, that does not\n follow explicitly documented use, is subject to breakage without\n warning.\n\n"__*"\n Class-private names. Names in this category, when used within the\n context of a class definition, are re-written to use a mangled form\n to help avoid name clashes between "private" attributes of base and\n derived classes. See section Identifiers (Names).\n', namespace

Completed in 3037 milliseconds

12