[Bug target/57017] «Error: expecting string instruction after `rep'» in code w/o inline assembly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 Jakub Jelinek jakub at gcc dot gnu.org changed: What|Removed |Added Status|WAITING |RESOLVED CC||jakub at gcc dot gnu.org Resolution||INVALID --- Comment #9 from Jakub Jelinek jakub at gcc dot gnu.org 2013-04-25 07:27:18 UTC --- Not a bug in gcc then.
[Bug target/57017] «Error: expecting string instruction after `rep'» in code w/o inline assembly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Target||x86_64-slackware-linux --- Comment #5 from Andrew Pinski pinskia at gcc dot gnu.org 2013-04-24 06:09:02 UTC --- What binutils version are you using? You can find out by doing as --version. I think this is a bug in the version of binutils you are using the generated assembly is: rep; ret which is a valid assembly for x86_64.
[Bug target/57017] «Error: expecting string instruction after `rep'» in code w/o inline assembly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 --- Comment #6 from Jakub Jelinek jakub at gcc dot gnu.org 2013-04-24 06:15:46 UTC --- Can't reproduce, perhaps misconfigured compiler? HAVE_AS_IX86_REP_LOCK_PREFIX test in particular. You haven't said what target it is and how you've configured the compiler...
[Bug target/57017] «Error: expecting string instruction after `rep'» in code w/o inline assembly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 Alan Aversa aaversa at optics dot arizona.edu changed: What|Removed |Added CC||aaversa at optics dot ||arizona.edu --- Comment #7 from Alan Aversa aaversa at optics dot arizona.edu 2013-04-24 06:22:54 UTC --- (In reply to comment #5) What binutils version are you using? You can find out by doing as --version. I think this is a bug in the version of binutils you are using the generated assembly is: rep; ret which is a valid assembly for x86_64. GNU assembler (Linux/GNU Binutils) 2.22.52.0.2.20120424 (In reply to comment #6) Can't reproduce, perhaps misconfigured compiler? HAVE_AS_IX86_REP_LOCK_PREFIX test in particular. You haven't said what target it is and how you've configured the compiler... ../gcc-4.8.0/configure --prefix=/usr --libdir=/usr/lib64 --mandir=/usr/man --infodir=/usr/info --enable-shared --enable-bootstrap --enable-languages=ada,c,c++,fortran,go,java,lto,objc --enable-threads=posix --enable-checking=release --enable-objc-gc --with-system-zlib --with-python-dir=/lib64/python2.7/site-packages --disable-libunwind-exceptions --enable-__cxa_atexit --enable-libssp --enable-lto --with-gnu-ld --verbose --enable-java-home --with-java-home=/usr/lib64/jvm/jre --with-jvm-root-dir=/usr/lib64/jvm --with-jvm-jar-dir=/usr/lib64/jvm/jvm-exports --with-arch-directory=amd64 --with-antlr-jar=/home/slackware/slackbuilds/gcc/antlr-runtime-3.4.jar --enable-multilib --target=x86_64-slackware-linux --build=x86_64-slackware-linux --host=x86_64-slackware-linux
[Bug target/57017] «Error: expecting string instruction after `rep'» in code w/o inline assembly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 --- Comment #8 from Alan Aversa aaversa at optics dot arizona.edu 2013-04-25 02:53:02 UTC --- I upgraded to binutils 2.23.52.0.1 and the problem went away.
[Bug target/57017] «Error: expecting string instruction after `rep'» in code w/o inline assembly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 --- Comment #4 from Alan Aversa aaversa at optics dot arizona.edu 2013-04-24 05:58:29 UTC --- Created attachment 29925 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=29925 the REAL preprocessed source file sorry, I uploaded the wrong file; this is the preprocessed source file
[Bug target/57017] «Error: expecting string instruction after `rep'» in code w/o inline assembly
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57017 Andrew Pinski pinskia at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Last reconfirmed||2013-04-21 Component|bootstrap |target Ever Confirmed|0 |1 --- Comment #3 from Andrew Pinski pinskia at gcc dot gnu.org 2013-04-21 03:59:55 UTC --- (In reply to comment #2) Created attachment 29907 [details] the preprocessed C source file This cannot be the preprocessed source as it still includes #include in it.