From: "H.J. Lu" <hjl.tools@gmail.com>
To: Mike Stump <mikestump@comcast.net>
Cc: gcc-patches@gcc.gnu.org, Uros Bizjak <ubizjak@gmail.com>,
ro@cebitec.uni-bielefeld.de
Subject: Re: PATCH: Support -mx32 in GCC tests
Date: Thu, 07 Jul 2011 21:32:00 -0000 [thread overview]
Message-ID: <CAMe9rOq4oJDUdwSFD28HX=kg8qS8oUPijL0+=PDpVosYbazH=w@mail.gmail.com> (raw)
In-Reply-To: <CAMe9rOpfTj_ji+Wp+cb4L185bY_=-qcOoZh311q9SAk_920KuQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Thu, Jul 7, 2011 at 1:57 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
> On Thu, Jul 7, 2011 at 1:56 PM, H.J. Lu <hjl.tools@gmail.com> wrote:
>
>>
>>>> -/* { dg-do compile { target { { { ! mips64 } && { ! ia64-*-* } } && { ! spu-*-* } } } } */
>>>> +/* { dg-do compile { target { { { { ! mips64 } && { ! ia64-*-* } } && { ! spu-*-* } } && { ! x32 } } } } */
>>>
>>>
>>> Hum, I worry about x86 walking away with large amounts of symbol space. Please change to x86 && x32 or x86_x32.
>>
>> gcc.dg/lower-subreg-1.c tests long long using on ilp32 targets. It
>> should be skipped on x32 similar to ia64, spu and mips. I don''t
>> know how x86 && x32 or x86_x32 will help here.
>>
>>>> -/* { dg-do compile } */
>>>> +/* { dg-do compile { target { x32 || lp64 } } } */
>>>
>>> Likewise.
>>
>> gcc.dg/pr44194-1.c is tested if a target returns structures in register.
>> Can you tell me how I can enable it for x32?
>>
>
> I will fix them.
Here is the updated patch. I will wait for Uros's comments.
Thanks.
--
H.J.
[-- Attachment #2: gcc-x32-test-2.patch.cl --]
[-- Type: application/simple-filter+xml, Size: 16292 bytes --]
next prev parent reply other threads:[~2011-07-07 21:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 17:38 H.J. Lu
2011-07-07 18:07 ` Mike Stump
2011-07-07 18:33 ` H.J. Lu
2011-07-07 20:33 ` Mike Stump
2011-07-07 20:58 ` H.J. Lu
2011-07-07 21:12 ` H.J. Lu
2011-07-07 21:32 ` H.J. Lu [this message]
2011-07-07 22:20 ` Mike Stump
2011-07-07 22:26 ` H.J. Lu
2011-07-07 23:04 ` Mike Stump
2011-07-08 0:17 ` H.J. Lu
2011-07-08 9:21 ` Uros Bizjak
2011-07-10 9:34 ` PATCH: Check ia32 " H.J. Lu
2011-07-10 10:02 ` H.J. Lu
2011-07-11 7:49 ` Mike Stump
2011-07-11 7:48 ` Mike Stump
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='CAMe9rOq4oJDUdwSFD28HX=kg8qS8oUPijL0+=PDpVosYbazH=w@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=ro@cebitec.uni-bielefeld.de \
--cc=ubizjak@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).