From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: cgen@sources.redhat.com
Subject: branch insn question
Date: Sat, 09 Jan 2010 16:46:00 -0000 [thread overview]
Message-ID: <20100109164523.GA15551@doriath.ww600.siemens.net> (raw)
Hello,
I've a small problem with branch instructions on my platorm (m68hc08).
All branch instructions are only short-ranged (signed 8bit offset).
The recommended way to handle this is to emit jump-over code: instead of
beq _long_label
emit:
bne .Lshort
jmp _long_label
.Lshort:
My question is: should this be handled somehow by cgen? Or this should
be completely done via gas relaxation? And what attributes should I use
on branch instructions in .cpu file?
Thank you.
--
With best wishes
Dmitry
next reply other threads:[~2010-01-09 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 16:46 Dmitry Eremin-Solenikov [this message]
2010-01-11 7:53 ` Doug Evans
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=20100109164523.GA15551@doriath.ww600.siemens.net \
--to=dbaryshkov@gmail.com \
--cc=cgen@sources.redhat.com \
/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).