From b9b28eefa77f1618cb3f20e8d4b73dd3a640a8ac Mon Sep 17 00:00:00 2001
From: John Maddock <john@johnmaddock.co.uk>
Date: Sat, 24 Nov 2012 18:28:04 +0000
Subject: [PATCH] Fix for gcc-4.4.x: rvalue reference support in gcc-4.4 isn't
 good enough for our use cases.

[SVN r81510]
---
 include/boost/multiprecision/detail/no_et_ops.hpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/boost/multiprecision/detail/no_et_ops.hpp b/include/boost/multiprecision/detail/no_et_ops.hpp
index 1ee492db..b967da2a 100644
--- a/include/boost/multiprecision/detail/no_et_ops.hpp
+++ b/include/boost/multiprecision/detail/no_et_ops.hpp
@@ -285,7 +285,7 @@ BOOST_FORCEINLINE typename enable_if<is_integral<I>, number<B, et_off> >::type
    return BOOST_MP_MOVE(result);
 }
 
-#ifndef BOOST_NO_CXX11_RVALUE_REFERENCES
+#if !defined(BOOST_NO_CXX11_RVALUE_REFERENCES) && !(defined(__GNUC__) && ((__GNUC__ == 4) && (__GNUC_MINOR__ < 5)))
 //
 // If we have rvalue references go all over again with rvalue ref overloads and move semantics.
 // Note that while it would be tempting to implement these so they return an rvalue reference