From: Michael Meissner <meissner@spectacle-pond.org>
To: John Kodis <kodis@mail630.gsfc.nasa.gov>, linux-kernel@vger.kernel.org
Subject: Re: Not a typewriterg
Date: Mon, 14 May 2001 11:33:45 -0400 [thread overview]
Message-ID: <20010514113345.B10909@munchkin.spectacle-pond.org> (raw)
In-Reply-To: <mharris@opensourceadvocate.org> <200105140103.f4E13U3r010249@sleipnir.valparaiso.cl> <20010514103148.B9532@tux.gsfc.nasa.gov>
In-Reply-To: <20010514103148.B9532@tux.gsfc.nasa.gov>; from kodis@mail630.gsfc.nasa.gov on Mon, May 14, 2001 at 10:31:48AM -0400
On Mon, May 14, 2001 at 10:31:48AM -0400, John Kodis wrote:
> On Sun, May 13, 2001 at 09:03:30PM -0400, Horst von Brand wrote:
>
> > The old C compiler/old Unix linker guaranteed 6 chars in an external symbol
> > name only, and C functions got an underscore prepended: _creat. I guess
> > this is the reason for this wart. As to why 6 chars only, I'd guess some
> > data structure in the linker was laid out that way. Machines had a few
> > dozen Kbs of RAM then, space was precious.
>
> I recall that RSX-11 and a few other series of early DEC operating
> systems stored linker symbols in a "RAD50" encoding scheme which
> allowed 6 chararacters to be crammed into a 32-bit "long word". I
> suspect that this is where the limitation originated.
More trivia. Rad50 actually allows 5 characters per 32-bit word. The 50 is
actually 050 in octal (ie, 40 decimal), and allows you to have all 26 english
letters, 10 digits, a null, and 3 characters. At this stage, I don't remember
what the precise encoding is, or what the additional 3 characters were (I
suspect different systems used different characters). One of the first systems
I worked on professionally (Data General RDOS) used RAD50 in their object file
format.
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: meissner@redhat.com phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482
next prev parent reply other threads:[~2001-05-14 15:53 UTC|newest]
Thread overview: 15+ 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 ` Michael Meissner [this message]
2001-05-14 15:25 ` Michael Meissner
2001-05-14 17:01 ` Alan Cox
2001-05-14 17:16 ` Michael Meissner
2001-05-14 17:29 ` Jesse Pollard
2001-05-14 18:04 ` H. Peter Anvin
2001-05-14 1:31 ` Jonathan Lundell
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=20010514113345.B10909@munchkin.spectacle-pond.org \
--to=meissner@spectacle-pond.org \
--cc=kodis@mail630.gsfc.nasa.gov \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®