This is the mail archive of the
mailing list for the GCC project.
Re: Async I/O patch with compilation fix
this is seriously weird - there is not even an I/O statement in that test case.
One question: Is this real hardware or an emulator?
Also, Could you try a few things?
Run the test case manually. Do you still fail?
Is there an error if the executable is run under valgrind?
If you have two compilers, one with the patch and one without: Is there a difference in the generated files for
-dump-tree-original, -fdump-tree-optimized and -S?