public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/35926] Pushing / Poping ebx without using it.
Date: Mon, 14 Apr 2008 11:13:00 -0000 [thread overview]
Message-ID: <20080414111300.6113.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35926-8951@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from ubizjak at gmail dot com 2008-04-14 11:12 -------
(In reply to comment #2)
> This is setting up the frame pointer which is needed for unwinding/debugging
> on some targets. You can use -fomit-frame-pointer to avoid this.
No, -fomit-frame-pointer uses %ebp.
%ebx is marked as used due to long long value in %ecx/%ebx. For some reason,
%ebx is still marked as live when function prologue and epilogue are
constructed.
--
ubizjak at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35926
next prev parent reply other threads:[~2008-04-14 11:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 17:49 [Bug c/35926] New: " ppelissi at caramail dot com
2008-04-13 17:50 ` [Bug c/35926] " ppelissi at caramail dot com
2008-04-14 9:19 ` [Bug target/35926] " rguenth at gcc dot gnu dot org
2008-04-14 11:13 ` ubizjak at gmail dot com [this message]
2008-12-28 7:00 ` pinskia at gcc dot gnu dot org
[not found] <bug-35926-4@http.gcc.gnu.org/bugzilla/>
2011-01-25 19:51 ` tony.poppleton at gmail dot com
2011-01-27 17:11 ` tony.poppleton at gmail dot com
2011-02-01 13:44 ` tony.poppleton at gmail dot com
2013-04-10 1:42 ` tony.poppleton at gmail dot com
2021-12-25 7:07 ` pinskia at gcc dot gnu.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=20080414111300.6113.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).