Remove a no-op break after a return, and correct one of the most

confusing indentations I've seen recently... Just noticed these while
making a change elsewhere.

No functionality changed.

llvm-svn: 134685
This commit is contained in:
Chandler Carruth 2011-07-08 04:59:44 +00:00
parent c5c3b0a25b
commit 904cb14225
1 changed files with 2 additions and 2 deletions

View File

@ -792,7 +792,7 @@ ExprResult Parser::ParseCastExpression(bool isUnaryExpression,
return ParseBuiltinPrimaryExpression();
case tok::kw___null:
return Actions.ActOnGNUNullExpr(ConsumeToken());
break;
case tok::plusplus: // unary-expression: '++' unary-expression [C99]
case tok::minusminus: { // unary-expression: '--' unary-expression [C99]
// C++ [expr.unary] has:
@ -1718,7 +1718,7 @@ ExprResult Parser::ParseBuiltinPrimaryExpression() {
ConsumeParen());
break;
}
}
}
if (Res.isInvalid())
return ExprError();