| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
llvm-svn: 59504
|
| |
|
|
| |
llvm-svn: 59503
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
are formed. In particular, a diagnostic with all its strings and ranges is now
packaged up and sent to DiagnosticClients as a DiagnosticInfo instead of as a
ton of random stuff. This has the benefit of simplifying the interface, making
it more extensible, and allowing us to do more checking for things like access
past the end of the various arrays passed in.
In addition to introducing DiagnosticInfo, this also substantially changes how
Diagnostic::Report works. Instead of being passed in all of the info required
to issue a diagnostic, Report now takes only the required info (a location and
ID) and returns a fresh DiagnosticInfo *by value*. The caller is then free to
stuff strings and ranges into the DiagnosticInfo with the << operator. When
the dtor runs on the DiagnosticInfo object (which should happen at the end of
the statement), the diagnostic is actually emitted with all of the accumulated
information. This is a somewhat tricky dance, but it means that the
accumulated DiagnosticInfo is allowed to keep pointers to other expression
temporaries without those pointers getting invalidated.
This is just the minimal change to get this stuff working, but this will allow
us to eliminate the zillions of variant "Diag" methods scattered throughout
(e.g.) sema. For example, instead of calling:
Diag(BuiltinLoc, diag::err_overload_no_match, typeNames,
SourceRange(BuiltinLoc, RParenLoc));
We will soon be able to just do:
Diag(BuiltinLoc, diag::err_overload_no_match)
<< typeNames << SourceRange(BuiltinLoc, RParenLoc));
This scales better to support arbitrary types being passed in (not just
strings) in a type-safe way. Go operator overloading?!
llvm-svn: 59502
|
| |
|
|
| |
llvm-svn: 59499
|
| |
|
|
|
|
| |
Use mutable to make it so.
llvm-svn: 59498
|
| |
|
|
|
|
| |
delete huge trailing whitespace to fit in 80 cols.
llvm-svn: 59497
|
| |
|
|
|
|
|
|
|
| |
- Use less indentation in coding.
- Shorten description.
- Update comments.
- Move code around
llvm-svn: 59496
|
| |
|
|
| |
llvm-svn: 59495
|
| |
|
|
|
|
|
|
| |
strings instead of array of strings. This reduces string copying
in some not-very-important cases, but paves the way for future
improvements.
llvm-svn: 59494
|
| |
|
|
| |
llvm-svn: 59493
|
| |
|
|
| |
llvm-svn: 59492
|
| |
|
|
| |
llvm-svn: 59491
|
| |
|
|
| |
llvm-svn: 59490
|
| |
|
|
| |
llvm-svn: 59489
|
| |
|
|
|
|
| |
a SelectionDAG*.
llvm-svn: 59488
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Running /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm.src/test/CodeGen/XCore/dg.exp ...
FAIL: /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm.src/test/CodeGen/XCore/fneg.ll
Failed with signal(SIGABRT) at line 1
while running: llvm-as < /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm.src/test/CodeGen/XCore/fneg.ll | llc -march=xcore > fneg.ll.tmp1.s
Assertion failed: (VT.isFloatingPoint() && "Cannot create integer FP constant!"), function getConstantFP, file /Volumes/Sandbox/Buildbot/llvm/full-llvm/build/llvm.src/lib/CodeGen/SelectionDAG/SelectionDAG.cpp, line 913.
0 llc 0x0092115c _ZN4llvm3sys18RemoveFileOnSignalERKNS0_4PathEPSs + 844
1 libSystem.B.dylib 0x9217809b _sigtramp + 43
2 ??? 0xffffffff 0x0 + 4294967295
3 libSystem.B.dylib 0x921f0ec2 raise + 26
4 libSystem.B.dylib 0x9220047f abort + 73
5 libSystem.B.dylib 0x921f2063 __assert_rtn + 101
6 llc 0x005a5b0a _ZN4llvm12SelectionDAG13getConmake[1]: *** [check-local] Error 1
make: *** [check] Error 2
llvm-svn: 59487
|
| |
|
|
|
|
|
|
|
| |
- Add static method to test if the current lexer is a non-macro/non-pragma
lexer.
- Refactor some code in PPLexerChange to use this static method.
- No performance change.
llvm-svn: 59486
|
| |
|
|
| |
llvm-svn: 59485
|
| |
|
|
| |
llvm-svn: 59484
|
| |
|
|
| |
llvm-svn: 59483
|
| |
|
|
| |
llvm-svn: 59482
|
| |
|
|
| |
llvm-svn: 59480
|
| |
|
|
|
|
|
| |
Performance tests on Cocoa.h (using the regular Lexer) shows no performance
difference.
llvm-svn: 59479
|
| |
|
|
| |
llvm-svn: 59478
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is because the PTHLexer will not support this method. Performance testing
on preprocessing Cocoa.h shows that this results in a negligible performance
difference (less than 1%).
I tried making Lexer::SetCommentRetentionState() an out-of-line function (a
precursor to making it a virtual function in PreprocessorLexer) and noticed a 1%
decrease in speed (it is called in a hot part of the Preprocessor).
llvm-svn: 59477
|
| |
|
|
|
|
| |
that are widely used.
llvm-svn: 59476
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
new CycleBound value. Instead, just update CycleBound on each call.
Also, make ReleasePred and ReleaseSucc methods more consistent accross
the various schedulers.
This also happens to make ScheduleDAGRRList's CycleBound computation
somewhat more interesting, though it still doesn't have any noticeable
effect, because no current targets that use the register-pressure
reduction scheduler provide pipeline models.
llvm-svn: 59475
|
| |
|
|
|
|
|
|
| |
alias for the current PreprocessorLexer. No functionality change. Performance
testing shows this results in no performance degradation when preprocessing
Cocoa.h.
llvm-svn: 59474
|
| |
|
|
|
|
|
|
|
| |
PreprocessorLexer, which will either be a 'Lexer' or 'PTHLexer'.
- Added stub field 'CurPTHLexer' to keep track of the current PTHLexer.
- Modified IncludeStackInfo to track both the current PTHLexer and
current PreprocessorLexer.
llvm-svn: 59472
|
| |
|
|
|
|
| |
increment value.
llvm-svn: 59471
|
| |
|
|
| |
llvm-svn: 59470
|
| |
|
|
|
|
|
|
|
| |
destructors, and conversion functions. The placeholders were used to
work around the fact that the parser and some of Sema really wanted
declarators to have simple identifiers; now, the code that deals with
declarators will use DeclarationNames.
llvm-svn: 59469
|
| |
|
|
|
|
|
|
| |
where the control reaches the end of a non-void function and also allows the
compiler to generate better code. When this assertion is false we can easily
add more else cases.
llvm-svn: 59468
|
| |
|
|
|
|
| |
Missing special lookup rule in Sema::ActOnInstanceMessage().
llvm-svn: 59467
|
| |
|
|
| |
llvm-svn: 59466
|
| |
|
|
|
|
| |
functions in these two schedulers.
llvm-svn: 59465
|
| |
|
|
|
|
|
| |
patch by Richard Osborne, tweaked and extended by your humble
servant.
llvm-svn: 59464
|
| |
|
|
| |
llvm-svn: 59463
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
C++ constructors, destructors, and conversion functions now have a
FETokenInfo field that IdentifierResolver can access, so that these
special names are handled just like ordinary identifiers. A few other
Sema routines now use DeclarationNames instead of IdentifierInfo*'s.
To validate this design, this code also implements parsing and
semantic analysis for id-expressions that name conversion functions,
e.g.,
return operator bool();
The new parser action ActOnConversionFunctionExpr takes the result of
parsing "operator type-id" and turning it into an expression, using
the IdentifierResolver with the DeclarationName of the conversion
function. ActOnDeclarator pushes those conversion function names into
scope so that the IdentifierResolver can find them, of course.
llvm-svn: 59462
|
| |
|
|
| |
llvm-svn: 59461
|
| |
|
|
|
|
|
| |
are trying to use the old GCC "casts as lvalue" extension. We don't and
will hopefully never support this.
llvm-svn: 59460
|
| |
|
|
|
|
| |
qualified id.
llvm-svn: 59459
|
| |
|
|
|
|
| |
a side-car datastructure
llvm-svn: 59458
|
| |
|
|
| |
llvm-svn: 59457
|
| |
|
|
|
|
| |
are not currently done (cf PowerPC/README.txt).
llvm-svn: 59456
|
| |
|
|
|
|
| |
optimizations) into this wishlist.
llvm-svn: 59455
|
| |
|
|
| |
llvm-svn: 59454
|
| |
|
|
| |
llvm-svn: 59451
|
| |
|
|
|
|
| |
for the target. This fixes PR3080.
llvm-svn: 59450
|
| |
|
|
| |
llvm-svn: 59449
|