Reworking FFT code

[twobob]

Originally Posted by geekmaster

That "broken image" in the post above is shown correctly in this embedded quote. Click this image to see the original HTML version.

Have to say it's a bit clearer when laid out in the tight Img. Which was probably Knc's intention. Hah! Bit clearer! I made a joke!

Must get out more

[geekmaster]

Originally Posted by twobob

Have to say it's a bit clearer when laid out in the tight Img. Which was probably Knc's intention. Hah! Bit clearer! I made a joke!

Must get out more

I replaced the image in the above post, but knc1's new version does not resize when you shrink the browser window like the previous version did. WYSIWYG. Sorry. There is still a dead image icon in knc1's post.

Why is it that in photography, an opaque object is easier to see than a clear object, but when discussing ideas, the opposite rule applies?

Obviously, 0-bits must be clear and 1-bits opaque, right? Take bit-clear and Bit-set functions for example.

[knc1]

Originally Posted by geekmaster

I noticed that. The new text does not resize like the previous version that I "screenshotted". An HTML page does not work very well inside the IMG tags you have in your post.

I deleted those, but the editor had other ideas in its preview processing.
They are gone for good now.

[twobob]

Originally Posted by knc1

I deleted those, but the editor had other ideas in its preview processing.
They are gone for good now.

Ah top-hole Either way the info is boss. Regardless of layout issues

Now to have a dig a bit deeper and see what can be dredged. Big thanks for this

[knc1]

Our Aboriginal Linux emulation environment has a gcc-4.2 based tool-chain installed.

Which has very poor support for VFP vectors (like, almost none).

There will be a delay, of from hours to weeks, while I update our emulation environment with the gcc-linaro tool-chain (gcc-4.7).

Grumble.

[twobob]

Homage for the effort mukka.

I will be ready and waiting hopefully by that point to engage it : )

Having spent all day doing erstwhile activities myself I know how you feel

[knc1]

The one we have (say: Thanks Rob) is a gcc-4.2 tool-chain built against uClibc.
Which is just fine for building static linked utilities.

So this one will be a gcc-4.7 tool-chain built against glibc (which may or may not work for producing kindle native applications). Maybe, if we are lucky, and the wind is blowing from the correct direction. If it doesn't, I will have to go back to the most recent gcc-4.6 compiler release.

Will include the C and C++ and C# front-ends.
Will ignore the Ada, Cobal, Fortran, VHDL, etc, etc, etc at my own request.
Sorry, no C# - that is one of the few languages that gcc does not do.

And all of this is going on as a "native build" within our QEMU-1.1.1 emulated environment.
If it seems I am always at the keyboard when someone posts here -
Well, just try to remember how slow a 300Mhz machine is.

Thank goodness, nobody wants OpenOffice on a Kindle.

[twobob]

Thanks Rob!
Pfft c#
I feel I have evolved from such a noddy language into the world of; vagrant bits; errant registers; and questionable memory handling!

Vive la evolution! (which probably sounded far saner in my head but meh)

[knc1]

Hmm...
Maybe there should be Ada available ...
Naw, lab126 isn't that organized.
Besides Amazon/lab126 is in business to make a buck with a consumer device.
Not to turn out code that once working, continues to work for a century or so.

Edit:
http://sourceforge.net/projects/arm-ada/files/Sources/

[twobob]

And for we noobies

The manual online http://www.adaic.org/standards/05rm/RM-Final.pdf

HTML http://www.adaic.org/standards/05rm/html/RM-TOC.html

Plain Text Ada Reference manual

Download RM-05-Txt.zip [559K bytes]

[knc1]

Originally Posted by twobob

And for we noobies

The manual online http://www.adaic.org/standards/05rm/RM-Final.pdf

HTML http://www.adaic.org/standards/05rm/html/RM-TOC.html

Plain Text Ada Reference manual

Download RM-05-Txt.zip [559K bytes]

Nice find.
For the antique computer manual collector -
I have the soft-cover, original, in wonderful shape, low mileage, only read by one grandmother on Saturdays, ...

Edit:
And if the reader found that manual a bit on the deep side ...
Think how long it would take to learn the 450 languages once used in embedded systems:
http://groups.engin.umd.umich.edu/CI...0/ada/ada.html

[knc1]

Of course, over twenty years has brought a bit of automation to the process of writing an Ada application.

And people are using it for things other than embedded programming.

Create your own web site application in less than 5 minutes (3 minutes if you type fast):
http://www.youtube.com/embed/2VOZ4_p7h2o?rel=0

Ref: http://code.google.com/p/ada-awa/

[twobob]

Originally Posted by knc1

3 minutes if you type fast):

I actually just guffawed.

Nice one

[geekmaster]

Originally Posted by knc1

Of course, over twenty years has brought a bit of automation to the process of writing an Ada application.

And people are using it for things other than embedded programming.

Create your own web site application in less than 5 minutes (3 minutes if you type fast):
http://www.youtube.com/embed/2VOZ4_p7h2o?rel=0

Ref: http://code.google.com/p/ada-awa/

And there are a LOT of people writing web site applications in COBOL too:
http://www.flexus.com/main/index.php...d=51&Itemid=61

And some people never got beyond the BASIC they learned in grade school. Web apps in Visual Basic:
http://www.youtube.com/watch?v=KQcz2eb5rYg

For some old people, learning those "new fangled" things like HTML would be just too hard, when that antique computer language that they grew up with can be hacked and bent with glued-on libraries to do modern things.

[knc1]

Originally Posted by twobob

I actually just guffawed.

Nice one

It would take me more than the 3:42 minutes of the video to think of a Title for a new blog.

KnetConnect.com is still showing a blank face to the world.
I was going to just clone my: http://OpenPlayer.org web-site and then change the banner/logo graphic into "something e-book".

But now will keep the above references bookmarked for "some day in the future".

For now, back to building glibc without first building Perl.