1 //===---------------------------------------------------------------------===//
3 //===---------------------------------------------------------------------===//
5 C90/C99/C++ Comparisons:
6 http://david.tribble.com/text/cdiffs.htm
8 //===---------------------------------------------------------------------===//
10 To time GCC preprocessing speed without output, use:
12 This is similar to -Eonly.
14 //===---------------------------------------------------------------------===//
16 Creating and using a PTH file for performance measurement (use a release build).
18 $ clang -ccc-pch-is-pth -x objective-c-header INPUTS/Cocoa_h.m -o /tmp/tokencache
19 $ clang -cc1 -token-cache /tmp/tokencache INPUTS/Cocoa_h.m
21 //===---------------------------------------------------------------------===//
23 C++ Template Instantiation benchmark:
24 http://users.rcn.com/abrahams/instantiation_speed/index.html
26 //===---------------------------------------------------------------------===//
28 TODO: File Manager Speedup:
30 We currently do a lot of stat'ing for files that don't exist, particularly
31 when lots of -I paths exist (e.g. see the <iostream> example, check for
32 failures in stat in FileManager::getFile). It would be far better to make
33 the following changes:
34 1. FileEntry contains a sys::Path instead of a std::string for Name.
35 2. sys::Path contains timestamp and size, lazily computed. Eliminate from
37 3. File UIDs are created on request, not when files are opened.
38 These changes make it possible to efficiently have FileEntry objects for
39 files that exist on the file system, but have not been used yet.
42 1. DirectoryEntry gets a boolean value "has read entries". When false, not
43 all entries in the directory are in the file mgr, when true, they are.
44 2. Instead of stat'ing the file in FileManager::getFile, check to see if
45 the dir has been read. If so, fail immediately, if not, read the dir,
47 3. Reading the dir uses the getdirentries syscall, creating an FileEntry
50 //===---------------------------------------------------------------------===//
51 // Specifying targets: -triple and -arch
52 //===---------------------------------------------------------------------===//
54 The clang supports "-triple" and "-arch" options. At most one -triple and one
55 -arch option may be specified. Both are optional.
57 The "selection of target" behavior is defined as follows:
59 (1) If the user does not specify -triple, we default to the host triple.
60 (2) If the user specifies a -arch, that overrides the arch in the host or
63 //===---------------------------------------------------------------------===//
66 verifyInputConstraint and verifyOutputConstraint should not return bool.
68 Instead we should return something like:
70 enum VerifyConstraintResult {
74 OutputOperandConstraintLacksEqualsCharacter,
75 MatchingConstraintNotValidInOutputOperand,
78 InputOperandConstraintContainsEqualsCharacter,
79 MatchingConstraintReferencesInvalidOperandNumber,
82 PercentConstraintUsedWithLastOperand
85 //===---------------------------------------------------------------------===//