public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "romikb at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/32680] unneeded movsbl
Date: Mon, 09 Jul 2007 05:44:00 -0000 [thread overview]
Message-ID: <20070709054427.5943.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32680-14818@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from romikb at mail dot ru 2007-07-09 05:44 -------
(In reply to comment #1)
>> eax register allready contains char
> not true
Can you explain, please, why it is not true?
Direct call of "function1" not produce "unneed movsb", so why indirect call
produce it?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32680
next prev parent reply other threads:[~2007-07-09 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 20:26 [Bug c/32680] New: " romikb at mail dot ru
2007-07-08 20:29 ` [Bug middle-end/32680] " pinskia at gcc dot gnu dot org
2007-07-09 5:44 ` romikb at mail dot ru [this message]
2007-07-09 9:50 ` rguenth at gcc dot gnu dot org
2007-07-09 9:54 ` [Bug middle-end/32680] fails to tailcall, useless stack adjustment rguenth 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=20070709054427.5943.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).