From: Hans-Peter Nilsson <hp@bitrange.com>
To: Joern Rennecke <joern.rennecke@superh.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PATCH: reorg branch displacement fix
Date: Mon, 04 Nov 2002 17:40:00 -0000 [thread overview]
Message-ID: <Pine.BSF.4.44.0211042017170.53849-100000@dair.pair.com> (raw)
In-Reply-To: <3DC6FFC6.ED886282@superh.com>
On Mon, 4 Nov 2002, Joern Rennecke wrote:
> Looking in google for fr30, it appears as if Fujitsu doesn't care about
> gcc at the moment; they talk about their 'Softune' IDE, but no word about
> GNU tools. Also the fr30 gdb port has been obsoleted...
And the fr30 port has been broken since some time after
2002-05-29. Build succeeded then but all the tests timed out.
I haven't tried it since. Hmm... better do that, then...
> - The c4x and cris do not even have a length attribute.
For the record: as you may imagine, the CRIS port trusts GAS
relaxation to handle varying-length branches (9-bit and 16-bit
including sign). It's my informed opinion that this is not
worth doing in GCC (for this target) just for sake of branch
shortening since asm:s *must* in GCC be considered of inordinate
length; GCC can't do better here than GAS anyway. (Still worth
doing for sake of switch tables; on the virtual TODO list.
Thanks to GAS broken-.word [don't puke!], offsets aren't too
long, though.)
brgds, H-P
next prev parent reply other threads:[~2002-11-05 1:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-01 14:13 Joern Rennecke
2002-11-01 14:49 ` Jeff Law
2002-11-01 14:52 ` tm
2002-11-01 15:21 ` Joern Rennecke
2002-11-01 15:37 ` Jeff Law
2002-11-01 14:51 ` tm
2002-11-01 15:05 ` Jeff Law
2002-11-04 15:16 ` Joern Rennecke
2002-11-04 17:40 ` Hans-Peter Nilsson [this message]
2002-11-05 11:45 ` tm
2002-11-06 12:18 ` Joern Rennecke
-- strict thread matches above, loose matches on Subject: below --
2002-10-31 15:25 tm
2002-11-01 6:34 ` Jeff Law
2002-11-01 11:35 ` tm
2002-11-03 12:34 ` Jeff Law
2002-11-01 14:55 ` tm
2002-11-01 15:07 ` Jeff Law
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=Pine.BSF.4.44.0211042017170.53849-100000@dair.pair.com \
--to=hp@bitrange.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joern.rennecke@superh.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).