From: Alan Lawrence <alan.lawrence@arm.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@foss.arm.com>
Cc: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/2][ARM] PR/65956 AAPCS update for alignment attribute
Date: Mon, 06 Jul 2015 16:38:00 -0000 [thread overview]
Message-ID: <559AAF0B.7080405@arm.com> (raw)
In-Reply-To: <559A8F51.80407@foss.arm.com>
Trying to push these now (svn!), patch 2 is going first.
I realize my second iteration of patch 1/2, dropped the testcases from the first
version. Okay to include those as per
https://gcc.gnu.org/ml/gcc-patches/2015-07/msg00215.html ?
Cheers, Alan
Ramana Radhakrishnan wrote:
>
> On 06/07/15 12:00, Alan Lawrence wrote:
>> Eric Botcazou wrote:
>>>> Technically this is incorrect since AGGREGATE_TYPE_P includes ARRAY_TYPE
>>>> and ARRAY_TYPE doesn't have TYPE_FIELDS. I doubt we could reach that
>>>> case though (unless there's a language that allows passing arrays by value).
>>> Ada passes small array types by the method specified by the pass_by_reference hook (and large array types by reference).
>> Ok, thanks. Here's a revised patch that handles array types. Again I've tested on both trunk (bootstrap + check-gcc) and gcc-5-branch (profiledbootstrap now succeeding + check-gcc). Jakub's pr65956.c testcase also now passes.
>>
>
>> The new code lacks a testcase; from what Eric says, it's possible we can write one using Ada, but I don't know any Ada myself, so I think any testcase should follow in a separate patch.
>>
>> Neither have I managed to run a check-ada yet, as I don't presently have a working Ada compiler with which to bootstrap gcc's Ada frontend. Working on this now.
>
> This is OK, the ada testing can go in parallel and we should take this in to not delay rc1 any further.
>
>
>
> regards
> Ramana
>
>> --Alan
>>
>> gcc/ChangeLog:
>>
>> * config/arm/arm.c (arm_needs_doubleword_align) : Drop any outer
>> alignment attribute, exploring one level down for records and arrays.
>
next prev parent reply other threads:[~2015-07-06 16:38 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-03 15:24 [PATCH 0/2][trunk+5 backport][ARM] PR/65956 Implement AAPCS updates " Alan Lawrence
2015-07-03 15:26 ` [PATCH 1/2][ARM] PR/65956 AAPCS update " Alan Lawrence
2015-07-03 16:11 ` Richard Earnshaw
2015-07-03 18:24 ` Richard Biener
2015-07-03 20:43 ` Richard Earnshaw
2015-07-04 10:57 ` Richard Biener
2015-07-04 11:13 ` Jakub Jelinek
2015-07-06 10:01 ` Alan Lawrence
2015-07-05 13:24 ` Eric Botcazou
2015-07-06 11:00 ` Alan Lawrence
2015-07-06 14:23 ` Ramana Radhakrishnan
2015-07-06 16:38 ` Alan Lawrence [this message]
2015-07-06 16:40 ` Ramana Radhakrishnan
2015-07-06 16:45 ` Alan Lawrence
2015-11-04 13:14 ` Jakub Jelinek
2015-11-04 21:30 ` Florian Weimer
2015-11-06 16:48 ` Alan Lawrence
2015-11-06 17:00 ` Jakub Jelinek
2015-11-26 14:05 ` Alan Lawrence
2015-11-27 13:45 ` Alan Lawrence
2015-11-27 18:17 ` Eric Botcazou
2015-11-30 19:40 ` Florian Weimer
2015-07-07 10:29 ` Alan Lawrence
2015-07-03 17:27 ` Jakub Jelinek
2015-07-03 15:27 ` [PATCH 2/2][ARM] fix movdi expander to avoid illegal ldrd/strd Alan Lawrence
2015-07-03 16:16 ` Richard Earnshaw
2015-07-06 17:40 ` Alan Lawrence
2015-07-03 17:12 ` [PATCH 0/2][trunk+5 backport][ARM] PR/65956 Implement AAPCS updates for alignment attribute 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=559AAF0B.7080405@arm.com \
--to=alan.lawrence@arm.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=ramana.radhakrishnan@foss.arm.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).