Other the other hand, C (C++…) is inadequate to express the parallelism
and deep pipeline nature of todays modern superscaler
superpipeline/VLIW/EPIC MPU architecture.
The problem is specially acute if one has to deal with new processor
features with more and more compiler intrinsics, if one is lucky to have
them in the first place (that is, someone has to do the dirty work for you).
Bi
-----Original Message-----
From: Calvin H. Guan [mailto:xxxxx@hotpop.com]
Sent: Monday, October 21, 2002 12:10 PM
To: NT Developers Interest List
Subject: [ntdev] Re: C++ in kernel. was Re: Batch file for Visual Stud
io build,
Gary, you are right. It’s really pain in the butt to write machine code.
When I was a 3rd-year university student, we were required to write the
assemble source code, look up the opcode from the instruction set table,
calculate the jmp/call/memory offsets and enter the opcodes by using a
stupid keyboard with keys “0-9”,and “a-f”. When done, then hit the “exec”
key to run. Although we have the nice assembler and ICE for that
processor, we were not allow to use it until we knew how to manually
“assemble and link” the source code.
Ain’t it funny? Not at all.
You are currently subscribed to ntdev as: xxxxx@appstream.com
To unsubscribe send a blank email to %%email.unsub%%