From: Eric Botcazou <ebotcazou@adacore.com>
To: Bernd Edlinger <bernd.edlinger@hotmail.de>
Cc: Richard Biener <rguenther@suse.de>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Jeff Law <law@redhat.com>, Jakub Jelinek <jakub@redhat.com>
Subject: Re: AW: [PATCH] Fix unaligned access when predictive commoning (PR 71083)
Date: Wed, 10 Aug 2016 12:19:00 -0000 [thread overview]
Message-ID: <113142642.78Fd9MK2D0@arcturus.home> (raw)
In-Reply-To: <AM4PR0701MB2162AF8FCA628D85B77F25C2E41D0@AM4PR0701MB2162.eurprd07.prod.outlook.com>
> I tried to translate the c-test case to an equivalent ada test case with
> my not-so-fluent Ada speak...
>
> So here is a test case that *actually* hits the if ((boff % BITS_PER_UNIT)
> != 0) code path.
I see, well done then.
> Before my patch there was an unaligned SImode access, and with
> the patch we have 3 QImode accesses here.
>
> cat pr71083_pkg.ads
> package Pr71083_pkg is
> type Nibble is mod 2**4;
> type Int24 is mod 2**24;
> type StructA is record
> a : Nibble;
> b : Int24;
> end record;
> pragma Pack(StructA);
> type StructB is record
> a : Nibble;
> b : StructA;
> end record;
> pragma Pack(StructB);
> type ArrayOfStructB is array(0..100) of StructB;
> procedure Foo (X : in out ArrayOfStructB);
> end Pr71083_pkg;
>
> cat pr71083_pkg.adb
> -- { dg-do compile }
> -- { dg-options "-O3" }
> package body Pr71083_pkg is
> procedure Foo (X : in out ArrayOfStructB) is
> begin
> for K in 0..99 loop
> X (K+1).b.b := X (K).b.b;
> end loop;
> end Foo;
> end Pr71083_pkg;
>
> cat pr71083.adb
> -- { dg-do run }
> -- { dg-options "-O3" }
> with Pr71083_pkg;
> use Pr71083_pkg;
> procedure Pr71083 is
> Test : ArrayOfStructB;
> begin
> Test (0).b.b := 9999;
> Foo (Test);
> if Test (100).b.b /= 9999 then
> raise Program_Error;
> end if;
> end;
>
>
> I was not sure which name to choose,
> so I used the same convention as in the c-torture.
> How do you like that?
Worst convention ever. :-) Either opt57 or loop_optimization23 at your
convenience (you can add a reference to the PR in a comment).
> I would like to add that to the gnat.dg because
> it seems that there is zero testing for the predictive
> commoning in the gnat.dg test suite.
Very likely so. The renamed testcase is OK for mainline, but please replace
"Eric's" with "the" in the patch or copy-and-paste the explanation.
--
Eric Botcazou
next prev parent reply other threads:[~2016-08-10 12:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 19:57 Bernd Edlinger
2016-08-09 7:29 ` Richard Biener
2016-08-09 17:31 ` Bernd Edlinger
2016-08-09 20:48 ` Eric Botcazou
2016-08-09 22:23 ` Bernd Edlinger
2016-08-10 8:47 ` AW: " Bernd Edlinger
2016-08-10 12:19 ` Eric Botcazou [this message]
2016-08-10 12:29 ` Richard Biener
2016-08-10 16:24 ` Bernd Edlinger
2016-08-11 7:07 ` Richard Biener
2016-08-11 10:09 ` Bernd Edlinger
2016-08-11 10:30 ` Richard Biener
2016-08-11 19:47 ` [PATCH] Increase alignment for bit-field " Bernd Edlinger
2016-08-12 7:13 ` 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=113142642.78Fd9MK2D0@arcturus.home \
--to=ebotcazou@adacore.com \
--cc=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--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).