public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/60870] go interface methods broken on ppc64le (bug296.go)
Date: Thu, 17 Apr 2014 19:28:00 -0000	[thread overview]
Message-ID: <bug-60870-4-yL25TSdUJm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60870-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60870

--- Comment #6 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Thu Apr 17 19:27:22 2014
New Revision: 209494

URL: http://gcc.gnu.org/viewcvs?rev=209494&root=gcc&view=rev
Log:
    PR go/60870

compiler: Don't convert function type for an interface method.

For an interface method the function type is the type without
the receiver, which is wrong since we are passing a receiver.
The interface method will always have the correct type in this
case, so no type conversion is necessary.

Also don't do the type conversion when calling a named
function, since in that case the type is also always correct.

The type can be wrong, and the conversion required, when the
function type refers to itself recursively.

Modified:
    trunk/gcc/go/gofrontend/expressions.cc


  parent reply	other threads:[~2014-04-17 19:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17  5:27 [Bug go/60870] New: " anton at samba dot org
2014-04-17 10:42 ` [Bug go/60870] " uweigand at gcc dot gnu.org
2014-04-17 16:37 ` ian at airs dot com
2014-04-17 16:38 ` ian at airs dot com
2014-04-17 19:04 ` uweigand at gcc dot gnu.org
2014-04-17 19:28 ` ian at gcc dot gnu.org [this message]
2014-04-17 19:28 ` ian at airs dot com

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=bug-60870-4-yL25TSdUJm@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).