public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44074] Solaris 2.9 x86 Sun assembler doesn't like rep/lock prefixes on same line
Date: Wed, 19 May 2010 17:42:00 -0000 [thread overview]
Message-ID: <20100519174230.29319.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44074-16543@http.gcc.gnu.org/bugzilla/>
------- Comment #10 from ro at gcc dot gnu dot org 2010-05-19 17:42 -------
Subject: Bug 44074
Author: ro
Date: Wed May 19 17:42:00 2010
New Revision: 159591
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=159591
Log:
Backport from mainline:
2010-05-17 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
PR target/44074
* configure.ac (HAVE_AS_IX86_REP_LOCK_PREFIX): New test.
* configure: Regenerate.
* config.in: Regenerate.
* config/i386/i386.c (print_operand) <case ;>: Also print ; if
!HAVE_AS_IX86_REP_LOCK_PREFIX.
Don't emit whitespace.
* config/i386/i386.md (*rep_movdi_rex64): Use {%;} after rep.
(*rep_movsi): Likewise.
(*rep_movsi_rex64): Likewise.
(*rep_movqi): Likewise.
(*rep_movqi_rex64): Likewise.
(*rep_stosdi_rex64): Likewise.
(*rep_stossi): Likewise.
(*rep_stossi_rex64): Likewise.
(*rep_stosqi): Likewise.
(*rep_stosqi_rex64): Likewise.
(*cmpstrnqi_nz_1): Use {%;} after repz.
(*cmpstrnqi_nz_rex_1): Likewise.
(*cmpstrnqi_1): Likewise.
(*cmpstrnqi_rex_1): Likewise.
(*strlenqi_1): Use {%;} after repnz.
(*strlenqi_rex_1): Likewise.
* config/i386/sync.md (memory_barrier_nosse): Replace {%;| } by {%;} .
(*sync_compare_and_swap<mode>): Likewise.
(sync_double_compare_and_swap<mode>): Likewise.
(*sync_double_compare_and_swapdi_pic): Likewise.
(sync_old_add<mode>): Likewise.
(sync_add<mode>): Likewise.
(sync_sub<mode>): Likewise.
(sync_<code><mode>): Likewise.
Modified:
branches/gcc-4_4-branch/gcc/ChangeLog
branches/gcc-4_4-branch/gcc/config.in
branches/gcc-4_4-branch/gcc/config/i386/i386.c
branches/gcc-4_4-branch/gcc/config/i386/i386.md
branches/gcc-4_4-branch/gcc/config/i386/sync.md
branches/gcc-4_4-branch/gcc/configure
branches/gcc-4_4-branch/gcc/configure.ac
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44074
next prev parent reply other threads:[~2010-05-19 17:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 8:22 [Bug c/44074] New: " jay dot krell at cornell dot edu
2010-05-11 8:26 ` [Bug c/44074] " ubizjak at gmail dot com
2010-05-12 10:03 ` [Bug target/44074] " ro at gcc dot gnu dot org
2010-05-12 10:50 ` jay dot krell at cornell dot edu
2010-05-12 11:50 ` ro at CeBiTec dot Uni-Bielefeld dot DE
2010-05-12 12:02 ` jay dot krell at cornell dot edu
2010-05-13 7:56 ` jay dot krell at cornell dot edu
2010-05-17 18:29 ` ro at gcc dot gnu dot org
2010-05-17 20:30 ` ro at gcc dot gnu dot org
2010-05-19 17:33 ` ro at gcc dot gnu dot org
2010-05-19 17:42 ` ro at gcc dot gnu dot org [this message]
2010-05-19 17:44 ` ro at gcc dot gnu dot org
2010-05-20 10:29 ` jakub at gcc dot gnu dot org
2010-05-20 10:31 ` jakub at gcc dot gnu dot org
2010-05-20 10:33 ` ro at CeBiTec dot Uni-Bielefeld dot DE
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100519174230.29319.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).