| |
|
Dentists
|
  |
| Joined: 09 Apr 2012 |
| Total Posts: 6624 |
|
|
| 25 Apr 2013 11:06 PM |
0101 1001 0100 0101 0101 0101 |
|
|
| Report Abuse |
|
|
1waffle1
|
  |
| Joined: 16 Oct 2007 |
| Total Posts: 16381 |
|
|
| 25 Apr 2013 11:06 PM |
| I'm going to guess that about ten in every billion people on this planet actually know machine code. |
|
|
| Report Abuse |
|
|
iStone4S
|
  |
| Joined: 07 May 2012 |
| Total Posts: 416 |
|
|
| 25 Apr 2013 11:07 PM |
| 1waffle1, I must be rare then. |
|
|
| Report Abuse |
|
|
coplox
|
  |
| Joined: 07 Jun 2008 |
| Total Posts: 3252 |
|
|
| 25 Apr 2013 11:08 PM |
Nobody does, you can't know binary code. You CAN know the binary patterns of the different ASCII characters but you didn't specify that. |
|
|
| Report Abuse |
|
|
1waffle1
|
  |
| Joined: 16 Oct 2007 |
| Total Posts: 16381 |
|
|
| 25 Apr 2013 11:08 PM |
| If you can type nothing but binary into a compiler and have it run a legit program, then yes, you are rare. |
|
|
| Report Abuse |
|
|
coplox
|
  |
| Joined: 07 Jun 2008 |
| Total Posts: 3252 |
|
|
| 25 Apr 2013 11:10 PM |
| Actually it could be quite easy, the OP doesn't realise though that binary is just a format of information storage. It depends on how the program/kernel/cpu interprets it. Just like writing a letter. |
|
|
| Report Abuse |
|
|
iStone4S
|
  |
| Joined: 07 May 2012 |
| Total Posts: 416 |
|
|
| 25 Apr 2013 11:10 PM |
| @1waffle1, give me a list of commands and I'll do it. But aside from that, I can do x86 machine code and my own machine code for my future CPU. |
|
|
| Report Abuse |
|
|
1waffle1
|
  |
| Joined: 16 Oct 2007 |
| Total Posts: 16381 |
|
|
| 25 Apr 2013 11:11 PM |
It is just redundant and useless that you would have to type binary code where binary is required for you to type. and then your code is compiled into binary.
digital binary -> machanical binary |
|
|
| Report Abuse |
|
|
1waffle1
|
  |
| Joined: 16 Oct 2007 |
| Total Posts: 16381 |
|
|
| 25 Apr 2013 11:15 PM |
@istone
do mak new kernel khtx |
|
|
| Report Abuse |
|
|
iStone4S
|
  |
| Joined: 07 May 2012 |
| Total Posts: 416 |
|
|
| 25 Apr 2013 11:19 PM |
| Well, I'm pretty sure x86 machine code has many revisions. I only know x86 machine code for 8086. |
|
|
| Report Abuse |
|
|
Quenty
|
  |
| Joined: 03 Sep 2009 |
| Total Posts: 9316 |
|
|
| 25 Apr 2013 11:37 PM |
| I know a tiny bit of ASCII binary, if that counts. |
|
|
| Report Abuse |
|
|
|
| 25 Apr 2013 11:59 PM |
| It is called assembly. I can only program in assembly on a couple processors, and always without operating systems. If you want to learn I suggest reading the pdf of "The Art of Assembly Language," which is just over 1400 pages long. |
|
|
| Report Abuse |
|
|
iStone4S
|
  |
| Joined: 07 May 2012 |
| Total Posts: 416 |
|
|
| 26 Apr 2013 12:00 AM |
| Arbiter, agreed, I can only do x86 assembly(8086 preferred.) DUO assembly(Check Duo adept and Duo compact on youtube.) And my own assembly which I have no name for. |
|
|
| Report Abuse |
|
|
|
| 26 Apr 2013 12:07 AM |
@coplex Some things only work on some processors, sometimes you will stall the pipeline, and a multitude of other problems. Bottom line: it requires TONS of knowledge on exactly how the not just how a single version of a processor works, but how the whole system works. It also requires tons of research for hardware, because every device is different and all have massive manuals. This isn't to mention the low readability without comments, and the long development time and the possibility of crashing your computer or writing over data that shouldn't be written over, or fudging the cmos. In short, it is NOT easy. |
|
|
| Report Abuse |
|
|
coplox
|
  |
| Joined: 07 Jun 2008 |
| Total Posts: 3252 |
|
|
| 26 Apr 2013 12:22 AM |
| I meant it is easy to remember what each bit pattern means and what opcode it represents. |
|
|
| Report Abuse |
|
|
|
| 26 Apr 2013 12:41 AM |
Pift! say you have a single byte. This byte has 8 bits, and codes for an instruction. There is 2^8 (256) possible instructions from that single byte, and then there is the 2 bytes appended to the end of the instruction if it is requires more data for a constant or address.
Let me tell you one thing, if the hardware was complex, and hardware designers think it is a peice of cake and name the 80x86 instruction sets "CISC instruction sets" (Complex Instruction Set Computers), you know that it has to be complicated in the extreme. |
|
|
| Report Abuse |
|
|
iStone4S
|
  |
| Joined: 07 May 2012 |
| Total Posts: 416 |
|
|
| 26 Apr 2013 12:50 AM |
CISC isn't that complex, in fact, I think it's very simple, mostly in implementation.
To add 2 addresses in CISC, you would have to do ADD [address 1], [address 2]
In RISC, you would have to do... MOV [address 1], AX MOV [address 2], BX ADD AX, BX MOV AX, [address 2]
So, yeah. |
|
|
| Report Abuse |
|
|
|
| 26 Apr 2013 12:53 AM |
| The assembler does the work in that case, but when you code plain 80x86 CISC binary code, it gets tricky. RISC is the x86 binary code that you are probably use to. |
|
|
| Report Abuse |
|
|
iStone4S
|
  |
| Joined: 07 May 2012 |
| Total Posts: 416 |
|
|
| 26 Apr 2013 01:14 AM |
| 80x86 CISC? Sorry, I haven't heard of that. And yes, x86 is RISC. |
|
|
| Report Abuse |
|
|
TeamDman
|
  |
| Joined: 04 Dec 2009 |
| Total Posts: 897 |
|
| |
|
|
| 26 Apr 2013 08:34 AM |
| BASIC is what's cool these days c: |
|
|
| Report Abuse |
|
|
Tappier
|
  |
| Joined: 10 Apr 2013 |
| Total Posts: 14077 |
|
| |
|
TNOMCat
|
  |
| Joined: 02 Aug 2011 |
| Total Posts: 156 |
|
|
| 26 Apr 2013 10:23 AM |
| assembly isnt machine code. you compile it to machine code |
|
|
| Report Abuse |
|
|
austinnix
|
  |
| Joined: 17 Feb 2009 |
| Total Posts: 403 |
|
|
| 26 Apr 2013 11:29 AM |
Im not the best, I'n just write with it, and them, im still to lazy to decode it letter by letter. (ASCII) This is how I translate text/binary binary/text (decimal/binary binary/decimal included).. Just a translation site. Its all I can really do. Does that count.. :D? Site: http://www.binarytranslator.com/ DONT BAN ME, WOBLOX.
|
|
|
| Report Abuse |
|
|