public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Fix PR80334
Date: Fri, 07 Apr 2017 08:21:00 -0000	[thread overview]
Message-ID: <yddtw60tyq5.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <alpine.LSU.2.20.1704070848140.30715@zhemvz.fhfr.qr> (Richard	Biener's message of "Fri, 7 Apr 2017 08:49:05 +0200 (CEST)")

Hi Richard,

> On Thu, 6 Apr 2017, Rainer Orth wrote:
>
>> Hi Richard,
>> 
>> > The following patch makes sure to preserve (mis-)alignment of memory
>> > references when IVOPTs generates TARGET_MEM_REFs for them.
>> >
>> > Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
>> >
>> > Richard.
>> >
>> > 2017-04-06  Richard Biener  <rguenther@suse.de>
>> >
>> > 	PR tree-optimization/80334
>> > 	* tree-ssa-loop-ivopts.c (rewrite_use_address): Properly
>> > 	preserve alignment of accesses.
>> >
>> > 	* g++.dg/torture/pr80334.C: New testcase.
>> 
>> the new testcase FAILs on 32-bit Solaris/SPARC:
>> 
>> +FAIL: g++.dg/torture/pr80334.C   -O0  (test for excess errors)
>> +FAIL: g++.dg/torture/pr80334.C   -O1  (test for excess errors)
>> +FAIL: g++.dg/torture/pr80334.C   -O2  (test for excess errors)
>> +FAIL: g++.dg/torture/pr80334.C   -O2 -flto  (test for excess errors)
>> +FAIL: g++.dg/torture/pr80334.C -O2 -flto -flto-partition=none (test for
>> exce
>> ss errors)
>> +FAIL: g++.dg/torture/pr80334.C -O3 -fomit-frame-pointer -funroll-loops
>> -fpeel
>> -loops -ftracer -finline-functions  (test for excess errors)
>> +FAIL: g++.dg/torture/pr80334.C   -O3 -g  (test for excess errors)
>> +FAIL: g++.dg/torture/pr80334.C   -Os  (test for excess errors)
>> 
>> Excess errors:
>> /vol/gcc/src/hg/trunk/local/gcc/testsuite/g++.dg/torture/pr80334.C:11:20:
>> warning: requested alignment 16 is larger than 8 [-Wattributes]
>
> Any suggestion how to mitigate that?  Possible solution includes
> adding { target { ! ... } } to dg-do run.

No idea.  However, according to gcc-testresults there are other
failures: s390-ibm-inux-gnu and s390x-ibm-linux-gnu so far.

This might argue against just excluding a random list of failing targets.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  reply	other threads:[~2017-04-07  8:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06 12:40 Richard Biener
2017-04-06 20:45 ` Rainer Orth
2017-04-07  6:49   ` Richard Biener
2017-04-07  8:21     ` Rainer Orth [this message]
2017-04-07  8:33       ` Richard Biener
2017-04-07  8:41         ` Rainer Orth
2017-04-07  8:45           ` Richard Biener

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=yddtw60tyq5.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rguenther@suse.de \
    /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).