All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Lohoff <flo@rfc822.org>
To: Ralf Baechle <ralf@oss.sgi.com>
Cc: Jun Sun <jsun@mvista.com>, linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: The initial results (Re: stable binutils, gcc, glibc ...
Date: Wed, 18 Oct 2000 14:30:03 +0200	[thread overview]
Message-ID: <20001018143003.C2354@paradigm.rfc822.org> (raw)
In-Reply-To: <20001018035719.F7865@bacchus.dhis.org>; from ralf@oss.sgi.com on Wed, Oct 18, 2000 at 03:57:19AM +0200

On Wed, Oct 18, 2000 at 03:57:19AM +0200, Ralf Baechle wrote:
> 
> loop:
> 	[...]
> 	beq	r1, r2, loop
> 
> should be turned into:
> 
> loop:
> 	[...]
> 	bnez	r1, r2, 1f
> 	j	loop
> 1:
> 
> but of course only if the branch destination is outside the 16-bit range.
> Thanks to the ever increasing code size there are now several realworld
> examples which run into this problem.  Volunteers?

By thinking about this without any knowledge of the binutils code generation.

How does this work if loop is only an external symbol ? The distance
will than be relevant when linking but then the code will already be there
and one would need to insert an instruction.

Flo
-- 
Florian Lohoff		flo@rfc822.org		      	+49-5201-669912
      "Write only memory - Oops. Time for my medication again ..."

  reply	other threads:[~2000-10-18 12:46 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-10-14  5:13 stable binutils, gcc, glibc Jun Sun
2000-10-14  3:55 ` Ralf Baechle
2000-10-14  4:21   ` Ralf Baechle
2000-10-14 10:57   ` Florian Lohoff
2000-10-14 14:51   ` Jay Carlson
2000-10-14 14:51     ` Jay Carlson
2000-10-14 15:09     ` Ralf Baechle
2000-10-14 16:11       ` Jay Carlson
2000-10-14 16:11         ` Jay Carlson
2000-10-14 16:29         ` Bradley D. LaRonde
2000-10-14 16:29           ` Bradley D. LaRonde
2000-10-16  0:35           ` Ralf Baechle
2000-10-16  1:33             ` Mike Klar
2000-10-16  1:33               ` Mike Klar
2000-10-16 11:26               ` Jay Carlson
2000-10-16 11:26                 ` Jay Carlson
2000-10-16 11:30                 ` Ralf Baechle
2000-10-16 12:00                 ` Ralf Baechle
2000-10-18  1:59                   ` Jay Carlson
2000-10-18  1:59                     ` Jay Carlson
2000-10-18 20:31                     ` Ralf Baechle
2000-10-14 16:11       ` Jay Carlson
2000-10-14 16:11         ` Jay Carlson
2000-10-14 16:12         ` Ralf Baechle
2000-10-14 16:22           ` Bradley D. LaRonde
2000-10-14 16:22             ` Bradley D. LaRonde
2000-10-14 23:47           ` Keith Owens
2000-10-16  1:07             ` Ralf Baechle
2000-10-16  7:00               ` Alan Cox
2000-10-16  7:00                 ` Alan Cox
2000-10-14 10:55 ` Florian Lohoff
2000-10-14 12:41   ` Ralf Baechle
     [not found]   ` <Pine.LNX.4.21.0010140730280.17430-100000@spawn.hockeyfiend.com>
2000-10-14 14:25     ` Ralf Baechle
2000-10-14 17:54       ` Florian Lohoff
2000-10-16 15:41 ` Maciej W. Rozycki
2000-10-18  4:04 ` The initial results (Re: " Jun Sun
2000-10-18  1:33   ` Florian Lohoff
2000-10-18  9:20     ` Jun Sun
2000-10-18  2:25       ` nick
2000-10-18  9:18       ` Florian Lohoff
2000-10-18 12:27         ` Ralf Baechle
2000-10-18  1:57   ` Ralf Baechle
2000-10-18 12:30     ` Florian Lohoff [this message]
2000-10-18 22:37       ` Ralf Baechle
2000-10-18 11:42   ` Geert Uytterhoeven
2000-10-18 17:15     ` Jun Sun
2000-10-20 14:55       ` Geert Uytterhoeven
2000-11-06 11:43   ` Jay Carlson
2000-11-06 11:43     ` Jay Carlson
2000-10-20 11:09 ` Andreas Jaeger
2000-10-20 12:03   ` Jay Carlson
2000-10-20 12:03     ` Jay Carlson
2000-10-21  1:24     ` Ralf Baechle

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=20001018143003.C2354@paradigm.rfc822.org \
    --to=flo@rfc822.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@fnet.fr \
    --cc=linux-mips@oss.sgi.com \
    --cc=ralf@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.