From: Alan Lawrence <alan.lawrence@arm.com>
To: Richard Biener <rguenther@suse.de>
Cc: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
Richard Biener <richard.guenther@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>
Subject: Re: New regression on ARM Linux
Date: Tue, 31 Mar 2015 10:47:00 -0000 [thread overview]
Message-ID: <551A7B49.7070108@arm.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1503311229310.31545@zhemvz.fhfr.qr>
Richard Biener wrote:
>
> But I find it odd that on ARM passing *((aligned_int *)p) as
> vararg (only as varargs?) changes calling conventions independent
> of the functions type signature.
Does it? Do you have a testcase, and compilation flags, that'll make this show
up in an RTL dump? I've tried numerous cases, including AFAICT yours, and I
always get the value being passed in the expected ("unaligned") register?
Cheers, Alan
next prev parent reply other threads:[~2015-03-31 10:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 15:09 [PATCH] Fix regression caused by PR65310 fix Richard Biener
2015-03-30 12:15 ` New regression on ARM Linux (was: Re: [PATCH] Fix regression caused by PR65310 fix) Alan Lawrence
2015-03-30 12:18 ` New regression on ARM Linux Alan Lawrence
2015-03-30 13:01 ` Richard Biener
2015-03-30 13:16 ` Richard Biener
2015-03-30 16:45 ` Alan Lawrence
2015-03-30 20:13 ` Richard Biener
2015-03-31 7:50 ` Richard Biener
2015-03-31 9:43 ` Richard Earnshaw
2015-03-31 10:00 ` Richard Biener
2015-03-31 10:10 ` Richard Earnshaw
2015-03-31 10:32 ` Jakub Jelinek
2015-03-31 10:36 ` Richard Biener
2015-03-31 10:40 ` Richard Earnshaw
2015-03-31 10:45 ` Richard Biener
2015-03-31 10:51 ` Richard Earnshaw
2015-03-31 11:09 ` Richard Biener
2015-03-31 12:15 ` Richard Earnshaw
2015-03-31 12:11 ` Alan Lawrence
2015-03-31 10:47 ` Alan Lawrence [this message]
2015-03-31 11:05 ` Richard Biener
2015-03-31 11:07 ` Jakub Jelinek
2015-03-31 11:11 ` Richard Biener
2015-03-31 13:11 ` Alan Lawrence
2015-03-31 13:25 ` Richard Biener
2015-04-02 14:59 ` Alan Lawrence
2015-03-31 10:20 ` Richard Biener
2015-03-31 10:31 ` Richard Earnshaw
2015-03-31 10:45 ` Richard Biener
2015-03-31 10:53 ` Richard Earnshaw
2015-03-31 9:50 ` Alan Lawrence
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=551A7B49.7070108@arm.com \
--to=alan.lawrence@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
--cc=richard.guenther@gmail.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).