aboutsummaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorJim Stichnoth <stichnot@chromium.org>2013-09-16 12:26:09 -0700
committerJim Stichnoth <stichnot@chromium.org>2013-09-16 12:26:09 -0700
commit591359fae065fb5f86ba957a550503daef727536 (patch)
tree8881027a692cea07997f733b736a8ece34054361 /include
parent1d241cef755d5a129d3f17117c559a70ecaa0e0c (diff)
Work around a gcc 4.6.3 / 4.7 bug.
GCC bug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58416 causes the bf64-1.c test to fail in the GCC torture test suite. This provides an upstreamable workaround. Inspection of the LLVM code base showed no other instances of the pattern that triggers the gcc bug. This can also be upstreamed as soon as I can get a working x86-32 upstream build working to verify/test against. In the meantime, we can make one pnacl-fyi bot go green again. BUG= https://code.google.com/p/nativeclient/issues/detail?id=3685 R=jfb@chromium.org, jfb@google.com Review URL: https://codereview.chromium.org/23437037
Diffstat (limited to 'include')
-rw-r--r--include/llvm/MC/MCInst.h6
1 files changed, 5 insertions, 1 deletions
diff --git a/include/llvm/MC/MCInst.h b/include/llvm/MC/MCInst.h
index 4766815da5..0b657bd146 100644
--- a/include/llvm/MC/MCInst.h
+++ b/include/llvm/MC/MCInst.h
@@ -50,7 +50,11 @@ class MCOperand {
};
public:
- MCOperand() : Kind(kInvalid), FPImmVal(0.0) {}
+ // @LOCALMOD-START
+ // Initialize ImmVal instead of FPImmVal, thanks to
+ // http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58416
+ MCOperand() : Kind(kInvalid), ImmVal(0) {}
+ // @LOCALMOD-END
bool isValid() const { return Kind != kInvalid; }
bool isReg() const { return Kind == kRegister; }