From: Vladimir Makarov <vmakarov@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: One more path to fix PR70478
Date: Tue, 11 Apr 2017 17:27:00 -0000 [thread overview]
Message-ID: <caa19ec3-1b78-35c6-df33-c1bc6ed4df1a@redhat.com> (raw)
In-Reply-To: <be4f9305-12fe-ec36-fa76-29782d13cfbd@redhat.com>
On 04/11/2017 11:42 AM, Vladimir Makarov wrote:
>
>
> Yes, Christophe. It would be helpful. I've tried to reproduce it but
> I don't see the difference in the generated code.
>
Never mind. I've reproduced it. Thanks.
next prev parent reply other threads:[~2017-04-11 17:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 15:05 Vladimir Makarov
2017-04-11 7:30 ` Christophe Lyon
2017-04-11 15:42 ` Vladimir Makarov
2017-04-11 16:26 ` Christophe Lyon
2017-04-11 16:31 ` Ramana Radhakrishnan
2017-04-11 17:27 ` Vladimir Makarov [this message]
2017-04-11 19:43 ` Vladimir Makarov
2017-04-12 6:10 ` Christophe Lyon
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=caa19ec3-1b78-35c6-df33-c1bc6ed4df1a@redhat.com \
--to=vmakarov@redhat.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
/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).