[Interest] Odd assembler error on pure Qt project with GCC 4.8.2

[Bob Hood]

I'm building the Qt Service v2.7 project under CentOS 6.6 using GCC 4.8.2:

[bob at centos64 qtservice_64_dll]$ gcc --version
gcc (GCC) 4.8.2 20140120 (Red Hat 4.8.2-15)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

I'm not setting any special options, just running qmake in the src/ folder and 
then launching "make -f Makefile.Release". However, I'm getting an error 
message that I don't get under Windows or OS X that appears to have to do with 
the Assembler output being compiled:

...
g++ -c -m64 -pipe -O2 -D_REENTRANT -Wall -W -fPIC -DNDEBUG -DQT_NO_DEBUG 
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED 
-I/usr/local/qt/4.8.6/64_dll/mkspecs/linux-g++-64 -I. 
-I/usr/local/qt/4.8.6/64_dll/include/QtCore 
-I/usr/local/qt/4.8.6/64_dll/include/QtNetwork 
-I/usr/local/qt/4.8.6/64_dll/include/QtGui 
-I/usr/local/qt/4.8.6/64_dll/include -I. -Irelease -o release/qtservice.o 
qtservice.cpp
{standard input}: Assembler messages:
{standard input}:14: Error: expecting string instruction after `rep'
{standard input}:30: Error: expecting string instruction after `rep'
{standard input}:41: Error: expecting string instruction after `rep'
{standard input}:52: Error: expecting string instruction after `rep'
{standard input}:63: Error: expecting string instruction after `rep'
{standard input}:333: Error: expecting string instruction after `rep'
{standard input}:362: Error: expecting string instruction after `rep'
{standard input}:471: Error: expecting string instruction after `rep'
{standard input}:608: Error: expecting string instruction after `rep'
{standard input}:954: Error: expecting string instruction after `rep'
{standard input}:5569: Error: expecting string instruction after `rep'
make: *** [release/qtservice.o] Error 1
Failed to build Qt 4.8.6 release

I'm guessing this is a bug/incompatibility with this version of GCC's 
toolchain.  If that's the case, are there any command-line tricks I might be 
able to use to work around it?  I need this version of GCC for C++11 support, 
and I don't think I can currently get a newer version under this RHE 
release.(...and we are using this RHE release because it is the one our 
customers use, so we must therefore support it.)

Thanks, guys.