public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kazuhiro dot inaoka dot ud at renesas dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45000] RX signed extened unsigned char or short return value.
Date: Wed, 28 Jul 2010 07:19:00 -0000	[thread overview]
Message-ID: <20100728071939.24078.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45000-19023@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from kazuhiro dot inaoka dot ud at renesas dot com  2010-07-28 07:19 -------
(In reply to comment #1)
Hi Nick

Thank you for your reply.

Your example is OK. 
But I'm not clear.

> extension being performed.  Eg:
>  int bar (int a) { return a < func(); }
If the func() is external function, output code is the following.
_bar:
 push.l r7
 mov.L  r1, r7
 bsr    _func
 mouv.B r1, r1
 cmp    r7, r1
 scgt.L r1
 rtsd   #4, r7-r7

If the return value is zero exteneded,
"movu.B r1, r1" code can be removed.

Is the explanation san integer conversion rank?
> PS. See section 6.3.1.1 of the ISO C99 standard for more information about this
> behaviour

I think that my request is depend on rx cpu target like sh, m32r not m32c. 


-- 


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


  parent reply	other threads:[~2010-07-28  7:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-20  9:07 [Bug target/45000] New: " kazuhiro dot inaoka dot ud at renesas dot com
2010-07-22  9:43 ` [Bug target/45000] " nickc at redhat dot com
2010-07-28  7:19 ` kazuhiro dot inaoka dot ud at renesas dot com [this message]
2010-07-28 13:55 ` nickc at redhat dot com
2010-07-28 14:05 ` nickc at redhat dot com
2010-08-03  9:33 ` kazuhiro dot inaoka dot ud at renesas 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=20100728071939.24078.qmail@sourceware.org \
    --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).