public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hpenner at de dot ibm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/14960] -maltivec affects vector return with -mabi=no-altivec
Date: Mon, 19 Apr 2004 11:39:00 -0000	[thread overview]
Message-ID: <20040419092535.22479.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040414231341.14960.janis187@us.ibm.com>


------- Additional Comments From hpenner at de dot ibm dot com  2004-04-19 09:25 -------
Yes, this is a bug. Looks to me, that rs6000_function_arg has a wrong check.
I think, we should check for TARGET_ALTIVEC_ABI instead of TARGET_ALTIVEC,
when we decide how to pass return value.


Index: rs6000.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/config/rs6000/rs6000.c,v
retrieving revision 1.397.2.35
diff -u -p -r1.397.2.35 rs6000.c
--- rs6000.c    30 Mar 2004 09:01:22 -0000      1.397.2.35
+++ rs6000.c    19 Apr 2004 09:21:52 -0000
@@ -16200,7 +16200,7 @@ rs6000_function_value (valtype, func)
           && TARGET_HARD_FLOAT
           && SPLIT_COMPLEX_ARGS)
     return rs6000_complex_function_value (mode);
-  else if (TREE_CODE (valtype) == VECTOR_TYPE && TARGET_ALTIVEC)
+  else if (TREE_CODE (valtype) == VECTOR_TYPE && TARGET_ALTIVEC_ABI)
     regno = ALTIVEC_ARG_RETURN;
   else
     regno = GP_ARG_RETURN;



-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aldyh at redhat dot com


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


  parent reply	other threads:[~2004-04-19  9:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 23:35 [Bug target/14960] New: " janis187 at us dot ibm dot com
2004-04-14 23:49 ` [Bug target/14960] " pinskia at gcc dot gnu dot org
2004-04-19 11:39 ` hpenner at de dot ibm dot com [this message]
2004-04-19 11:44 ` aldyh at redhat dot com
2004-04-22 22:06 ` janis187 at us dot ibm dot com
2004-04-24 10:32 ` cvs-commit at gcc dot gnu dot org
2004-04-28  7:20 ` cvs-commit at gcc dot gnu dot org
2004-06-05 20:33 ` mmitchel at gcc dot gnu dot org
2004-06-10  2:02 ` amodra at bigpond dot net dot au
2004-06-10  6:15 ` [Bug target/14960] [3.4 only] " cvs-commit at gcc dot gnu dot org
2004-06-10  6:40 ` amodra at bigpond dot net dot au

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=20040419092535.22479.qmail@sources.redhat.com \
    --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).