The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Hellwig.Geisse@mni.fh-giessen.de (Hellwig Geisse)
Subject: [Unix-jun72] Minor errors
Date: Fri, 02 May 2008 18:57:22 +0200	[thread overview]
Message-ID: <1209747442.5140.1012.camel@papa> (raw)

I just did a 'grep' of some suspicious
character combinations and found the following:

e00-04:/ initialize i-nodes r1.,...,47. and wr1te the root device,
binary, etc.,
e04-01:       bne     3f /Is1t zero now?
e08-05:       bis     $103,r3 / now rbn,for,un1t,1e
e04-03:1: / flle just opened
e05-04: cmp     r1, ii / r1 = i-number of current flle
e03-01:       jsr     r0,rswap / read new process 1nto core
e04-04:       cmp     r1,$12 / is char a l1ne feed
e06-02:         br ret / it 1n r1; 1f there 1s no problem with reader,
it
e06-02: inc     *u.fofp / increment file offset to point to 'next' char
1n
e08-03:       br      1f / branch if block already 1n a I/O buffer
e08-03:       bis     $2000,(r5) / set read mu (bu: 100 1n 1/0 buffer)
e08-06:       bit    $173000,(r5) / lock+keep+active+outstand1ng
e11-07: cmp     0b,$1nbuf+256. / have we exceeded innut buffer size
e06-04: inc     *u.fofp / increment f11e offset to point to next
available
e06-05:  mov    r2,i.size / yes, increase the f11e size to file offset +
e06-06:                    / be written to the f11e
e08-03:tstdeve: / check whether permanent error has occured on special
f11e
e03-02:                        / to end of stack gets written out) ~
e08-03:       mov     u.base,r2 / put users base in r2 ~
e11-01: cdpb    B(r5),$'- / was this sh calleZd by init or loginx~
e03-02:       cmp     r2,$core / is u.break less than Score

As you can see, the errors are almost exclusively in
the comments. Someone with write access to the svn
repository could perhaps take care of that.

Hellwig




             reply	other threads:[~2008-05-02 16:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 16:57 Hellwig Geisse [this message]
2008-05-02 17:56 ` Brad Parker
2008-05-02 18:16   ` Brad Parker

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=1209747442.5140.1012.camel@papa \
    --to=hellwig.geisse@mni.fh-giessen.de \
    /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).