public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "casmyu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/39403] Excessive optimization issue
Date: Tue, 10 Mar 2009 01:23:00 -0000 [thread overview]
Message-ID: <20090310012302.23368.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39403-17407@http.gcc.gnu.org/bugzilla/>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2771 bytes --]
------- Comment #3 from casmyu at gmail dot com 2009-03-10 01:23 -------
Hi:
I have changed the code as you said, but it is more error now.
1 #include <stdio.h>
2
3 int main()
4 {
5 char src[30] = {"This is a test message.\n"};
6 char dst[30];
7 int len = 25;
8
9 __asm__ __volatile__(
10 "cld\n\t"
11 "rep movsb"
12 :
13 // : "(src), "D"(dst), "c"(len)
14 : "+c"(len), "+D"(dst), "+S"(src)
15 );
16 printf("%s\t%d\n", dst, len);
17 return 0;
18 }
[root][~]# gcc -O2 -o bugtest bugtest.c
bugtest.c: In function ¡®main¡¯:
bugtest.c:15: error: input operand constraint contains ¡®+¡¯
bugtest.c:15: error: input operand constraint contains ¡®+¡¯
bugtest.c:15: error: input operand constraint contains ¡®+¡¯
bugtest.c:9: error: input operand constraint contains ¡®+¡¯
bugtest.c:9: error: input operand constraint contains ¡®+¡¯
bugtest.c:9: error: input operand constraint contains ¡®+¡¯
Please help to re-check this issue.
Thank you!
(In reply to comment #2)
> Subject: Re: Excessive optimization issue
>
>
>
> Sent from my iPhone
>
> On Mar 9, 2009, at 8:36 AM, "rguenth at gcc dot gnu dot org"
> <gcc-bugzilla@gcc.gnu.org
> > wrote:
>
> >
> >
> > ------- Comment #1 from rguenth at gcc dot gnu dot org 2009-03-09
> > 15:36 -------
> > You need to specify that the registers are clobbered by the asm.
> > The only
> > way to do that is to use output constraints ("+D", "+c", etc.) on
> > proper
> > temporaries.
> >
> > int lent = len;
> > char *dstt = dst;
> > char *srct = src;
> > __asm__ __volatile__(
> > "cld\n\t"
> > "rep movsb"
> > : "+c" (lent), "+D"(dstt), "+S"(src)
> > );
> > Otherwise GCC thinks the registers still hold the original value.
>
> Oh and mark this inline-ask as clobbering memory.
>
> >
> >
> >
> > --
> >
> > rguenth at gcc dot gnu dot org changed:
> >
> > What |Removed |Added
> > ---
> > ---
> > ----------------------------------------------------------------------
> > Status|UNCONFIRMED |RESOLVED
> > Resolution| |INVALID
> >
> >
> > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39403
> >
>
--
casmyu at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |casmyu at gmail dot com
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39403
next prev parent reply other threads:[~2009-03-10 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 4:06 [Bug c/39403] New: " casmyu at gmail dot com
2009-03-09 15:36 ` [Bug c/39403] " rguenth at gcc dot gnu dot org
2009-03-09 15:57 ` Andrew Thomas Pinski
2009-03-09 15:57 ` pinskia at gmail dot com
2009-03-10 1:23 ` casmyu at gmail dot com [this message]
2009-04-16 20:32 ` [Bug target/39403] " pinskia at gcc dot gnu dot org
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=20090310012302.23368.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).