Searched refs:forbid (Results 1 – 25 of 132) sorted by relevance
123456
3 < forbid W
3 < forbid 8W
8 < forbid 8W
4 < forbid W
6 < forbid 8W
5 < forbid 8W
5 < forbid 9?=ABCDEFfGILMNPTUWXZ<
5 < forbid W
809 * We forbid instructions that directly interact with the operating813 * We forbid instructions that change the processor's execution mode to817 * We forbid instructions that aren't available to user code (i.e. have823 * We forbid instructions, or variants of instructions, that are826 * Finally, we forbid a small number of instructions, such as ``setend``,
251 // For now we have no reason to forbid this on other MacOS as we don't
518 xmlParse3986Segment(const char **str, char forbid, int empty) in xmlParse3986Segment() argument528 while (ISA_PCHAR(cur) && (*cur != forbid)) in xmlParse3986Segment()
549 xmlParse3986Segment(const char **str, char forbid, int empty) in xmlParse3986Segment() argument559 while (ISA_PCHAR(cur) && (*cur != forbid)) in xmlParse3986Segment()
594 fiers. If an input line for pcretest starts with the string "< forbid "599 < forbid 8W607 < forbid <JS><cr>609 There must be a single space between < and "forbid" for this feature to