public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cort at fsmlabs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/19417] New: return value of some functions not properly set (in r3)
Date: Wed, 12 Jan 2005 23:46:00 -0000	[thread overview]
Message-ID: <20050112234624.19417.cort@fsmlabs.com> (raw)

I have included 2 .i and .s files.  One correctly sets the return value (r3) and
one does not.  The addition of the nonleaf() call causes the return value to be
set properly.  If you search the .s files for "cort start return" "cort end
return" you can see it.

It seems that the return value isn't set properly if the function does not call
another function at the out: label.

I'm cross compiling from a 32-bit x86 to a 32-bit PowerPC (of the 6xx/74xx variety).

-- 
           Summary: return value of some functions not properly set (in r3)
           Product: gcc
           Version: 3.3.2
            Status: UNCONFIRMED
          Severity: critical
          Priority: P1
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: cort at fsmlabs dot com
                CC: gcc-bugs at gcc dot gnu dot org
  GCC host triplet: i386-linux
GCC target triplet: ppc-linux


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


             reply	other threads:[~2005-01-12 23:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 23:46 cort at fsmlabs dot com [this message]
2005-01-12 23:48 ` [Bug c/19417] " cort at fsmlabs dot com
2005-01-12 23:48 ` cort at fsmlabs dot com
2005-01-12 23:49 ` cort at fsmlabs dot com
2005-01-12 23:49 ` cort at fsmlabs dot com
2005-01-12 23:51 ` cort at fsmlabs dot com
2005-01-13  0:02 ` pinskia at gcc dot gnu dot org
2005-01-13  0:38 ` [Bug middle-end/19417] " pinskia at gcc dot gnu dot org
2005-01-13  0:44 ` pinskia at gcc dot gnu dot org
2005-01-14 23:24 ` [Bug middle-end/19417] [3.3 only] " pinskia at gcc dot gnu dot org
2005-01-15  0:40 ` dje at gcc dot gnu dot org

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=20050112234624.19417.cort@fsmlabs.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).