The variable bit cpu

[Skybuck Flying]

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: 011101011101011 01010101
meta bits: 000000001000100 01100001

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.

[Michael Mair]

Skybuck Flying wrote:

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: 011101011101011 01010101
meta bits: 000000001000100 01100001

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.

Why don't you just show us your C implementation and show us how this
improves or countermands a good, portable (whatever that may mean)
programming style.
Otherwise, I fear you are rather off-topic round here and may go on to
comp.programmin g or wherever appropriate.

-Michael
--
E-Mail: Mine is an /at/ gmx /dot/ de address.

[Flash Gordon]

Michael Mair wrote:

Skybuck Flying wrote:
<snip rubbish>
Why don't you just show us your C implementation and show us how this
improves or countermands a good, portable (whatever that may mean)
programming style.
Otherwise, I fear you are rather off-topic round here and may go on to
comp.programmin g or wherever appropriate.

I suggest you search the archives for other rubbish posted by skybuck.
This kill file it.
--
Flash Gordon
Living in interesting times.
Although my email address says spam, it is real and I read it.

[Michael Mair]

Flash Gordon wrote:

Michael Mair wrote:

Skybuck Flying wrote:

<snip rubbish>

Why don't you just show us your C implementation and show us how this
improves or countermands a good, portable (whatever that may mean)
programming style.
Otherwise, I fear you are rather off-topic round here and may go on to
comp.programmin g or wherever appropriate.

I suggest you search the archives for other rubbish posted by skybuck.
This kill file it.

Thanks for the suggestion -- Skybuck already has spent some time
in my killfile but got out on probation. Guess this settles it.

Cheers
Michael
--
E-Mail: Mine is an /at/ gmx /dot/ de address.

[CBFalconer]

Michael Mair wrote:

Flash Gordon wrote:

Michael Mair wrote:

Skybuck Flying wrote:

<snip rubbish>

Why don't you just show us your C implementation and show us
how this improves or countermands a good, portable (whatever
that may mean) programming style.
Otherwise, I fear you are rather off-topic round here and may
go on to comp.programmin g or wherever appropriate.

I suggest you search the archives for other rubbish posted by
skybuck. This kill file it.

Thanks for the suggestion -- Skybuck already has spent some time
in my killfile but got out on probation. Guess this settles it.

Makes almost as much sense as Reaganomics. He even multi-posted
it. He's gone.

--
"If you want to post a followup via groups.google.c om, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson

[Skybuck Flying]

"Michael Mair" <Mi**********@i nvalid.invalid> wrote in message
news:3l******** *****@individua l.net...

Skybuck Flying wrote:

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: 011101011101011 01010101
meta bits: 000000001000100 01100001

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.

Why don't you just show us your C implementation and show us how this
improves or countermands a good, portable (whatever that may mean)
programming style.
Otherwise, I fear you are rather off-topic round here and may go on to
comp.programmin g or wherever appropriate.

There is no implementation yet.

Though you are free to think about this concept/idea and maybe find a way
how to implement it in C ;)

Bye,
Skybuck.

[Malcolm]

"Skybuck Flying" <no****@hotmail .com> wrote

I think I might have just invented the variable bit cpu :)

It works simply like this:
Each "data bit" has a "meta data bit".

This is on topic for an electronic engineering, CPU design type newsgroup,
but not on comp.lang.c.

It sounds like an idea that might be worth exploring further, but I'm not a
hardware person. You would double memory costs, but these days that is only
a slight penalty. You would certainly be able to catch a lot of illegal
operations at a very low level. What I couldn't tell you is what the effect
would be on the speed and costs of building such a chip, which is why this
ng isn't the best place to discuss this.

However you might want to look at Fibonnacci computers to see a related,
though different, idea.

[Skybuck Flying]

Yeah after some feedback a more efficient encoding could be used for large
values/data.

type field + type marker + length field + length maker + data

For example
1 bit 1 bit 20 bits 20 bits +
data

The first 4 fields all use the original idea of gaining flexible fields.

Since the length is now known the remaining data does not need any markers.

(Instead of meta bits I now called them markers a term borried from the ibm
1401 reference manual ;))

The type field is to indicate the encoding type.

Bye,
Skybuck.

"Malcolm" <re*******@btin ternet.com> wrote in message
news:dc******** **@nwrdmz01.dmz .ncs.ea.ibs-infra.bt.com...

"Skybuck Flying" <no****@hotmail .com> wrote

I think I might have just invented the variable bit cpu :)

It works simply like this:
Each "data bit" has a "meta data bit".
This is on topic for an electronic engineering, CPU design type newsgroup,
but not on comp.lang.c.

It sounds like an idea that might be worth exploring further, but I'm not

a hardware person. You would double memory costs, but these days that is only a slight penalty. You would certainly be able to catch a lot of illegal
operations at a very low level. What I couldn't tell you is what the effect would be on the speed and costs of building such a chip, which is why this
ng isn't the best place to discuss this.

However you might want to look at Fibonnacci computers to see a related,
though different, idea.

[Giannis Papadopoulos]

Skybuck Flying wrote:

Hi,

I think I might have just invented the variable bit cpu :)
Apart from the off-topic, you haven't invented it yet... You simply
proposed a scheme that cannot necessarily be implemented - well, it
might be, but I am not very sure that it would be helpful at all.
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: 011101011101011 01010101
meta bits: 000000001000100 01100001
You have already doubled the memory you are using.
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.
The CPU does not read bits... If it has some kind of a cache, it moves
memory blocks of many bytes from memory to the cache and several bytes
from the cache to the registers (4bytes if 32bit, 8bytes if 64bit).

How big would the registers be in this hypothetical machine of variable
bits? And it would be better if called "variable word".

And if you would suggest to get rid of cache, it would severely harm
perfomance.
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 ;)

You wouldn't accomplish all that, but you'd just removed the fuss from
the programmer to choose whether to use int, char, long, long long etc.

However, you could more easily write a profiler that would scan the
program, estimate the range of values of every variable and assign the
proper type to the variable. It would be nice that one...
--
one's freedom stops where other's begin

Giannis Papadopoulos
http://dop.users.uth.gr/
University of Thessaly
Computer & Communications Engineering dept.

[Eric Sosman]

Skybuck Flying wrote:

Skybuck Flying wrote:

I think I might have just invented the variable bit cpu :)

There is no implementation yet.

Such machines existed in the 1960's; I personally used
one in 1966 and 1967. If you can show that your invention
predated that era, you may be able to sue IBM for patent
infringement and make yourself a very rich man. (Or woman.
Or mollusc, or slime mold; whatever.)

However tenuous the legal argument may be, the potential
rewards are surely enormous. Were I in your enviable position,
I would strain every sinew to wresting my pot of gold from
plutocratic corporate Amerika, even if the effort left me no
time to pollute Usenet with nonsense.

--
Eric Sosman
es*****@acm-dot-org.invalid