- Jan 15, 2013
-
-
Richard Smith authored
with function definitions. We really should remove Parser::isDeclarationAfterDeclarator entirely, since it's meaningless in C++11 (an open brace could be either a function definition or an initializer, which is what it's trying to differentiate between). The other caller of it happens to be correct right now... llvm-svn: 172510
-
Douglas Gregor authored
llvm-svn: 172509
-
Michael J. Spencer authored
Marks a decl as constexpr if the compiler supports it. llvm-svn: 172508
-
Shankar Easwaran authored
llvm-svn: 172507
-
rdar://problem/13010909Greg Clayton authored
Don't accidentally sign extend unsigned bitfields. llvm-svn: 172506
-
Jim Ingham authored
llvm-svn: 172505
-
Richard Smith authored
attributes appertain to a declaration, even though they would be much more naturally modelled as appertaining to a function type. Previously, we would try to distribute them from the declarator to the function type, then reject them for being at an incorrect location. Now, we just distribute them as far as the declarator; the existing attribute handling code can actually apply them there just fine. llvm-svn: 172504
-
Jim Ingham authored
Separated the "expr --unwind-on-error" behavior into two parts, actual errors (i.e. crashes) which continue to be controlled by the --unwind-on-error flag, and --ignore-breakpoint which separately controls behavior when a called function hits a breakpoint. For breakpoints, we don't unwind, we either stop, or ignore the breakpoint, which makes more sense. Also make both these behaviors globally settable through "settings set". Also handle the case where a breakpoint command calls code that ends up re-hitting the breakpoint. We were recursing and crashing. Now we just stop without calling the second command. <rdar://problem/12986644> <rdar://problem/9119325> llvm-svn: 172503
-
Michael J. Spencer authored
This gives an overview of the driver and explains how to add options and driver flavors. llvm-svn: 172502
-
Michael J. Spencer authored
llvm-svn: 172501
-
Argyrios Kyrtzidis authored
previously it was calling the "StringMapImpl(unsigned itemSize)" constructor. llvm-svn: 172500
-
Nadav Rotem authored
llvm-svn: 172499
-
Daniel Dunbar authored
- Also, update the LangRef documentation on module flags to match the implementation. llvm-svn: 172498
-
Chad Rosier authored
warning options to setup diagnostic state, but should not be emitting warnings as these would be rudndant with what the frontend emits. rdar://13001556 llvm-svn: 172497
-
Jack Carter authored
we need to generate a N64 compound relocation R_MIPS_GPREL_32/R_MIPS_64/R_MIPS_NONE. The bug was exposed by the SingleSourcetest case DuffsDevice.c. Contributer: Jack Carter llvm-svn: 172496
-
Nick Kledzik authored
constants and string literals which the linker should coalesce. llvm-svn: 172495
-
Jason Molenda authored
document some simple bourne shell to re-generate these from the DNBDefs.h header file in case this needs to be done again in the future. llvm-svn: 172494
-
Enrico Granata authored
Adding a test case for expression parser's support for Unicode strings. This is an expected failure for now llvm-svn: 172493
-
rdar://problem/12790664Enrico Granata authored
Single-character Unicode data formatters llvm-svn: 172492
-
Eli Bendersky authored
simply use the getParser method from MCAsmParserExtension, working through the MCAsmParser interface. There's no longer a need to overload that method to cast it to the concrete AsmParser. llvm-svn: 172491
-
Eli Bendersky authored
This finally allows AsmParser to no longer list GenericAsmParser as a friend. All member vars directly accessed by GenericAsmParser have been properly encapsulated and exposed through the MCAsmParser interface. This reduces the coupling between AsmParser and GenericAsmParser. llvm-svn: 172490
-
Jakub Staszak authored
llvm-svn: 172489
-
- Jan 14, 2013
-
-
Shuxin Yang authored
--------------------------------------------------------------------------- C_A: reassociation is allowed C_R: reciprocal of a constant C is appropriate, which means - 1/C is exact, or - reciprocal is allowed and 1/C is neither a special value nor a denormal. ----------------------------------------------------------------------------- rule1: (X/C1) / C2 => X / (C2*C1) (if C_A) => X * (1/(C2*C1)) (if C_A && C_R) rule 2: X*C1 / C2 => X * (C1/C2) if C_A rule 3: (X/Y)/Z = > X/(Y*Z) (if C_A && at least one of Y and Z is symbolic value) rule 4: Z/(X/Y) = > (Z*Y)/X (similar to rule3) rule 5: C1/(X*C2) => (C1/C2) / X (if C_A) rule 6: C1/(X/C2) => (C1*C2) / X (if C_A) rule 7: C1/(C2/X) => (C1/C2) * X (if C_A) llvm-svn: 172488
-
Dmitri Gribenko authored
[[gnu::...]] syntax Pointed out by Richard Smith on the mailing list. llvm-svn: 172487
-
Tobias Grosser authored
llvm-svn: 172486
-
Richard Smith authored
ActOnFinishFullExpr that some of its checks only apply to discarded-value expressions. This adds missing checks for unexpanded variadic template parameter packs to a handful of constructs. llvm-svn: 172485
-
Chad Rosier authored
have an arbitrary ordering of the base register, index register and displacement. rdar://12527141 llvm-svn: 172484
-
Dmitri Gribenko authored
llvm-svn: 172483
-
Nick Kledzik authored
llvm-svn: 172482
-
Dmitri Gribenko authored
llvm-svn: 172481
-
Bill Schmidt authored
The included test case is derived from one of the GCC compatibility tests. The problem arises after the selection DAG has been converted to type-legalized form. The combiner first sees a 64-bit load that can be converted into a pre-increment form. The original load feeds into a SRL that isolates the upper 32 bits of the loaded doubleword. This looks like an opportunity for DAGCombiner::ReduceLoadWidth() to replace the 64-bit load with a 32-bit load. However, this transformation is not valid, as the replacement load is not a pre-increment load. The pre-increment load produces an extra result, which feeds a subsequent add instruction. The replacement load only has one result value, and this value is propagated to all uses of the pre- increment load, including the add. Because the add is looking for the second result value as its operand, it ends up attempting to add a constant to a token chain, resulting in a crash. So the patch simply disables this transformation for any load with more than two result values. llvm-svn: 172480
-
Sean Callanan authored
JIT it again. llvm-svn: 172477
-
Michael Gottesman authored
We lower these into 2x chained usub.with.overflow intrinsics. llvm-svn: 172476
-
Quentin Colombet authored
Refactor the big if/else sequence into one string switch for ARM subtype selection. llvm-svn: 172475
-
Dmitri Gribenko authored
llvm-svn: 172474
-
Quentin Colombet authored
Complete the existing support of ARM v6m, v7m, and v7em, i.e., respectively cortex-m0, cortex-m3, and cortex-m4 on the backend side. Adds new subtype values for the MachO format and use them when the related triple are set. llvm-svn: 172472
-
David Greene authored
Fix a casting-away-const compiler warning. llvm-svn: 172471
-
David Greene authored
Do proper casting to eliminate a const-away-cast compiler warning. llvm-svn: 172470
-
David Greene authored
Properly cast some more code that triggered cast-away-const errors. llvm-svn: 172469
-
David Greene authored
Properly cast code to eliminate cast-away-const errors. llvm-svn: 172468
-