From: Kai Tietz <Kai.Tietz@onevision.com>
To: NightStrike <nightstrike@gmail.com>
Cc: "GCC Patches" <gcc-patches@gcc.gnu.org>, jh@suse.cz
Subject: Re: [patch]: pr33617 vector modes have to be passed via memory for x86_64-pc-mingw32
Date: Wed, 26 Mar 2008 17:22:00 -0000 [thread overview]
Message-ID: <OF5951AD45.AFA32F33-ONC1257418.0053E2CE-C1257418.00540B42@onevision.de> (raw)
In-Reply-To: <b609cb3b0803260811n37610eb8v19f1470c96733984@mail.gmail.com>
NightStrike <nightstrike@gmail.com> wrote on 26.03.2008 16:11:37:
> On 3/19/08, Kai Tietz <Kai.Tietz@onevision.com> wrote:
> > Hello,
> >
> > This bug was found by running testsuite gcc.c-torture for test
pr33617.c
> > for target x86_64-pc-mingw32. By ABI complex and vector types have to
be
> > returned via memory and passed as memory reference for functions. This
> > patch fixes the ICE happening.
> >
> > ChangeLog entries for gcc
> >
> > 2008-03-19 Kai Tietz <kai.tietz@onevision.com>
> >
> > * gcc/config/i386/i386.c (return_in_memory_ms_64): Vector and
> > block
> > types are passed via memory. (testsuite
> > gcc.c-torture/compile/pr33617.c).
> > (ix86_pass_by_reference): Check for complex and vector modes.
> >
> > Tested for x86_64-pc-mingw32 target. Other targets are not affected.
> > Is this patch OK for apply?
>
> Was this applied yet?
No, it out-dated. Please refer to
http://gcc.gnu.org/ml/gcc-patches/2008-03/msg01458.html
Cheers,
Kai
| (\_/) This is Bunny. Copy and paste Bunny
| (='.'=) into your signature to help him gain
| (")_(") world domination.
next prev parent reply other threads:[~2008-03-26 15:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 15:44 Kai Tietz
2008-03-26 17:11 ` NightStrike
2008-03-26 17:22 ` Kai Tietz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-16 12:16 Ping - old patch from April - mingw support for I32/I64 MS printf formatters to c-format.c Kai Tietz
2008-03-18 9:12 ` [patch]: pr33617 vector modes have to be passed via memory for x86_64-pc-mingw32 Kai Tietz
2008-03-18 9:54 ` Kai Tietz
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=OF5951AD45.AFA32F33-ONC1257418.0053E2CE-C1257418.00540B42@onevision.de \
--to=kai.tietz@onevision.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=nightstrike@gmail.com \
/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).