| Commit message (Collapse) | Author | Age | Files | Lines |
| ... | |
| |
|
|
| |
llvm-svn: 136971
|
| |
|
|
|
|
|
| |
The immediate portion of the operand is just a boolean (the 'U' bit indicating
add vs. subtract). Treat it as such.
llvm-svn: 136969
|
| |
|
|
| |
llvm-svn: 136968
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
arrays. This now suppresses the warning only in the case of
a one-element array as the last field in a struct where the array size
is a literal '1' rather than any macro expansion or template parameter.
This doesn't distinguish between the language standard in use to allow
code which dates from C89 era to compile without the warning even in C99
and C++ builds. We could add a separate warning (under a different flag)
with fixit hints to switch to a flexible array, but its not clear that
this would be desirable. Much of the code using this idiom is striving
for maximum portability.
Tests were also fleshed out a bit, and the diagnostic itself tweaked to
be more pretty w.r.t. single elment arrays. This is more ugly than
I would like due to APInt's not being supported by the diagnostic
rendering engine.
A pseudo-patch for this was proposed by Nicola Gigante, but I reworked
it both for several correctness issues and for code style.
Sorry this was so long in coming.
llvm-svn: 136965
|
| |
|
|
|
|
|
|
|
| |
1-element character arrays which are serving as flexible arrays. This is
the initial step, which is to restrict the 1-element array whitelist to
arrays that are member declarations. I'll refine it from here based on
the proposed patch.
llvm-svn: 136964
|
| |
|
|
| |
llvm-svn: 136963
|
| |
|
|
|
|
| |
<rdar://problem/9878189>
llvm-svn: 136962
|
| |
|
|
|
|
|
|
| |
~or~
Paint the bikeshed green.
llvm-svn: 136959
|
| |
|
|
|
|
|
| |
This patch takes some time because the old Python constructor pattern was not a valid one,
and breaks with SBTypeList's __init__ signature. Oops.
llvm-svn: 136958
|
| |
|
|
|
|
|
| |
- Added a test case in python-synth
Minor code improvements in categories, making them ready for adding new element types
llvm-svn: 136957
|
| |
|
|
| |
llvm-svn: 136956
|
| |
|
|
| |
llvm-svn: 136955
|
| |
|
|
|
|
| |
fixups to be added
llvm-svn: 136954
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
inlined variable, based on the discussion in PR10542.
This explodes the runtime of several passes down the pipeline due to
a large number of "copies" remaining live across a large function. This
only shows up with both debug and opt, but when it does it creates
a many-minute compile when self-hosting LLVM+Clang. There are several
other cases that show these types of regressions.
All of this is tracked in PR10542, and progress is being made on fixing
the issue. Once its addressed, the re-instated, but until then this
restores the performance for self-hosting and other opt+debug builds.
Devang, let me know if this causes any trouble, or impedes fixing it in
any way, and thanks for working on this!
llvm-svn: 136953
|
| |
|
|
|
|
| |
getAsPointeeMemoryRegion so that it could be reused.
llvm-svn: 136952
|
| |
|
|
| |
llvm-svn: 136951
|
| |
|
|
| |
llvm-svn: 136950
|
| |
|
|
|
|
| |
releasing the collection.
llvm-svn: 136949
|
| |
|
|
|
|
| |
functions when performing function overload resolution.
llvm-svn: 136948
|
| |
|
|
|
|
|
|
|
| |
empty constructor after the recent changes.
And remove expectedFailure decorator for test_SBTypeMember, which no longer exists after the recent changes, replace
it with test_SBTypeList.
llvm-svn: 136947
|
| |
|
|
|
|
| |
argument to bool. // rdar://9899834
llvm-svn: 136946
|
| |
|
|
|
|
| |
algorithm
llvm-svn: 136945
|
| |
|
|
| |
llvm-svn: 136944
|
| |
|
|
|
|
|
|
|
| |
when performing typo correction involving any overloaded template functions.
The added test cases, while currently demontrating sub-optimal behavior, will
not trigger any messages without the 1-line change to SemaExpr.cpp.
llvm-svn: 136943
|
| |
|
|
| |
llvm-svn: 136942
|
| |
|
|
|
|
| |
it can be controlled with a distinct flag.
llvm-svn: 136941
|
| |
|
|
|
|
|
| |
Enhance support for LDR instruction assembly parsing for post-indexed
addressing with immediate values. Add tests.
llvm-svn: 136940
|
| |
|
|
| |
llvm-svn: 136939
|
| |
|
|
|
|
| |
the bot.
llvm-svn: 136938
|
| |
|
|
| |
llvm-svn: 136937
|
| |
|
|
|
|
| |
instead of just the average.
llvm-svn: 136932
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(lldb's Driver::MainLoop()).
Sample run on my OSX Lion (MacBook Pro):
1: test_run_gdb_then_lldb (TestDisassembly.DisassembleDriverMainLoop)
Test disassembly on a large function with lldb vs. gdb. ...
gdb benchmark: Avg: 0.201802 (Laps: 5, Total Elapsed Time: 1.009008)
lldb benchmark: Avg: 0.109569 (Laps: 5, Total Elapsed Time: 0.547843)
lldb_avg/gdb_avg: 0.542952
ok
2: test_run_lldb_then_gdb (TestDisassembly.DisassembleDriverMainLoop)
Test disassembly on a large function with lldb vs. gdb. ...
lldb benchmark: Avg: 0.109580 (Laps: 5, Total Elapsed Time: 0.547902)
gdb benchmark: Avg: 0.201587 (Laps: 5, Total Elapsed Time: 1.007936)
lldb_avg/gdb_avg: 0.543588
ok
llvm-svn: 136931
|
| |
|
|
|
|
| |
exploring the transition on which a call to allocator function failed (to be able to find errors in examples like ErrorCodesFromDifferentAPISDoNotInterfere).
llvm-svn: 136930
|
| |
|
|
| |
llvm-svn: 136929
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
expressions that used function pointers. The problem
was that IRForTarget previously only scanned the IR
for the expression for call instructions; if a function
was used in another context, it was ignored.
Now LLDB scans the Module for functions that are only
declared (not also defined -- so these are externals);
it then constructs function pointers for these
functions and substitutes them wherever the function
is used.
Also made some changes so that "expr main" works just
as well as "expr &main"; they end up being the same
code, but LLDB was generating the result variable in
different ways.
llvm-svn: 136928
|
| |
|
|
|
|
|
|
| |
situation. When a class explicitly or implicitly (through inheritance)
"conformsTo" two protocols which conflict (have methods which conflict).
This is 2nd part of // rdar://6191214.
llvm-svn: 136927
|
| |
|
|
| |
llvm-svn: 136924
|
| |
|
|
|
|
| |
Patch by Ivan Krasin!
llvm-svn: 136921
|
| |
|
|
| |
llvm-svn: 136920
|
| |
|
|
| |
llvm-svn: 136919
|
| |
|
|
| |
llvm-svn: 136918
|
| |
|
|
| |
llvm-svn: 136917
|
| |
|
|
| |
llvm-svn: 136916
|
| |
|
|
| |
llvm-svn: 136915
|
| |
|
|
|
|
| |
cursor, from Connor Wakamo! Addresses <rdar://problem/9087798>.
llvm-svn: 136911
|
| |
|
|
|
|
| |
node) which should be appropriately mapped.
llvm-svn: 136910
|
| |
|
|
| |
llvm-svn: 136909
|
| |
|
|
| |
llvm-svn: 136908
|
| |
|
|
| |
llvm-svn: 136907
|
| |
|
|
|
|
|
|
| |
This is meant to be overriden by backends. Implement an override on PowerPC
which adjusts the offset by 2 for ha16/lo16 relocation kinds. This removes
a commented out hack and enables hello world to be compiled on PowerPC.
llvm-svn: 136905
|