File: hints.txt

package info (click to toggle)
chromium 138.0.7204.183-1
  • links: PTS, VCS
  • area: main
  • in suites: trixie
  • size: 6,071,908 kB
  • sloc: cpp: 34,937,088; ansic: 7,176,967; javascript: 4,110,704; python: 1,419,953; asm: 946,768; xml: 739,971; pascal: 187,324; sh: 89,623; perl: 88,663; objc: 79,944; sql: 50,304; cs: 41,786; fortran: 24,137; makefile: 21,806; php: 13,980; tcl: 13,166; yacc: 8,925; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (26 lines) | stat: -rw-r--r-- 660 bytes parent folder | download | duplicates (31) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
 
Subject: Re: [nasm-devel] P4 insns
Date: Sat, 05 May 2001 11:39:36 -0500
From: Kyle Markley <kmarkley@seffera.net>
Reply-To: nasm-devel@yahoogroups.com
To: nasm-devel@yahoogroups.com

berkus wrote:
>
> Use The Source, NASM!
>
> Do we have the P4 'probable branch taken' (3e) and 'probable branch
> not taken' (2e) prefixes opcodes?

They're just segment override prefixes: 2e is CS, 3e is DS.  You can just
say
"cs jnz foo" for a not-taken hint, "ds jnz foo" for a taken hint.

Maybe it would be nice to have a more suggestive name, but you could just
%define one.

---
Kyle Markley



Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/