public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Alan Lawrence <alan.lawrence@arm.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>, gcc-patches@gcc.gnu.org
Cc: Jeff Law <law@redhat.com>, Bernd Schmidt <bschmidt@redhat.com>,
	Jason Merrill <jason@redhat.com>, Nathan Sidwell <nathan@acm.org>
Subject: Re: [PING^2][PATCH] Improve C++ loop's backward-jump location
Date: Wed, 02 Dec 2015 13:53:00 -0000	[thread overview]
Message-ID: <565EF7CF.2030605@arm.com> (raw)
In-Reply-To: <m3r3jfxx9d.fsf@oc1027705133.ibm.com>

On 24/11/15 14:55, Andreas Arnez wrote:
> Ping?
>
>    https://gcc.gnu.org/ml/gcc-patches/2015-11/msg01192.html
>
> I guess we want C and C++ behave the same here?
>
>> gcc/cp/ChangeLog:
>>
>> 	* cp-gimplify.c (genericize_cp_loop): Change LOOP_EXPR's location
>> 	to start of loop body instead of start of loop.
>>
>> gcc/testsuite/ChangeLog:
>>
>> 	* g++.dg/guality/pr67192.C: New test.
>
>
>

Since this, we've been seeing these tests fail natively on AArch64 and ARM:

FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++11  gcov: 3 failures in line counts, 0 in 
branch percentages, 0 in return percentages, 0 in intermediate format
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++11  line 115: is 27:should be 14
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++11  line 58: is 18:should be 9
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++11  line 73: is 162:should be 81
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++14  gcov: 3 failures in line counts, 0 in 
branch percentages, 0 in return percentages, 0 in intermediate format
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++14  line 115: is 27:should be 14
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++14  line 58: is 18:should be 9
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++14  line 73: is 162:should be 81
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++98  gcov: 3 failures in line counts, 0 in 
branch percentages, 0 in return percentages, 0 in intermediate format
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++98  line 115: is 27:should be 14
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++98  line 58: is 18:should be 9
FAIL: g++.dg/gcov/gcov-1.C  -std=gnu++98  line 73: is 162:should be 81

I've not had a chance to look any further yet.

Thanks, Alan

  parent reply	other threads:[~2015-12-02 13:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 14:58 Andreas Arnez
2015-11-25 22:12 ` Jason Merrill
2015-12-02 13:53 ` Alan Lawrence [this message]
2015-12-02 14:44   ` Andreas Arnez

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=565EF7CF.2030605@arm.com \
    --to=alan.lawrence@arm.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=bschmidt@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.com \
    --cc=law@redhat.com \
    --cc=nathan@acm.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).