From: "Petar Bajic" <petar.bajic@micronasnit.com>
To: <gcc-help@gcc.gnu.org>
Subject: register usage
Date: Wed, 12 Jul 2006 08:58:00 -0000 [thread overview]
Message-ID: <003401c6a591$774b43a0$4900a8c0@niit.micronasnit.com> (raw)
In-Reply-To: <m3y7uznz6t.fsf@localhost.localdomain>
I want to forbid compiler to use condition register for destination in movz
instruction
instruction (if r3 == 0, move r2 to r1) should look like this:
movz r1, r2, r3 (r3 condition, r2 source, r1 destination register)
but compiler generates this
movz r3, r2, r3
and uses r3 further on. Wich is techincally ok, but I have this problem with
overwritting condition and would like to save it.
How do I tell compiler to generate different register for destination?
Petar
next prev parent reply other threads:[~2006-07-12 8:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-12 1:27 gcc binary format output Victor Roman Archidona
2006-07-12 4:39 ` Ian Lance Taylor
2006-07-12 5:35 ` Victor Roman Archidona
2006-07-12 5:57 ` Ian Lance Taylor
2006-07-12 8:58 ` Petar Bajic [this message]
2006-07-12 12:48 ` register usage Andrew Haley
2006-07-13 12:33 ` Petar Bajic
2006-07-13 12:45 ` Andrew Haley
2006-07-13 12:45 ` gcc binary format output Kai Ruottu
2006-07-13 12:50 ` Andrew Haley
2006-07-13 16:42 ` Kai Ruottu
2006-07-15 14:01 ` Victor Roman Archidona
2006-07-17 19:13 ` Kai Ruottu
2006-07-18 12:24 ` Kai Ruottu
2006-07-18 14:12 ` Victor Roman Archidona
2006-07-18 18:26 ` Mike Frysinger
2009-04-28 16:06 Register Usage John Farmer
2009-04-28 16:50 ` Ian Lance Taylor
2009-04-28 22:06 ` John Farmer
2009-04-29 0:27 ` Ian Lance Taylor
2009-04-29 7:57 ` John Farmer
2009-04-29 9:27 ` Richard Earnshaw
2009-04-29 10:18 ` John Farmer
2009-04-29 10:38 ` Richard Earnshaw
2009-04-29 12:14 ` John Farmer
2009-04-29 13:34 ` Richard Earnshaw
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='003401c6a591$774b43a0$4900a8c0@niit.micronasnit.com' \
--to=petar.bajic@micronasnit.com \
--cc=gcc-help@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).