This is the mail archive of the
mailing list for the GCC project.
Re: Async I/O patch with compilation fix
On Sat, 4 Aug 2018 at 00:42, Thomas König <firstname.lastname@example.org> wrote:
> Hi Cristophe,
> 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?
I'm using QEMU
> 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?
I don't know how to do that with qemu, nor if valgrind supports armeb?
> 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?
I posted a few comments in the associated PR:
- the .s files are the same with /without the patch, so I suppose the
problem comes from the runtime libraries
- I've attached both execution traces and output from objdump on the
statically linked executable, so as to hopefully include all the code
> Regards, Thomas