GDC prints diagnostic messages like importall to stderr instead of stdout (DMD behavior). This isn't normally a problem, but since rdmd invokes "<compiler> -v -o- -Ipath path/script.d" and uses an stdout redirect to capture compiler output, it means that these diagnostics are shown in the user's terminal unnecessarily. The solution would probably be to just print all of these to stdout, but I don't know if this goes against some GCC convention.
We could do, but it does not work with -pipe, which feeds everything sent to stdout straight to the assembler - think: `gcc -o - | as -o foo.o` For convenience, could simply error that options like -fd-verbose and -fvtls cannot work with -pipe.
Created attachment 35 [details] Modifies output of -fd-verbose to go to stdout
I recently played with rdmd, and these are the modifications required to GDC to make it work. As mentioned by ibuclaw, it won't work with -pipe and could probably use a few sanity checks for that condition.
> I recently played with rdmd, and these are the modifications required to GDC to > make it work. One way to work around that would be to change rdmd to use -deps flag (-fdeps for GDC) to get dependencies instead of -v.
Any updates here?
I have no intention to direct any compiler diagnostic output to stdout in the forseeable future, if that's what you mean.
OK, I'll close this as WONTFIX then.