Invalid character in name (Fortran90 -> Go) about quine-relay HOT 13 CLOSED

Looks a bug of f2c, tcc, or a combination of them, because QR.f outputs a broken QR.f90.
Did you update f2c recently? I guess this is a trigger. Can you try an old f2c?

from quine-relay.

I've built and tried AUR's f2c source tarball in Ubuntu.
It compiles QR.f successfully, but the executable writes the output to stderr instead of stdout.
I don't read the discussion of AUR, but I doubt if we can trust the tarball.

from quine-relay.

I'm the maintainer of the AUR package for f2c. On my system, the F77 -> F90 step segfaults when I use the default tcc for that step. However, the entire quine-relay runs all the way through with no errors at any step if I use gcc or clang instead. The programs that gcc and clang produce from the f2c'd source do not write anything to stderr, either.

Do you two still have problems if you use gcc or clang? If so, I'll look into them as potential bugs in the f2c package.

from quine-relay.

The quine-relay-git package installs and runs fine now, using gcc instead of tcc. tcc has not changed lately.

from quine-relay.

Hmm, then, f2c is innocent and the recent change of f2c may hit tcc's bug?

I wonder if we should use gcc instead of tcc. The reason why it uses tcc is because gcc (gfortran) seems to require huge memory to compile QR.f on some platforms. (#2)

from quine-relay.

Sounds like the recent change of f2c hit tcc's bug, yes.

Perhaps clang uses less memory than gcc and resolves both #2 and this? Would need to be tested.

from quine-relay.

Another option is to simply use $(CC) (which I believe defaults to cc if it's not defined by the environment, at least using GNU make), and let whoever's running it choose their own compiler using environment variables. Similarly you can use $(CXX) for the C++ compiler.

from quine-relay.

Unfortunately clang seems not to work so well.

$ /usr/bin/time -f "%M KB" gcc -o QR QR.c /usr/lib/libf2c.a 
702572 KB
$ /usr/bin/time -f "%M KB" clang -o QR QR.c /usr/lib/libf2c.a 
525980 KB
$ /usr/bin/time -f "%M KB" tcc -o QR QR.c /usr/lib/libf2c.a 
43872 KB

I guess it is a good idea to use $(CC) and to add to the document something like "try make CC=tcc if you have no enough memory."
But I have to check if $(CC) does not affect other compilation processes. In particular, gcc was very very slow to compile INTERCAL code, if I recall. I will do later.

from quine-relay.

Thanks for testing, the memory usage information is interesting.

from quine-relay.

It appears that passing -bfO to the intercal compiler (ick) causes it to "optimize" the C code it produces, in such a way that GCC takes less time to compile it. I haven't tested this rigorously yet.

from quine-relay.

Using -bfO and gcc is slightly faster than tcc without -bfO here, while gcc without -bfO is almost three times as slow.

Confirmed that gcc + -bfO is a viable alternative to tcc.

from quine-relay.

I think this is already fixed by #38. Closing.
Please let me know if I misunderstand. Thank you.

from quine-relay.

Sounds right! Thanks.

from quine-relay.