On 15 Dec 2006 at 19:18, Chris M wrote:
> Is it a *recent* development of compilers that as an
> intermediate step the source code will first be
> reduced to assembler mnemonics, before being reduced
> to object code?
Those mnemonics aren't used by the compiler in many cases--they're
for the compiler writers and maintainers (and curious users who'd
like to take a peek). While I suppose looking at a binary dump of
the object code might reveal something, it's the hard way to answer
the question "Am I really generating the right code?"
There are many compilers that will generate code that can be
assembled by the same assembler that the programmers use, but if you
have a single target, why parse ASCII text if you don't have to? It
just slows the compilation process down. On the other hand, if
you're writing a compiler to generate native code on multiple
platforms, then using the standard assembler makes some sense. Saves
you from having to know about object file layout and such.
Every compiler needs some sort of assembly pass, if for nothing more
than to satisfy forward references. Because the code being generated
is fairly restricted as to form, a pass-and-a-half assembly phase is
often more than enough.
As to mnemonics, it's interesting that even in P-code
implementations, the instruction mnemonics are often one of the first
things specified in the design process. After all, you have to have
some way to talk about the instructions you're making up. If it's
native code you're compiling to, well, those are already made up for
you.
Cheers,
Chuck
--- Kelly Leavitt <kelly at catcorner.org> wrote:
> > > Andrew wrote...
> > > > BOG (no, not the toilet!)
> > > Absolutely no clue.
> >
> >
> Isn't there an expression: Bog standard
>
> Which just means ordinary or stock configuration?
>
> Kelly
>
Yes, something like that.
Thanks to whoever posted the
www.acronymfinder.com link.
Regards,
Andrew B
aliensrcooluk at yahoo.co.uk
Has anyone purchased from this guy?
He has a lot of weird stuff, but the pricing seems like he took the
high number form suggested range in "Collectible Microcomputers" and
multiplied it by 10 or 20.
You'll also note that every item is marked "rare" even things like
Atari 800!
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
>I could imagine that some of the lubricants that they used on the
>surfaces could have contributed to stiction. Although, the heads do
fly >when at speed, they do have to drag on the surface. For this they
also >put a very thin layer of lub on the surfaces.
Billy Pettit has been surprisingly quiet about all of this...
The one case of lubricant stiction I know of for a fact is in Quantum
Q540. Apple had a huge field failure problem because of this in HD40s.
They modified the firmware to giggle the head on powerup to help prevent
landing zone lubricant accumulation.
> Westerb Dynex drives were the inspiration for the top loading 5 and 10
> mb 2314 type patter and head drives.
Top-loading single platter drives are descendants of the IBM 5440 series
used on the System 3, which were copied by most of the players in the
day (Pertec, Wanco, Western Dynex, Diablo, etc.). DEC used the case
design for the RL01/2 but added an embedded servo track.
2314s are 20 surface top loading 'washing machine' drives. End of the
line for the head technology started on the 1311 (10 surface).
Had the chance last week to talk to one of the guys at Memorex who did
their early 2314 clones in the late 60's (sold to DEC as the RP01 and RP02).
none of the disks I have are likely to work. I do have
the floppy and expansion units. And Land O Goshen the
mobo has test points! And no no signs of life...
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
I've read several replies indicating that the drive needs to be taken apart.
People have also advocated just "hitting" the drive to break the stiction.
Holding the drive and giving it a quick twist around the spindle axis has always
worked for me and avoids potential problems with disassembly or damage.
Has anyone seen stiction on the IDE or later drives? The only stiction I've seen
has always been on the 5 1/4" MFM/RLL type drives, and probably ESDI/SCSI/SASI
as well although my experience is limited on those drives.
Something else I've noticed is that if a drive has stiction, that stiction will
return after the drive sets for a while again. Anyone know what actually causes
stiction?
Hi all. I'm writing an article for MIT's Technology Review magazine about
vintage computer replica kits. I need someone to interview RIGHT AWAY.
It's currently 1:30AM here on the east coast but that is okay. So, if
you're awake and have any opinions about the various replica kits, or
especially if you've built one or plan to get one soon, then email me
OFF-LIST but RIGHT NOW. (Sorry for the late notice!!) I'm at
evan at snarc.net. Be sure to leave your phone number because I don't have
time for playing tag tonight.
Thanks! At least 15 minutes of fame gauranteed. :)
- Evan
--- Tony Duell <ard at p850ug1.demon.co.uk> wrote:
> >
> > Andrew wrote...
> > > BOG (no, not the toilet!)
> > Absolutely no clue.
>
> Could it be BOT, which is Begining Of Tape (one of
> the sensors in a tape
> drive, the other being EOT (End Of Tape).
>
> Or SOG, neaning Sync On Green, refering to an
> analogue RGB video monitor
> where the gree nvideo signal is in fact composite
> video and includes the
> sync signal.
>
> -tony
>
Hmmm.... I could have mis-read "SOG" as "BOG",
I guess.
I have been rather tired lately.
Regards,
Andrew B
aliensrcooluk at yahoo.co.uk
