Searched refs:collide (Results 1 – 12 of 12) sorted by relevance
84 static NameCollisionResolution collide(Atom::Definition first, in collide() function130 switch (collide(existing->definition(), newAtom.definition())) { in addByName()
10 # VAX a.out (BSD; others collide with 386 and other 32-bit little-endian
12 # long, as it would be on a VAX. In any case, that could collide with
8 # (No other current magic entries collide.)
72 # I don't see why these might collide with anything else.
344 # filename of the first file (null terminated). Since some types collide369 # [GRR: the original entries collide with ARC, above; replaced with combined
44 If a B<BIGNUM> is equal to the value of all-bits-set, it will collide
5 // they don't collide with the ld64 compat options.
1552 // collide with the explicit nullary versions above. So I'm calling them
1022 …name clash, OPT_OUTFILE from parse.y and from options.h these collide: OPT_OUTFILE OPT_PREFIX OP…
8265 # remove ncv#3 [colors collide with highlights, bitmask] not applicable
39396 collide