GCC asm() warning suppression options?

[Piru]

EDIT: Oh, I guess we have 'make -j n', but it's not very robust.

Code: [Select]

if [ -a /proc/cpuinfo ]; then
    export CONCURRENCY_LEVEL=$(($(grep -c processor /proc/cpuinfo) * 2 + 1))
    export MAKEOPTS="-j${CONCURRENCY_LEVEL}"
fiWhy wouldn't it be robust?

[Piru]

The main differences from a tool chain perspective, though, should be in the hunks supported. Everything else could be handled as it is today, and newlib, crt0.s, and amiga.lib could be written to run optimally on arbitrary releases. Having that magic at compile time, though, would result in much tighter binaries.

Well, some 32bit relocs could be made 16bit, that doesn't account for much in most binaries.

[Piru]

Perhaps the Makefiles are subtly flawed? There could be bits that have to be compiled before others that may not be guaranteed with concurrent jobs?

Just guessing here.

Well that's not it. The concurrent jobs are only used for things that can be concurrent. Obviously make cannot change the order of commands being executed, that'd never work.