The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cdl@mpl.ucsd.edu (Carl Lowenstein)
Subject: [pups] 2.11BSD "make unix" aborts Error 141
Date: Wed, 19 Mar 2003 10:58:37 -0800 (PST)	[thread overview]
Message-ID: <200303191858.h2JIwb726378@opihi.ucsd.edu> (raw)

> From: "Steven M. Schultz" <sms at 2BSD.COM>
> To: pups at minnie.tuhs.org
> Subject: Re: [pups] 2.11BSD "make unix" aborts Error 141
> List-Archive: <http://minnie.tuhs.org/pipermail/pups/>
> Date: Wed, 19 Mar 2003 09:46:51 -0800 (PST)
> 
> Hi -
> 
> > From: David Evans <dfevans at bbcr.uwaterloo.ca>
> >   Ugh.
> > 
> >   Am I naive to suggest a rewrite of as?  :)
> 
> 	Just a little bit <g>
> 
> 	It's a thought that used to occur to me fairly often a long time 
> 	ago.  I cured myself of it though after I did the rewrite into
> 	its current form (if you think it's bad now you should have seen it
> 	before ;)).
> 
> 	The biggest problem are the SDI (Span Dependent Instructions).  The
> 	PDP-11 has 'jmp' (non conditional but no range limit) and 'br' (many
> 	flavors of conditional branches but with a +/- 128 byte range).  
> 	The compiler generates pseudo instructions like 'jeq' and leaves it
> 	up to the assembler to figure out if a branch will reach or if a
> 	branch around a jump is needed.   That's a PITA to handle and is
> 	I believe the cause of much ugliness in the assembler.

That, of course, is a _neat feature_ of AS.  On the other hand, how
much code bloat would result if AS always emitted (bne;jmp) pairs for
'jeq', etc.  Maybe only generate (bne;jmp) for forward 'jeq' where the
span is not yet known.  I am sure there are pathological instabilities
in this kind of code generation, where expanding one branch/jump
instruction makes another one go out of span range.

Answer:  3:1 for each unnecessary pair.  But I have no idea of the
statistics for real code.

    carl
-- 
    carl lowenstein         marine physical lab     u.c. san diego
                                                 clowenst at ucsd.edu



             reply	other threads:[~2003-03-19 18:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-19 18:58 Carl Lowenstein [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-19 17:59 Steven M. Schultz
2003-03-19 21:26 ` Warren Toomey
2003-03-19 17:46 Steven M. Schultz
2003-03-19 16:52 Norman Wilson
2003-03-19 16:29 Steven M. Schultz
2003-03-19 16:38 ` David Evans
2003-03-17 16:38 [pups] 2BSD build problem - unix.o not too big Steven M. Schultz
2003-03-19  2:24 ` [pups] 2.11BSD "make unix" aborts Error 141 Jonathan Engdahl

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=200303191858.h2JIwb726378@opihi.ucsd.edu \
    --to=cdl@mpl.ucsd.edu \
    /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 NNTP newsgroup(s).