public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: alan@lxorguk.ukuu.org.uk, meissner@spectacle-pond.org (Michael Meissner)
Cc: vonbrand@sleipnir.valparaiso.cl (Horst von Brand),
	mharris@opensourceadvocate.org (Mike A. Harris),
	Wayne.Brown@altec.com, hacksaw@hacksaw.org (Hacksaw),
	linux-kernel@vger.kernel.org (Linux Kernel mailing list)
Subject: Re: Not a typewriter
Date: Mon, 14 May 2001 12:29:56 -0500 (CDT)	[thread overview]
Message-ID: <200105141729.MAA28295@tomcat.admin.navo.hpc.mil> (raw)
In-Reply-To: <E14zLj4-0000zO-00@the-village.bc.nu>

---------  Received message begins Here  ---------

> 
> > IIRC, the 6 character linker requirement came from when the Bell Labs folk
> > ported the C compiler the IBM mainframe world, not from the early UNIX (tm)
> > world.  During the original ANSI C meetings, I got the sense from the IBM rep,
> 
> 6 character linker name limits are very old. Honeywell L66 GCOS3/TSS which I
> had the dubious pleasure of experiencing and which is a direct derivative of
> GECOS and thus relevant to the era like many 36bit boxes uses 6 char link names
> 
> Why - well because 6 BCD characters fit in a 36bit word and its a single compare
> to check symbol matches

well... actually it was 6 bit "ascii" computed from: (char - ' '). Depends
entirely on architecture, and implementation. EBCD/6Bit/7Bit and EBCDIC were
supported on the Honeywell systems.

-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

  parent reply	other threads:[~2001-05-14 17:30 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 16:07 Not a typewriter Wayne.Brown
2001-05-11 17:03 ` Joel Jaeggli
2001-05-11 21:43 ` Hacksaw
2001-05-13 23:39   ` Mike A. Harris
2001-05-12  4:18 ` John Alvord
2001-05-13 23:35 ` Mike A. Harris
2001-05-14  1:03   ` Horst von Brand
2001-05-14 14:31     ` John Kodis
2001-05-14 15:33       ` Not a typewriterg Michael Meissner
2001-05-14 15:25     ` Not a typewriter Michael Meissner
2001-05-14 17:01       ` Alan Cox
2001-05-14 17:16         ` Michael Meissner
2001-05-14 17:29         ` Jesse Pollard [this message]
2001-05-14 18:04           ` H. Peter Anvin
2001-05-14  1:31   ` Jonathan Lundell
  -- strict thread matches above, loose matches on Subject: below --
2001-05-14  2:59 Wayne.Brown
2001-05-11 23:57 Bingner Sam J. Contractor RSIS
2001-05-11 23:18 Wayne.Brown
2001-05-14 22:22 ` Kai Henningsen
2001-05-11 18:37 Wayne.Brown
2001-05-10 23:06 Wayne.Brown
2001-05-10 23:20 ` Hacksaw
2001-05-10 23:52   ` Jonathan Lundell
2001-05-11  0:07     ` Alexander Viro
2001-05-11  2:01       ` Jonathan Lundell
2001-05-11  9:21         ` Malcolm Beattie
2001-05-11  0:10 ` H. Peter Anvin
2001-05-11  1:31   ` David S. Miller
2001-05-11  1:32     ` Blue Lang
2001-05-11  9:31       ` Alan Cox
2001-05-11 12:25   ` Richard B. Johnson
2001-05-11  9:37 ` Alan Cox
2001-05-15 14:01 ` Anuradha Ratnaweera
2001-05-10 21:42 Richard B. Johnson
2001-05-10 22:38 ` H. Peter Anvin
2001-05-11  7:22 ` Tom Leete

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=200105141729.MAA28295@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=Wayne.Brown@altec.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=hacksaw@hacksaw.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=meissner@spectacle-pond.org \
    --cc=mharris@opensourceadvocate.org \
    --cc=vonbrand@sleipnir.valparaiso.cl \
    /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