Size of executable output from gcc

[wongck]

The output executable from gcc are large.
A simple hello world executable was size over 100K+. Stripping it reduce it to 80K+.
Are there any switches to reduce the size?

[lp]

Edit: Never mind, reread your message. You already used strip.

[joska]

The output executable from gcc are large.
A simple hello world executable was size over 100K+. Stripping it reduce it to 80K+.
Are there any switches to reduce the size?

If you want to develop Atari/GEM-software, you are probably better off using PureC or AHCC. They produce much smaller binaries and does it a lot quicker. PureC can compile an entire project with a megabyte of source in a fraction of the time it takes gcc to compile hello.c.

[wongck]

Pure C... yes. I been using that for the last 18 years or so.... and Laser C before that.
I am at home with Pure C, just that I am thinking of some Mint programming.
Guess I am stuck with gcc, and the older version that I got from sparemint RPM don't help

[joska]

Pure C... yes. I been using that for the last 18 years or so.... and Laser C before that.
I am at home with Pure C, just that I am thinking of some Mint programming.

What kind of "MiNT programming" are you thinking of? There's nothing in MiNT that prevents you from using PureC. Or are you thinking about ported stuff?

[wongck]

What kind of "MiNT programming" are you thinking of? There's nothing in MiNT that prevents you from using PureC. Or are you thinking about ported stuff?

I am thinking of writting a device driver for a serial-USB thingy - USBwiz, or at least for the last 2 years or so among other things.
I read from somewhere that there are differences in the way the functions are called and sizes of integers/long which may give interfacing issues.
Of course I have seen XIF written in Assembler (like for the EtherNEC) so it may be just to keep an eye on the bytes that is required.

[joska]

What kind of "MiNT programming" are you thinking of? There's nothing in MiNT that prevents you from using PureC. Or are you thinking about ported stuff?

I am thinking of writting a device driver for a serial-USB thingy - USBwiz, or at least for the last 2 years or so among other things.
I read from somewhere that there are differences in the way the functions are called and sizes of integers/long which may give interfacing issues.

This is not a problem. You can set PureC to call functions by putting the arguments on the stack like MiNT expects. And long is the same in PureC and gcc, but PureC has 16 bit ints instead of gcc's 32 bit. Just use longs, or use AHCC which is PureC-compatible (and almost as fast) but can also use 32 bit ints.

However, you have to figure out how to access the kernel lib. I have never done this using PureC, so I don't know how to do that.

[wongck]

This is not a problem. You can set PureC to call functions by putting the arguments on the stack like MiNT expects. And long is the same in PureC and gcc, but PureC has 16 bit ints instead of gcc's 32 bit. Just use longs, or use AHCC which is PureC-compatible (and almost as fast) but can also use 32 bit ints.

Thanks for the pointers. I will keep them in mind.