From: Christophe Lyon <christophe.lyon@linaro.org>
To: tk@tkoenig.net
Cc: koenigni@student.ethz.ch,
Andre Simoes Dias Vieira <Andre.SimoesDiasVieira@arm.com>,
gcc Patches <gcc-patches@gcc.gnu.org>,
fortran@gcc.gnu.org, Thomas Koenig <tkoenig@netcologne.de>,
Ulrich Weigand <uweigand@de.ibm.com>,
David Edelsohn <dje.gcc@gmail.com>,
clyon@gcc.gnu.org
Subject: Re: Async I/O patch with compilation fix
Date: Mon, 06 Aug 2018 11:33:00 -0000 [thread overview]
Message-ID: <CAKdteObf6sgiC7kGnVLcShdTX6gBJfqiSDNrsht56ehR0Ptohw@mail.gmail.com> (raw)
In-Reply-To: <EC190FA0-60D1-46B2-B462-335634159C43@tkoenig.net>
On Sat, 4 Aug 2018 at 00:42, Thomas König <tk@tkoenig.net> 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?
Yes.
> 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
executed
> Regards, Thomas
next prev parent reply other threads:[~2018-08-06 11:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 19:28 AsyncI/O patch committed Nicolas Koenig
2018-07-26 13:31 ` Build fail on gthr-simple.h targets (Re: AsyncI/O patch committed) Ulrich Weigand
2018-07-26 13:40 ` Build fail on gthr-single.h " Ulrich Weigand
2018-07-26 20:54 ` Build fail on gthr-simple.h " Thomas Koenig
2018-07-27 7:31 ` Thomas Koenig
2018-07-27 12:26 ` David Edelsohn
2018-07-31 8:45 ` Andre Vieira (lists)
2018-07-31 10:30 ` Thomas König
2018-08-02 11:35 ` Async I/O patch with compilation fix Nicolas Koenig
2018-08-02 15:43 ` Christophe Lyon
2018-08-02 17:08 ` Nicolas Koenig
2018-08-03 8:46 ` Christophe Lyon
2018-08-03 22:43 ` Thomas König
2018-08-06 11:33 ` Christophe Lyon [this message]
2018-08-17 15:41 ` Thomas Koenig
2018-08-18 22:44 ` Christophe Lyon
2018-08-19 13:40 ` Thomas Koenig
[not found] ` <CAKdteObsx+RK2t-OteU_w6L_Pv7FGLpAcLrHaPY4NDAamV-z7g@mail.gmail.com>
2018-08-21 19:43 ` Thomas Koenig
2018-08-21 20:08 ` Fwd: " Thomas Koenig
2018-08-22 18:49 ` David Edelsohn
2018-08-22 21:31 ` Thomas Koenig
2018-08-23 12:25 ` David Edelsohn
2018-08-23 17:42 ` Thomas Koenig
2018-08-23 12:53 ` David Edelsohn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKdteObf6sgiC7kGnVLcShdTX6gBJfqiSDNrsht56ehR0Ptohw@mail.gmail.com \
--to=christophe.lyon@linaro.org \
--cc=Andre.SimoesDiasVieira@arm.com \
--cc=clyon@gcc.gnu.org \
--cc=dje.gcc@gmail.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=koenigni@student.ethz.ch \
--cc=tk@tkoenig.net \
--cc=tkoenig@netcologne.de \
--cc=uweigand@de.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).