public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/44942] Bug in argument passing of long double
Date: Thu, 15 Jul 2010 12:03:00 -0000 [thread overview]
Message-ID: <20100715120322.3686.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44942-19440@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from jakub at gcc dot gnu dot org 2010-07-15 12:03 -------
Created an attachment (id=21209)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=21209&action=view)
gcc46-pr44942.patch
Untested fix. Grep tells me that cum->words is only ever used for x86-64
va_start expansion (and only for non-ms ABI), so I hope this patch doesn't
affect anything but __builtin_va_start in functions where at least one of the
arguments passed on the stack had to be padded.
--
jakub at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |jakub at gcc dot gnu dot org
|dot org |
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44942
next prev parent reply other threads:[~2010-07-15 12:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 2:39 [Bug c/44942] New: " pdox at alum dot mit dot edu
2010-07-15 8:06 ` [Bug target/44942] " rguenth at gcc dot gnu dot org
2010-07-15 9:50 ` jakub at gcc dot gnu dot org
2010-07-15 12:03 ` jakub at gcc dot gnu dot org [this message]
2010-07-16 9:06 ` jakub at gcc dot gnu dot org
2010-07-16 10:35 ` jakub at gcc dot gnu dot org
2010-07-22 6:42 ` jakub at gcc dot gnu dot org
2010-07-22 6:46 ` jakub at gcc dot gnu dot org
2010-07-22 6:49 ` jakub at gcc dot gnu dot org
2010-08-06 23:23 ` ebotcazou at gcc dot gnu dot org
2010-08-06 23:23 ` ebotcazou at gcc dot gnu dot org
2010-08-06 23:23 ` ebotcazou at gcc dot gnu 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=20100715120322.3686.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).