public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl at lucon dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/34001] Incorrect __attribute__ fastcall behavior Date: Fri, 09 Nov 2007 16:55:00 -0000 [thread overview] Message-ID: <20071109165509.4014.qmail@sourceware.org> (raw) In-Reply-To: <bug-34001-15308@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from hjl at lucon dot org 2007-11-09 16:55 ------- From http://msdn2.microsoft.com/en-us/library/6xa169sk(VS.80).aspx "The first two DWORD or smaller arguments are passed in ECX and EDX registers; all other arguments are passed right to left." But it isn't clear if it applies to structure/union. We tested all MS compilers we have and verified that the above doesn't apply to structure/union. To make fastcall compatible with MS compilers, we should only put scalar arguments in ECX and EDX. -- hjl at lucon dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |hjl at lucon dot org |dot org | Status|NEW |ASSIGNED Last reconfirmed|2007-11-08 17:12:05 |2007-11-09 16:55:09 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34001
next prev parent reply other threads:[~2007-11-09 16:55 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-05 23:40 [Bug c/34001] New: " zia at aracnet dot com 2007-11-05 23:58 ` [Bug target/34001] " pinskia at gcc dot gnu dot org 2007-11-08 17:12 ` hjl at lucon dot org 2007-11-09 16:55 ` hjl at lucon dot org [this message] 2007-11-09 17:34 ` hjl at lucon dot org 2007-11-12 3:27 ` [Bug target/34001] Incorrect x86 " hjl at lucon dot org 2007-11-16 4:52 ` hjl at lucon dot org 2007-11-26 23:19 ` hjl at lucon dot org 2007-11-27 2:36 ` hjl at lucon dot org 2007-11-28 1:20 ` hjl at gcc dot gnu dot org 2007-11-28 1:25 ` hjl at lucon 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=20071109165509.4014.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: linkBe 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).