This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/52441] SH Target: Double sign/zero extensions for function arguments
- From: "olegendo at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 01 Mar 2012 22:13:23 +0000
- Subject: [Bug target/52441] SH Target: Double sign/zero extensions for function arguments
- Auto-submitted: auto-generated
- References: <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.