From: Paul Brook <paul@codesourcery.com>
To: gcc@gcc.gnu.org
Cc: Denis Zaitsev <zzz@anda.ru>, Michael Matz <matz@suse.de>,
linux-gcc@vger.kernel.org
Subject: Re: [new-ra] GCC-3.3.2/x86: some suspicious behaviour
Date: Thu, 8 Jul 2004 17:52:57 +0100 [thread overview]
Message-ID: <200407081752.57212.paul@codesourcery.com> (raw)
In-Reply-To: <20040708223119.A7162@natasha.ward.six>
On Thursday 08 July 2004 17:31, Denis Zaitsev wrote:
> On Thu, Jul 08, 2004 at 04:46:33PM +0200, Michael Matz wrote:
> > Hi,
> >
> > On Thu, 8 Jul 2004, Denis Zaitsev wrote:
> > > So, what does these two commands mean:
> > >
> > >
> > > movl %ecx, 16(%esp)
> > > movl %esi, 20(%esp)
> >
> > It means that the compiler wasn't able to optimize them away. They do no
> > harm. FWIW gcc 3.4 or the new-regalloc-branch don't have this problem.
>
> They don't harm. But to optimize _what_? So, what is the initial
> meaning of these assignments? And why they appear only for the double
> asm statement?
They're storing the modified values of s and d back into their stack slots
after the first asm. The compiler wasn't able to determine that these were
dead stores.
Remove the "extern inline" and compile with -O0. This will show you
approximately what the code looks like before optimization.
Paul
next prev parent reply other threads:[~2004-07-08 16:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-07 22:06 [new-ra] GCC-3.3.2/x86: some suspicious behaviour Denis Zaitsev
2004-07-08 14:46 ` Michael Matz
2004-07-08 16:31 ` Denis Zaitsev
2004-07-08 16:52 ` Paul Brook [this message]
2004-07-08 17:18 ` Denis Zaitsev
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=200407081752.57212.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=linux-gcc@vger.kernel.org \
--cc=matz@suse.de \
--cc=zzz@anda.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.