summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDan Gohman <gohman@apple.com>2009-03-23 05:02:44 +0000
committerDan Gohman <gohman@apple.com>2009-03-23 05:02:44 +0000
commit772de0ae2d5364db9ea005a86aead0b50dabd83d (patch)
treed81084cf3ef898e62cc32b6cef81586223b471cf
parent449fe54cff70ea9ad42130e43d1b45eb57323262 (diff)
downloadbcm5719-llvm-772de0ae2d5364db9ea005a86aead0b50dabd83d.tar.gz
bcm5719-llvm-772de0ae2d5364db9ea005a86aead0b50dabd83d.zip
Fix a grammaro in a comment that Bill noticed.
llvm-svn: 67507
-rw-r--r--llvm/lib/Target/X86/X86CallingConv.td2
1 files changed, 1 insertions, 1 deletions
diff --git a/llvm/lib/Target/X86/X86CallingConv.td b/llvm/lib/Target/X86/X86CallingConv.td
index 370bae7a50c..6924520ab8f 100644
--- a/llvm/lib/Target/X86/X86CallingConv.td
+++ b/llvm/lib/Target/X86/X86CallingConv.td
@@ -24,7 +24,7 @@ class CCIfSubtarget<string F, CCAction A>
def RetCC_X86Common : CallingConv<[
// Scalar values are returned in AX first, then DX, except for i8 where
// the convention is to return values in AL and AH. However, using AL and
- // is AH problematic -- a return of {i16,i8} would end up using AX and AH,
+ // AH is problematic -- a return of {i16,i8} would end up using AX and AH,
// and one value would clobber the other. C front-ends are currently expected
// to pack two i8 values into an i16 in the rare situations where this
// is necessary.
OpenPOWER on IntegriCloud