mirror of
https://github.com/capstone-engine/llvm-capstone.git
synced 2024-11-27 07:31:28 +00:00
0a6b5b653e
When debugging a boost build with a modified version of Clang, I discovered that the PTH implementation stores TokenKind in 8 bits. However, we currently have 368 TokenKinds. The result is that the value gets truncated and the wrong token gets picked up when including PTH files. It seems that this will go wrong every time someone uses a token that uses the 9th bit. Upon asking on IRC, it was brought up that this was a highly experimental features that was considered a failure. I discovered via googling that BoostBuild (mostly Boost.Math) is the only user of this feature, using the CC1 flag directly. I believe that this can be transferred over to normal PCH with minimal effort: https://github.com/boostorg/build/issues/367 Based on advice on IRC and research showing that this is a nearly completely unused feature, this patch removes it entirely. Note: I considered leaving the build-flags in place and making them emit an error/warning, however since I've basically identified and warned the only user, it seemed better to just remove them. Differential Revision: https://reviews.llvm.org/D54547 Change-Id: If32744275ef1f585357bd6c1c813d96973c4d8d9 llvm-svn: 348266
105 lines
4.0 KiB
Plaintext
105 lines
4.0 KiB
Plaintext
//===---------------------------------------------------------------------===//
|
|
// Random Notes
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
To time GCC preprocessing speed without output, use:
|
|
"time gcc -MM file"
|
|
This is similar to -Eonly.
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
C++ Template Instantiation benchmark:
|
|
http://users.rcn.com/abrahams/instantiation_speed/index.html
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
TODO: File Manager Speedup:
|
|
|
|
We currently do a lot of stat'ing for files that don't exist, particularly
|
|
when lots of -I paths exist (e.g. see the <iostream> example, check for
|
|
failures in stat in FileManager::getFile). It would be far better to make
|
|
the following changes:
|
|
1. FileEntry contains a sys::Path instead of a std::string for Name.
|
|
2. sys::Path contains timestamp and size, lazily computed. Eliminate from
|
|
FileEntry.
|
|
3. File UIDs are created on request, not when files are opened.
|
|
These changes make it possible to efficiently have FileEntry objects for
|
|
files that exist on the file system, but have not been used yet.
|
|
|
|
Once this is done:
|
|
1. DirectoryEntry gets a boolean value "has read entries". When false, not
|
|
all entries in the directory are in the file mgr, when true, they are.
|
|
2. Instead of stat'ing the file in FileManager::getFile, check to see if
|
|
the dir has been read. If so, fail immediately, if not, read the dir,
|
|
then retry.
|
|
3. Reading the dir uses the getdirentries syscall, creating a FileEntry
|
|
for all files found.
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
// Specifying targets: -triple and -arch
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
The clang supports "-triple" and "-arch" options. At most one -triple and one
|
|
-arch option may be specified. Both are optional.
|
|
|
|
The "selection of target" behavior is defined as follows:
|
|
|
|
(1) If the user does not specify -triple, we default to the host triple.
|
|
(2) If the user specifies a -arch, that overrides the arch in the host or
|
|
specified triple.
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
|
|
verifyInputConstraint and verifyOutputConstraint should not return bool.
|
|
|
|
Instead we should return something like:
|
|
|
|
enum VerifyConstraintResult {
|
|
Valid,
|
|
|
|
// Output only
|
|
OutputOperandConstraintLacksEqualsCharacter,
|
|
MatchingConstraintNotValidInOutputOperand,
|
|
|
|
// Input only
|
|
InputOperandConstraintContainsEqualsCharacter,
|
|
MatchingConstraintReferencesInvalidOperandNumber,
|
|
|
|
// Both
|
|
PercentConstraintUsedWithLastOperand
|
|
};
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
Blocks should not capture variables that are only used in dead code.
|
|
|
|
The rule that we came up with is that blocks are required to capture
|
|
variables if they're referenced in evaluated code, even if that code
|
|
doesn't actually rely on the value of the captured variable.
|
|
|
|
For example, this requires a capture:
|
|
(void) var;
|
|
But this does not:
|
|
if (false) puts(var);
|
|
|
|
Summary of <rdar://problem/9851835>: if we implement this, we should
|
|
warn about non-POD variables that are referenced but not captured, but
|
|
only if the non-reachability is not due to macro or template
|
|
metaprogramming.
|
|
|
|
//===---------------------------------------------------------------------===//
|
|
|
|
We can still apply a modified version of the constructor/destructor
|
|
delegation optimization in cases of virtual inheritance where:
|
|
- there is no function-try-block,
|
|
- the constructor signature is not variadic, and
|
|
- the parameter variables can safely be copied and repassed
|
|
to the base constructor because either
|
|
- they have not had their addresses taken by the vbase initializers or
|
|
- they were passed indirectly.
|
|
|
|
//===---------------------------------------------------------------------===//
|