public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/46942] x86_64 parameter passing unnecessary sign/zero extends
Date: Sun, 02 Jan 2011 17:58:00 -0000 [thread overview]
Message-ID: <bug-46942-4-rhEAiqIlNL@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46942-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46942
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |42324
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> 2011-01-02 17:58:18 UTC ---
I proposed to update x86-64 psABI with
---
When a value of type _Bool is returned in a register, bit 0 contains the truth
value and bits 1 to 7 shall be zero. When an argument of type _Bool is passed
in a register or on the stack, bit 0 contains the truth value and bits
1 to 31 shall be
zero.
When a value of type signed/unsigned char or short is returned in a register,
bits 0 to 7 for char and bits 0 to 15 for short contain the value and other
bits are left unspecified. When an argument of signed/unsigned type char or
short is passed in a register or on the stack, it shall be sign/zero extended
to
signed/unsigned int.
---
next prev parent reply other threads:[~2011-01-02 17:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 16:50 [Bug target/46942] New: " jakub at gcc dot gnu.org
2010-12-14 17:13 ` [Bug target/46942] " jakub at gcc dot gnu.org
2010-12-14 17:26 ` joseph at codesourcery dot com
2010-12-16 15:12 ` rguenth at gcc dot gnu.org
2011-01-02 17:58 ` hjl.tools at gmail dot com [this message]
2011-01-02 17:59 ` hjl.tools at gmail dot com
2011-01-02 19:02 ` jakub at gcc dot gnu.org
2011-01-02 20:53 ` hjl.tools at gmail dot com
2011-01-03 14:23 ` hjl.tools at gmail dot com
2011-03-25 20:06 ` jakub at gcc dot gnu.org
2011-04-28 16:38 ` rguenth at gcc dot gnu.org
2012-03-08 3:42 ` meadori at gmail 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=bug-46942-4-rhEAiqIlNL@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).