If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
The variable bit cpu
Hi,
I think I might have just invented the variable bit cpu It works simply like this: Each "data bit" has a "meta data bit". The meta data bit describes if the bit is the ending bit of a possibly large structure/field. The meta bits together form a sort of bit mask or bit pattern. For example the idea is best seen when putting the data bits and meta bits below each other. data bits: 01110101110101101010101 meta bits: 00000000100010001100001 In reality the data bit and meta bit are grouped together as a single entity which can be read into the cpu since otherwise the cpu would not know where to start reading the data or meta bits. Now it simplies start with the first data + meta bit pair. Because a cpu might need to know the length of the bit field up front the cpu/algorithm works simply as follows: The cpu starts reading data and meta bits until it reaches a meta bit of 1. All bits that form the variable bit field are now read and can be used etc. The above example then looks like this: data bits: 011101011#1010#1101#0#10101 meta bits: 000000001#0001#0001#1#00001 (The # sign is too indicate to you where the variable bit fields are.) Notice how even single bit fields are possible. The reason for the variable bit cpu with variable bit software is too save costs and to make computers/software even more powerfull and usefull For example: Currently fixed bitsoftware has to be re-written or modified, re-compiled, re-documented, re-distributed, re-installed, re-configured when it's fixed bit limit is reached and has to be increased for example from 32 bit to 64 bit etc. Example are windows xp 32 to 64 bit, the internet IPv4 to IPv6. Bye, Skybuck. |
#2
|
|||
|
|||
"Skybuck Flying" wrote in message ... Hi, I think I might have just invented the variable bit cpu It works simply like this: Each "data bit" has a "meta data bit". The meta data bit describes if the bit is the ending bit of a possibly large structure/field. The meta bits together form a sort of bit mask or bit pattern. For example the idea is best seen when putting the data bits and meta bits below each other. data bits: 01110101110101101010101 meta bits: 00000000100010001100001 In reality the data bit and meta bit are grouped together as a single entity which can be read into the cpu since otherwise the cpu would not know where to start reading the data or meta bits. Now it simplies start with the first data + meta bit pair. Because a cpu might need to know the length of the bit field up front the cpu/algorithm works simply as follows: The cpu starts reading data and meta bits until it reaches a meta bit of 1. All bits that form the variable bit field are now read and can be used etc. The above example then looks like this: data bits: 011101011#1010#1101#0#10101 meta bits: 000000001#0001#0001#1#00001 (The # sign is too indicate to you where the variable bit fields are.) Notice how even single bit fields are possible. The reason for the variable bit cpu with variable bit software is too save costs and to make computers/software even more powerfull and usefull For example: Currently fixed bitsoftware has to be re-written or modified, re-compiled, re-documented, re-distributed, re-installed, re-configured when it's fixed bit limit is reached and has to be increased for example from 32 bit to 64 bit etc. Example are windows xp 32 to 64 bit, the internet IPv4 to IPv6. Hmmm. What about the instructions? What will be their length? Also, how would you implement that CPU in hardware? I mean at some point you'd have to have a fixed number of bits next to each other to perform operations on them. You could make various I/O buses serial and ramp up the frequency on those to make them really fast, but you'd still have to deserialize the data somewhere, which could cause a bottleneck. -- NoRemorse "Expect me when you see me." |
#3
|
|||
|
|||
"NoRemorse" wrote in message ... "Skybuck Flying" wrote in message ... Hi, I think I might have just invented the variable bit cpu It works simply like this: Each "data bit" has a "meta data bit". The meta data bit describes if the bit is the ending bit of a possibly large structure/field. The meta bits together form a sort of bit mask or bit pattern. For example the idea is best seen when putting the data bits and meta bits below each other. data bits: 01110101110101101010101 meta bits: 00000000100010001100001 In reality the data bit and meta bit are grouped together as a single entity which can be read into the cpu since otherwise the cpu would not know where to start reading the data or meta bits. Now it simplies start with the first data + meta bit pair. Because a cpu might need to know the length of the bit field up front the cpu/algorithm works simply as follows: The cpu starts reading data and meta bits until it reaches a meta bit of 1. All bits that form the variable bit field are now read and can be used etc. The above example then looks like this: data bits: 011101011#1010#1101#0#10101 meta bits: 000000001#0001#0001#1#00001 (The # sign is too indicate to you where the variable bit fields are.) Notice how even single bit fields are possible. The reason for the variable bit cpu with variable bit software is too save costs and to make computers/software even more powerfull and usefull For example: Currently fixed bitsoftware has to be re-written or modified, re-compiled, re-documented, re-distributed, re-installed, re-configured when it's fixed bit limit is reached and has to be increased for example from 32 bit to 64 bit etc. Example are windows xp 32 to 64 bit, the internet IPv4 to IPv6. Hmmm. What about the instructions? What will be their length? Everything inside the computer can be "encoded" using "the variable bit field format" as explained in the original post. The meta data bit indicates when the end of a field is reached thus indicating the length or end. To answer your question the cpu instructions are encoded as variable bit fields as well. Also, how would you implement that CPU in hardware? I mean at some point you'd have to have a fixed number of bits next to each other to perform operations on them. You could make various I/O buses serial and ramp up the frequency on those to make them really fast, but you'd still have to deserialize the data somewhere, which could cause a bottleneck. Implementing such a CPU requires a little change in thinking. I have not yet thought of how to do variable bit binary arithmetic operations but I will look into it Though a variable bit field format is a good start Thanks for your questions and interest etc Bye, Skybuck. |
#4
|
|||
|
|||
Skybuck Flying wrote: "NoRemorse" wrote in message ... "Skybuck Flying" wrote in message ... Hi, I think I might have just invented the variable bit cpu It works simply like this: Each "data bit" has a "meta data bit". The meta data bit describes if the bit is the ending bit of a possibly large structure/field. The meta bits together form a sort of bit mask or bit pattern. For example the idea is best seen when putting the data bits and meta bits below each other. data bits: 01110101110101101010101 meta bits: 00000000100010001100001 In reality the data bit and meta bit are grouped together as a single entity which can be read into the cpu since otherwise the cpu would not know where to start reading the data or meta bits. Now it simplies start with the first data + meta bit pair. Because a cpu might need to know the length of the bit field up front the cpu/algorithm works simply as follows: The cpu starts reading data and meta bits until it reaches a meta bit of 1. All bits that form the variable bit field are now read and can be used etc. The above example then looks like this: data bits: 011101011#1010#1101#0#10101 meta bits: 000000001#0001#0001#1#00001 (The # sign is too indicate to you where the variable bit fields are.) Notice how even single bit fields are possible. The reason for the variable bit cpu with variable bit software is too save costs and to make computers/software even more powerfull and usefull For example: Currently fixed bitsoftware has to be re-written or modified, re-compiled, re-documented, re-distributed, re-installed, re-configured when it's fixed bit limit is reached and has to be increased for example from 32 bit to 64 bit etc. Example are windows xp 32 to 64 bit, the internet IPv4 to IPv6. Hmmm. What about the instructions? What will be their length? Everything inside the computer can be "encoded" using "the variable bit field format" as explained in the original post. The meta data bit indicates when the end of a field is reached thus indicating the length or end. To answer your question the cpu instructions are encoded as variable bit fields as well. Also, how would you implement that CPU in hardware? I mean at some point you'd have to have a fixed number of bits next to each other to perform operations on them. You could make various I/O buses serial and ramp up the frequency on those to make them really fast, but you'd still have to deserialize the data somewhere, which could cause a bottleneck. Implementing such a CPU requires a little change in thinking. I have not yet thought of how to do variable bit binary arithmetic operations but I will look into it Though a variable bit field format is a good start Thanks for your questions and interest etc Bye, Skybuck. No one's gonna listen to you jerk! |
#5
|
|||
|
|||
"nydwarf" wrote in message oups.com... Skybuck Flying wrote: "NoRemorse" wrote in message ... "Skybuck Flying" wrote in message ... Hi, I think I might have just invented the variable bit cpu It works simply like this: Each "data bit" has a "meta data bit". The meta data bit describes if the bit is the ending bit of a possibly large structure/field. The meta bits together form a sort of bit mask or bit pattern. For example the idea is best seen when putting the data bits and meta bits below each other. data bits: 01110101110101101010101 meta bits: 00000000100010001100001 In reality the data bit and meta bit are grouped together as a single entity which can be read into the cpu since otherwise the cpu would not know where to start reading the data or meta bits. Now it simplies start with the first data + meta bit pair. Because a cpu might need to know the length of the bit field up front the cpu/algorithm works simply as follows: The cpu starts reading data and meta bits until it reaches a meta bit of 1. All bits that form the variable bit field are now read and can be used etc. The above example then looks like this: data bits: 011101011#1010#1101#0#10101 meta bits: 000000001#0001#0001#1#00001 (The # sign is too indicate to you where the variable bit fields are.) Notice how even single bit fields are possible. The reason for the variable bit cpu with variable bit software is too save costs and to make computers/software even more powerfull and usefull For example: Currently fixed bitsoftware has to be re-written or modified, re-compiled, re-documented, re-distributed, re-installed, re-configured when it's fixed bit limit is reached and has to be increased for example from 32 bit to 64 bit etc. Example are windows xp 32 to 64 bit, the internet IPv4 to IPv6. Hmmm. What about the instructions? What will be their length? Everything inside the computer can be "encoded" using "the variable bit field format" as explained in the original post. The meta data bit indicates when the end of a field is reached thus indicating the length or end. To answer your question the cpu instructions are encoded as variable bit fields as well. Also, how would you implement that CPU in hardware? I mean at some point you'd have to have a fixed number of bits next to each other to perform operations on them. You could make various I/O buses serial and ramp up the frequency on those to make them really fast, but you'd still have to deserialize the data somewhere, which could cause a bottleneck. Implementing such a CPU requires a little change in thinking. I have not yet thought of how to do variable bit binary arithmetic operations but I will look into it Though a variable bit field format is a good start Thanks for your questions and interest etc Bye, Skybuck. No one's gonna listen to you jerk! I don't give a **** what you think,say or do. So go **** yourself. Yup that's me =D Bye, Skybuck. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
The variable bit cpu | Skybuck Flying | Asus Motherboards | 3 | August 2nd 05 06:48 AM |
The variable bit cpu | Skybuck Flying | General | 3 | August 1st 05 02:59 PM |
vcore mod a7n8x-x | Moods | Asus Motherboards | 1 | January 18th 04 10:23 AM |
Q-fan settings and buying a variable speed detectable and variable fan: WTF | kgs | Asus Motherboards | 21 | January 6th 04 01:32 AM |
Do FX5200 (non Ultra) have variable speed fans? | Harry Muscle | Nvidia Videocards | 5 | August 28th 03 06:01 AM |