HomeSort by: relevance | last modified time | path
    Searched refs:was (Results 1 - 25 of 129) sorted by relevancy

1 2 3 4 5 6

  /src/usr.bin/make/unit-tests/
varname-dot-objdir.exp 1 : purge-cache was reached.
counter-append.mk 7 # 6 words, even though the NEXT variable was only accessed 3 times.
8 # The cause for this surprising behavior was that the ::= variable modifiers
counter.mk 7 # 4 words, even though the NEXT variable was only accessed 3 times.
8 # The cause for this surprising behavior was that the ::= variable modifiers
var-scope-cmdline.mk 39 # was not entirely equivalent to the simple rule though. The mistake was
40 # that when a cmdline variable with '$$' in its name was added, a global
41 # variable was deleted, but not with the exact same name as the cmdline
42 # variable. Instead, the name of the global variable was expanded one more
44 # have a '$$' in their name, it was implemented correctly all the time.
46 # The bug was added in var.c 1.183 on 2013-07-16, when Var_Set called
50 # row. This bug was fixed in var.c 1.835 from 2021-02-22.
52 # Another bug was the wrong assumption that "deleting a cmdline variable is
55 # temporary loop variable after finishing the loop. It was probably no
    [all...]
unexport.mk 12 # was not reachable though. At that point, backslash-newline has already
deptgt-end-fail.mk 7 # even though this was intended. The cause for this was a missing condition
66 # Until 2020-12-07, '.END' was even made if 'all' failed, but if a dependency
67 # of 'all' failed, it was skipped. This inconsistency was not needed for
cond-eof.mk 11 # parse error. Before cond.c 1.286 from 2021-12-10, it was always fully
12 # evaluated, even if it was not necessary to expand the expression.
opt-debug-lint.mk 10 # error message was "Malformed conditional" only, which was wrong and
41 # conditional was well-formed and the only error was an undefined variable.
48 # Before, undefined variables were forbidden, but this distinction was not
70 # variable modifier had to be separated by colons. This was wrong though
92 # Before var.c 1.856 from 2021-03-14, this regular expression was then
93 # compiled even though that was not necessary for checking the syntax at the
varmod-gmtime.mk 47 # Before var.c 1.1050 from 2023-05-09, it was not possible to pass the
54 # Before var.c 1.631 from 2020-10-31 21:40:20, it was possible to pass
110 # Because this modifier is implemented using strtoul, the parsed time was
123 # Before var.c 1.631 from 2020-10-31, there was no error handling while
124 # parsing the :gmtime modifier, thus no error message was printed. Parsing
125 # stopped after the '=', and the remaining string was parsed for more variable
127 # variable value was discarded and thus not printed.
136 # followed by the next modifier, without a ':' separator. This was the same
varmod-to-abs.mk 8 # Between 2016-06-03 and 2020-11-14, it was possible to trick the :tA modifier
14 # This unintended behavior was caused by cached_realpath using a GNode for
dep-colon-bug-cross-file.mk 4 # was not finished properly. This made it possible to add further commands
14 # which was still the one from pass 1, which means it was possible to later
cond-short.mk 9 # Before 2020-06-28, the right-hand side of an && or || operator was always
10 # evaluated, which was wrong. In cond.c 1.69 and var.c 1.197 on 2015-10-11,
14 # relevant expressions was that in the irrelevant
17 # error message 'Malformed conditional', but the irrelevant expression was
22 # but that was wrong. The code in cond.c 1.1 from 1993-03-21 looks good since
53 # "VAR U11" is not evaluated; it was evaluated before 2020-07-02.
67 # Before 2020-07-02, it was wrongly evaluated.
154 # On the right-hand side of the '&&', the expression ${INDIR_UNDEF} was
155 # defined and had the value '${UNDEF}', but the nested variable UNDEF was
157 # and in parse-only mode, the "value" of the parsed expression was th
    [all...]
cond-func-empty.mk 59 # Since the variable was undefined to begin with, the fallback value from the
179 # conditions were not evaluated, but that was wrong for a long time. The
188 # side containing the '!empty' was evaluated though, as it had always been.
190 # When evaluating the !empty condition, the variable name was parsed as
192 # this case the ${:U2}. The expression '${:U2}' was replaced with an empty
193 # string, the resulting variable name was thus "VARNAME". This conceptually
197 # The expression was evaluated, and this was wrong. The evaluation was done
201 # VARNAME=${VARNAME}, and that definition was evaluated even though it wa
    [all...]
var-op-append.mk 17 # The '+=' variable assignment operator was added before 1993-03-21.
49 # variable was expanded two times in a row, which was unexpected but
varmod-ifelse.mk 6 # The modifier was added on 1998-04-01.
125 # Despite the error message (which was not clearly marked with "error:"),
212 # parsed differently, depending on whether the branch was taken or not. When
213 # the branch was taken, the parser recognized that in the modifier ':S,}},,',
214 # the '}}' were ordinary characters. When the branch was not taken, the
220 # unbalanced braces in the ':S' modifiers into account. This change was not
221 # on purpose, the commit message mentioned 'has the same effect', which was a
224 # In var.c 1.323 from 2020-07-26, the unintended fix from var.c 1.285 was
228 # In var.c 1.1028 from 2022-08-08, there was another attempt at fixing this
230 # it was reverted in var.c 1.1029 from 2022-08-23
    [all...]
  /src/common/lib/libc/quad/
muldi3.c 7 * This software was developed by the Computer Systems Engineering group
196 u_int prodh, prodl, was; local
229 was = prodl;
231 prodh -= HHALF(mid) + (prodl > was);
233 was = prodl;
235 prodh += HHALF(mid) + (prodl < was);
239 was = prodl;
241 prodh += HHALF(low) + (prodl < was);
  /src/sys/arch/m68k/060sp/dist/
changes 41 1) "movep" emulation where data was being read from memory
42 was reading the intermediate bytes. Emulation now only
45 2) "flogn", "flog2", and "flog10" of "1" was setting the
50 mode was pre-decrement or post-increment and the address register
51 was A0 or A1, the address register was not being updated as a result
readme 67 was connected properly; hex image
70 itest.sa Simple test program to test that isp.sa was
  /src/lib/libc/arch/powerpc64/gen/
swapcontext.S 44 std %r3,SF_PARAM(%r1) # must save oucp (was 8)
45 std %r4,SF_PARAM+8(%r1) # must save ucp (was 12)
  /src/lib/libc/arch/vax/gen/
__sigsetjmp14.S 60 tstl (_JBLEN*4)(%r0) # test if "savemask" was set
  /src/common/dist/zlib/examples/
gun.c 519 struct stat was; local
523 if (stat(from, &was) != 0 || (was.st_mode & S_IFMT) != S_IFREG)
527 (void)chmod(to, was.st_mode & 07777);
530 (void)chown(to, was.st_uid, was.st_gid);
533 when.actime = was.st_atime;
534 when.modtime = was.st_mtime;
  /src/sys/arch/sh3/sh3/
lock_stubs.S 95 !! T bit still indicates if cas was successful
117 !! T bit still indicates if cas was successful
  /src/usr.sbin/sysinst/arch/evbarm/
msg.md.en 78 {The RPI kernel was not installed, perhaps you didn't select it?}
  /src/common/dist/zlib/
inflate.h 125 unsigned was; /* initial length of match */ member in struct:inflate_state
  /src/sys/arch/sparc64/sparc64/
lock_stubs.s 62 brnz,pn %o1, 1f ! lock was unowned?

Completed in 867 milliseconds

1 2 3 4 5 6