public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "olegendo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52441] SH Target: Double sign/zero extensions for function arguments
Date: Thu, 01 Mar 2012 22:14:00 -0000	[thread overview]
Message-ID: <bug-52441-4-YxuoYx70vz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52441-4@http.gcc.gnu.org/bugzilla/>

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

Oleg Endo <olegendo at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2012-03-01
         AssignedTo|unassigned at gcc dot       |olegendo at gcc dot gnu.org
                   |gnu.org                     |
     Ever Confirmed|0                           |1

--- Comment #2 from Oleg Endo <olegendo at gcc dot gnu.org> 2012-03-01 22:13:23 UTC ---
(In reply to comment #1)
> 
> I don't know any historical reason but x86 uses that double sign/zero
> extension too.  It wouldn't be a safe ABI change.  There can exist hand
> written functions depending that behavior.  It's too late to change
> the default behavior, I think.  Of course, you can add a new -m option
> or function attribute changing it, though it shouldn't be default for
> non Renesas ABI.

Right, thanks!  I haven't thought of the hand-written asm code scenario.  This
can turn into a funny problem indeed.

I'll go the option way, then.


  parent reply	other threads:[~2012-03-01 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 21:15 [Bug target/52441] New: " olegendo at gcc dot gnu.org
2012-03-01 22:00 ` [Bug target/52441] " kkojima at gcc dot gnu.org
2012-03-01 22:14 ` olegendo at gcc dot gnu.org [this message]
2024-03-28  4:50 ` pinskia at gcc dot gnu.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=bug-52441-4-YxuoYx70vz@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).