public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Sebastian Pop <sebpop@gmail.com>,
	Richard Henderson <rth@redhat.com>,
	  gcc-patches@gcc.gnu.org
Subject: Re: PATCH: Add LWP support for upcoming AMD Orochi processor.
Date: Mon, 14 Dec 2009 20:52:00 -0000	[thread overview]
Message-ID: <4B269CC0.1090103@gmail.com> (raw)
In-Reply-To: <20091214195148.GU22813@hs20-bc2-1.build.redhat.com>

On 12/14/2009 08:51 PM, Jakub Jelinek wrote:
> On Mon, Dec 14, 2009 at 08:38:20PM +0100, Uros Bizjak wrote:
>    
>> Strangely, with attached patch, I got a couple of errors:
>>
>> In file included from
>> /home/uros/gcc-build/gcc/testsuite/g++/../../include/x86intrin.h:77:0,
>>                   from
>> /home/uros/gcc-svn/trunk/gcc/testsuite/g++.dg/other/i386-2.C:8:
>> <built-in>: In function 'void* __slwpcb()':
>> <built-in>:0:0: error: too few arguments to function 'void*
>> __builtin_ia32_slwpcb(void)'
>> /home/uros/gcc-build/gcc/testsuite/g++/../../include/lwpintrin.h:44:33:
>> error: at this point in file
>>      
> Here is a fix for that.  Committing as obvious...
>    

Thanks, works for me.

I have committed my testsuite patch with following changelog:

2009-12-14  Uros Bizjak <ubizjak@gmail.com>

     * g++.dg/other/i386-2.C: Add -mpopcnt -mabm -mlwp to dg-options.
     * g++.dg/other/i386-3.C: Ditto.
     * g++.dg/other/i386-5.C: Remove duplicated test.
     * g++.dg/other/i386-6.C: Ditto.

Patch was tested on x86_64-pc-linux-gnu {,-m32}.

Uros.

  reply	other threads:[~2009-12-14 20:15 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09  1:13 Harsha Jagasia
2009-10-09 10:07 ` Jakub Jelinek
2009-10-22 21:07   ` rajagopal, dwarak
2009-11-05  9:32 ` Jakub Jelinek
2009-11-05 16:21   ` Jakub Jelinek
2009-11-05 16:58     ` Sebastian Pop
2009-11-05 17:03       ` Richard Guenther
2009-11-05 17:21       ` Uros Bizjak
2009-11-06 10:15     ` Jakub Jelinek
2009-12-10 19:58       ` Sebastian Pop
2009-12-10 21:01         ` Jakub Jelinek
2009-12-10 21:04           ` Sebastian Pop
2009-12-10 21:52             ` Jakub Jelinek
2009-12-11 14:51               ` Jakub Jelinek
2009-12-11 16:54                 ` Richard Henderson
2009-12-11 21:00                 ` Sebastian Pop
2009-12-11 21:43                   ` Jakub Jelinek
2009-12-11 22:27                     ` Sebastian Pop
2009-12-12  9:27                       ` Sebastian Pop
2009-12-14 16:35                         ` Richard Henderson
2009-12-14 19:15                         ` H.J. Lu
2009-12-14 19:21                           ` Jakub Jelinek
2009-12-14 19:38                             ` Richard Henderson
2009-12-14 20:15                               ` Jakub Jelinek
2009-12-14 20:14                         ` Uros Bizjak
2009-12-14 20:38                           ` Jakub Jelinek
2009-12-14 20:52                             ` Uros Bizjak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-10-09  2:12 Ross Ridge
2009-10-01  7:51 Uros Bizjak
2009-10-01 10:09 ` Jan Hubicka
2009-10-01  4:06 Harsha Jagasia
2009-10-01  6:30 ` Jakub Jelinek

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=4B269CC0.1090103@gmail.com \
    --to=ubizjak@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=rth@redhat.com \
    --cc=sebpop@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).