From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6057 invoked by alias); 23 Apr 2012 17:04:57 -0000 Received: (qmail 6045 invoked by uid 22791); 23 Apr 2012 17:04:56 -0000 X-SWARE-Spam-Status: No, hits=-5.2 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,TW_ZJ,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail-gy0-f175.google.com (HELO mail-gy0-f175.google.com) (209.85.160.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 23 Apr 2012 17:04:36 +0000 Received: by ghbz2 with SMTP id z2so6760692ghb.20 for ; Mon, 23 Apr 2012 10:04:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-system-of-record :x-gm-message-state; bh=PkjvSSopfpmb+l5JcgJB4T3JjGBsUQjVgeXCcPN2zQA=; b=piAmOLiCw8Zq9rAV8SUzctjm+iIQ9v5+zUg0ACHsgnIn1yT2zGaQ0i9VwCfev6rp5r GGcbELQD7LkAKrXAWNgFBktc4djsJUFKhEsbmmd5C+qzLRga89QnXCAqrhllWK8GbaXP Di+pcEZKT/tG9KM0xt1wg8mtUFmQQtV98r3n/+bg7tIbtTV+sHKKCYs0wbyYTHB3LDFN 7RFBTCL95L/MEOldyeo3qKcJsV3y/Ns4b0/3PdCKgnhILYWMeEm+d4jWGyJurii1ZNif 9ewZQBgJfWW5PF4TV3OZR0qnizv1MkSkL6gafg+IH+fEJDZ39FBklU91NQADLz10z1MH qJBQ== Received: by 10.182.154.5 with SMTP id vk5mr2916873obb.60.1335200676095; Mon, 23 Apr 2012 10:04:36 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.154.5 with SMTP id vk5mr2916839obb.60.1335200675955; Mon, 23 Apr 2012 10:04:35 -0700 (PDT) Received: by 10.182.147.104 with HTTP; Mon, 23 Apr 2012 10:04:35 -0700 (PDT) In-Reply-To: References: <20120330001021.9E30EB2086@azwildcat.mtv.corp.google.com> Date: Mon, 23 Apr 2012 17:04:00 -0000 Message-ID: Subject: Re: Support for Runtime CPU type detection via builtins (issue5754058) From: Sriraman Tallam To: Uros Bizjak Cc: Richard Guenther , Michael Matz , reply@codereview.appspotmail.com, gcc-patches@gcc.gnu.org, Richard Henderson , Jan Hubicka Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-System-Of-Record: true X-Gm-Message-State: ALoCoQm26WjrRnL22ks9bLEiIhLeQEcwCDvmgO4S9nT8ET2NZQo56wD3lE4CFtkhl2TscGlw3s/fowDmZac1xM8vfDqfVZa69tPPBVH4gXwFrZrLJw1TVBxxV5iE5JUJ3dpBCsHTVjdQ3EwHL45MvyiPI8l7EuJZrg== X-IsSubscribed: yes Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org X-SW-Source: 2012-04/txt/msg01399.txt.bz2 On Mon, Apr 23, 2012 at 1:19 AM, Uros Bizjak wrote: > On Tue, Apr 3, 2012 at 9:47 PM, Sriraman Tallam wro= te: > >> i386 maintainers - =A0Is this patch ok? > > Has the community reached the consensus on how this kind of > functionality has to be implemented? I have followed the discussion a > bit, but IIRC, there was no clear decision. Without this decision, I > am not able to review the _implementation_ of agreed functionality for > x86 target. > > (I apologize if I have missed the decision, please point me to the > discussion in this case.) Also, Richard's ok on just using 2 builtins: __builtin_cpu_is and __builtin_cpu_supports http://gcc.gnu.org/ml/gcc-patches/2012-03/msg00752.html > >>>>> Patch available for review here: >>>>> http://codereview.appspot.com/5754058 > > Please attach patches or inline it in the message itself for a review. > Please see [1] for further instructions. > > [1] http://gcc.gnu.org/contribute.html#patches > > Uros.