From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Richard Biener <rguenther@suse.de>,
gcc-patches@gcc.gnu.org, Martin Jambor <mjambor@suse.de>,
Alan Lawrence <alan.lawrence@arm.com>
Subject: Re: [PATCH] Fix eipa_sra AAPCS issue (PR target/65956)
Date: Tue, 05 May 2015 13:02:00 -0000 [thread overview]
Message-ID: <5548BF5B.9000904@foss.arm.com> (raw)
In-Reply-To: <20150505125431.GJ1751@tucnak.redhat.com>
On 05/05/15 13:54, Jakub Jelinek wrote:
> On Tue, May 05, 2015 at 01:49:55PM +0100, Richard Earnshaw wrote:
>> The real question here is why is TYPE the type of the value, rather than
>> the type of the formal as expressed by the prototype (or implicit
>> prototype in the case of variadics or K&R)? Surely this is the mid-end
>> passing the wrong information to the back-end.
>
> There is nothing else for unnamed arguments (K&R, stdarg).
> For named arguments, the backend has the option to save the fntype in
> CUMULATIVE_ARGS and look it up when it needs that. But, that will
> still mean K&R and stdarg will be just broken on arm.
>
> Jakub
>
In a literal sense, yes. However, even K&R & stdarg have standard
promotion and conversion rules (size < int => int, floats promoted to
double, etc). What are those rules for GCC's overaligned types (ie
where in the docs does it say what happens and how a back-end should
interpret them)? Shouldn't the mid-end be doing that work so as to
create a consistent view of the values passed into the back-end? It
seems to me that at present the back-end has to be psychic as to what is
really happening.
R.
next prev parent reply other threads:[~2015-05-05 13:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-02 8:24 Jakub Jelinek
2015-05-04 8:11 ` Richard Biener
2015-05-04 15:00 ` Jakub Jelinek
2015-05-05 7:32 ` Jakub Jelinek
2015-05-05 10:54 ` Richard Earnshaw
2015-05-05 11:02 ` Richard Earnshaw
2015-05-05 12:30 ` Jakub Jelinek
2015-05-05 12:37 ` Richard Biener
2015-05-05 12:45 ` Richard Earnshaw
2015-05-05 12:46 ` Richard Earnshaw
2015-05-05 12:50 ` Richard Earnshaw
2015-05-05 12:54 ` Jakub Jelinek
2015-05-05 13:02 ` Richard Earnshaw [this message]
2015-05-05 13:07 ` Jakub Jelinek
2015-05-05 13:20 ` Richard Earnshaw
2015-05-05 14:29 ` Jakub Jelinek
2015-05-05 14:33 ` Richard Earnshaw
2015-05-05 14:34 ` Richard Earnshaw
2015-05-05 18:07 ` Richard Biener
2015-05-06 14:04 ` Richard Earnshaw
2015-05-07 11:16 ` Alan Lawrence
2015-05-07 11:30 ` Jakub Jelinek
2015-06-01 12:08 ` Jakub Jelinek
2015-06-02 16:21 ` Richard Earnshaw
2015-06-02 16:51 ` Alan Lawrence
2015-05-05 14:06 ` Richard Biener
2015-05-05 14:22 ` Richard Earnshaw
2015-05-05 14:26 ` Jakub Jelinek
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=5548BF5B.9000904@foss.arm.com \
--to=richard.earnshaw@foss.arm.com \
--cc=alan.lawrence@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=mjambor@suse.de \
--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).