GCC for tha AMIGA...

 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements GCC for tha AMIGA...
# 1  
Old 03-28-2015
GCC for tha AMIGA...

Hi guys...

For the AMIGA fans out there...

Not sure if this is the right forum but someone has done a successful working port of gcc for the classic AMIGA A1200.

It contains a very large subset of *NIX commands and now AMIGA fanatics like me can include another platform, within the platforms limits.

The gcc version is old 2.95.3 but hey the platform is old too and opens up a new avenue to learn shell scripting.

The shell is ksh.

The source code is there along with pre-compiled binaries, much more too.

It is on AMINET here:-

Aminet - dev/gcc/ADE.zip

Get out your old A1200s and have a little fun... ;oD
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. What is on Your Mind?

The AMIGA, great or flop. Your memories...

Hi everybody... Anyone who sees posts from me see the word AMIGA on my machines' terminal prompts. AMINET is the oldest Internet SW repository and currently holds 82,800+ freely available SW packages. About Aminet - AminetWiki I am a member of LAG, (Linclonshire Amiga Group), in the... (5 Replies)
Discussion started by: wisecracker
5 Replies

2. OS X (Apple)

Back on python for the AMIGA again and discovered this little gem...

I am back on Python for the AMIGA again and discovered this little gem that exits the program:- (If you search GOOGLE as 'os.sys.exit()' python nothing seems to appear.) import os os.sys.exit()I know of the other four and how they apply but I have no idea whether this creates any zombies or... (2 Replies)
Discussion started by: wisecracker
2 Replies

3. OS X (Apple)

FFT for the AMIGA through ksh88 shell.

I don't know if anyone is interested but I have been meddling with FFT for the AMIGA. (Sadly we AMIGAns don't have these luxuries through any scripting language. Below is a Python snippet that uses the builtin 'cmath' module to work with the lowly Python 2.0.1 for the AMIGA. It is part of a... (0 Replies)
Discussion started by: wisecracker
0 Replies

4. What is on Your Mind?

GIF Anim of my AMIGA real Oscilloscope.

Firstly I don't know where to put this so if it is the wrong forum then chastise me... ;oD I built the hardware and wrote the software for an Audio Oscilloscope DC-100KHz in 2001 for the A1200(HD) via the AMIGA parallel port. It clocks the port at 200KHz, although 250KHz was easy enough via a... (4 Replies)
Discussion started by: wisecracker
4 Replies

5. What is on Your Mind?

Ah, the AMIGA, (another poem I wrote in 2005).

Well I wrote this in 2005 and uploaded to AMINET.as a commemoration of a machine that is still in use today. It is now 29 years since this machne came into being. Phenominal and it is still being supported- WOW! My A1200 is on 24/7 and I use it to test code developed on AMIGA emulators... ... (0 Replies)
Discussion started by: wisecracker
0 Replies

6. What is on Your Mind?

A journey down memory lane - AMIGA...

Hi guys and gals... Who still plays with the AMIGA in any of its guises? I have a classic A1200(HD) on 24/7 and still build and code for it... Also _clones_ of the same machine using WinUAE and E-UAE... It still has that one major beauty for this 62 year old - moi - it is FUN! ;o) (2 Replies)
Discussion started by: wisecracker
2 Replies

7. Shell Programming and Scripting

Perl: array name tha contains contents of a variable

Hi there I have a counter called my $counter = 0; I am trying to build an array that will have a name that is for example my @array0 = ("some", "stuff"); but instead of hard coding the "0" in the array name i want to use whatever value the aforementioned $counter has in it...so ... (1 Reply)
Discussion started by: hcclnoodles
1 Replies

8. Solaris

Installing gcc - recieve error message gcc : cannot execute

AIM- Install Oracle 11g on Solaris using VMWare Steps 1.Logged on as root 2.Created subfolders à /usr/local/bin & /usr/local/bin/gcc 3.Downloaded gcc & libiconv & unzipped them on my harddrive & burnt them on CD 4.Copied files from CD to /usr/local/bin/gcc 5.Terminal (root) à pkgadd -d... (8 Replies)
Discussion started by: Ackers
8 Replies
Login or Register to Ask a Question
ERROR::SDT(7stap)														 ERROR::SDT(7stap)

NAME
error::sdt - <sys/sdt.h> marker failures DESCRIPTION
Systemtap's <sys/sdt.h> probes are modeled after the dtrace USDT API, but are implemented differently. They leave a only a NOP instruction in the userspace program's text segment, and add an ELF note to the binary with metadata. This metadata describes the marker's name and parameters. This encoding is designed to be parseable by multiple tools (not just systemtap: GDB, the GNU Debugger, also contains sup- port). These allow the tools to find parameters and their types, wherever they happen to reside, even without DWARF debuginfo. The reason finding parameters is tricky is because the STAP_PROBE / DTRACE_PROBE markers store an assembly language expression for each op- erand, as a result of use of gcc inline-assembly directives. The compiler is given a broad gcc operand constraint string ("nor") for the operands, which usually works well. Usually, it does not force the compiler to load the parameters into or out of registers, which would slow down an instrumented program. However, some instrumentation sites with some parameters do not work well with the default "nor" con- straint. unresolveable at run-time GCC may emit strings that an assembler could resolve (from the context of compiling the original program), but a run-time tool can- not. For example, the operand string might refer to a label of a local symbol that is not emitted into the ELF object file at all, which leaves no trace for the run-time. Reference to such parameters from within systemtap can result in "SDT asm not understood" errors. too complicated expression GCC might synthesize very complicated assembly addressing modes from complex C data types / pointer expressions. systemtap or gdb may not be able to parse some valid but complicated expressions. Reference to such parameters from within systemtap can result in "SDT asm not understood" errors. overly restrictive constraint GCC might not be able to even compile the original program with the default "nor" constraint due to shortage of registers or other reasons. A compile-time gcc error such as "asm operand has impossible constraints" may result. There are two general workarounds to this family of problems. change the constraints While compiling the original instrumented program, set the STAP_SDT_ARG_CONSTRAINT macro to different constraint strings. See the GCC manual about various options. For example, on many machine architectures, "r" forces operands into registers, and "g" leaves operands essentially unconstrained. revert to debuginfo As long as the instrumented program compiles, it may be fine simply to keep using <sys/sdt.h> but eschew extraction of a few indi- vidual parameters. In the worst case, disable <sys/sdt.h> macros entirely to eschew the compiled-in instrumentation. If DWARF debuginfo was generated and preserved, a systemtap script could refer to the underlying source context variables instead of the positional STAP_PROBE parameters. SEE ALSO
stap(1), stapprobes(3stap), error::dwarf(7stap), http://gcc.gnu.org/onlinedocs/gcc/Constraints.html, http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation, error::reporting(7stap) ERROR::SDT(7stap)