public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Tobler <andreast-list@fgznet.ch>
To: Andrew Haley <aph@redhat.com>, Richard Guenther <rguenther@suse.de>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	        Java Patches <java-patches@gcc.gnu.org>,
	        Eric Christopher <echristo@apple.com>,
	Michael Matz <matz@suse.de>
Subject: Re: [patch] libffi darwin x86-32bit, fix return_sc testcase.
Date: Fri, 04 Jan 2008 22:31:00 -0000	[thread overview]
Message-ID: <477EB3AD.8070702@fgznet.ch> (raw)
In-Reply-To: <18300.46176.896671.145271@zebedee.pink>

Andrew Haley wrote:
> Richard Guenther writes:
> 
>  > We obviously disagree about what the ABI specifies.  r126480 made
>  > the C/C++ frontend behavior the same as other frontends behavior
>  > (for example Fortran behavior, which I explicitly checked).  As GCC
>  > supports both promoting function return values or not in the
>  > backends and the x86 backend explicitly does _not_ enable this
>  > promotion it agrees with my reading of the ABI.
> 
> But the ABI isn't in doubt: it is required to 
> 
>> Functions pass all integer-valued arguments as words, expanding or
>> padding signed or unsigned bytes and halfwords as needed'
> 
> and this surely applies to return values as well as arguments passed
> to functions.  It is utterly perverse to assume that return values are
> treated differently from arguments passed to functions.  So if the
> back end isn't promoting return values then the back end is wrong.

I'm not in the position to judge about this, I can only read the ABI and 
I have to give my vote to aph, at least from what _I_ understand.
Maybe my understanding lacks some basic issues, in this case I'd like to 
be advised to understand it right. But until then, I suppose this patch 
is hold on ice, right?
This blocks my further work and I fear this issue might take some moons 
to be resolved/clarified.

Who has the ability to clarify this issue? Do we need to expand the 
to/cc list to the _right_ people? Who are the right people?

I'd like to have this clarified, even if I can't help that much in 
clarifying....

Thanks,
Andreas

  reply	other threads:[~2008-01-04 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-02 21:47 Andreas Tobler
2008-01-03  9:52 ` Andrew Haley
2008-01-03 10:05   ` Richard Guenther
2008-01-03 10:13     ` Andrew Haley
2008-01-04 22:31       ` Andreas Tobler [this message]
2008-01-05 10:46         ` Andrew Haley
2008-01-06 12:17           ` Andreas Tobler

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=477EB3AD.8070702@fgznet.ch \
    --to=andreast-list@fgznet.ch \
    --cc=aph@redhat.com \
    --cc=echristo@apple.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=java-patches@gcc.gnu.org \
    --cc=matz@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).