From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-patches-return-361742-listarch-gcc-patches=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 20380 invoked by alias); 13 Feb 2014 23:57:03 -0000
Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-patches.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-patches/>
List-Post: <mailto:gcc-patches@gcc.gnu.org>
List-Help: <mailto:gcc-patches-help@gcc.gnu.org>
Sender: gcc-patches-owner@gcc.gnu.org
Received: (qmail 20370 invoked by uid 89); 13 Feb 2014 23:57:02 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,BODY_URI_ONLY,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO: mail-ig0-f174.google.com
Received: from mail-ig0-f174.google.com (HELO mail-ig0-f174.google.com) (209.85.213.174) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES128-SHA encrypted) ESMTPS; Thu, 13 Feb 2014 23:57:01 +0000
Received: by mail-ig0-f174.google.com with SMTP id hl1so14035988igb.1        for <gcc-patches@gcc.gnu.org>; Thu, 13 Feb 2014 15:56:59 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20130820;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc:content-type;        bh=iCmDl8KOoGrZmwgsEEKFMqQUN9x3+A/mlyCjvsAs4sE=;        b=VGK8o//VLEW60YioK6KBsPJyOfX22BLdxPoEssQGGM4k6Byl1gnPJ5wGYH66ufDwSu         mSkeEofZpAbsGATnhUAp0VBfWaJorE3CmehlLLMxv8JQAuCrzRp8AQ0Atl1BO5PGlB9O         qbACsD2kJBl/ct3kNTJOc2o1WnlE1SspUqUEZxJq+PDRwJi+T6gfWg2V9739clJbhWoR         NZ9rHioGDxWSaZopuwNu/M3uTFcFktgoRu3u3810AAmlaM0g0eD5LQmXIYMIXza/E3qS         2mAEiccqb7tTQSKYVXFtGVo1oXvuiz1JchGhB109teDjgPujXJP2M7v80l26ejix1REY         2VRg==
X-Gm-Message-State: ALoCoQltANuSfycjljUVd4iotNl5mqikHxYqQisRhE2hcxvat4ji7wqIiYUgIMuJbZzxgewPNq+ZhOyNCCAnA4zou3LMaO9dhtj2kS/8x9aiOxU3rSAjwrGoDhgqbxGwk5dFtTzlh4e/Pg/j51mIBVaLLszp2Q+9pu+0HWa9cxfnd69yidntv+CFtHAsxqrruq2+IQKA01JZahHc5ilscYuuk352Ne21Fg==
X-Received: by 10.50.23.108 with SMTP id l12mr6412522igf.46.1392335819561; Thu, 13 Feb 2014 15:56:59 -0800 (PST)
MIME-Version: 1.0
Received: by 10.64.240.3 with HTTP; Thu, 13 Feb 2014 15:56:39 -0800 (PST)
In-Reply-To: <CA+=Sn1mU7C6Y+T65ArPidnP=WkB9moer1CmAQ2=p6g+TTrVTzg@mail.gmail.com>
References: <CAB=4xhrEQAf1ksLHfWZSabct4NF3HBxXUUBHuaYQ3dKGPZ315w@mail.gmail.com> <CA+=Sn1mzbw95+BBQp+iFG9k+H=v9VKUaYRGE+ie-4KjsgctZUg@mail.gmail.com> <CA+=Sn1mU7C6Y+T65ArPidnP=WkB9moer1CmAQ2=p6g+TTrVTzg@mail.gmail.com>
From: Roland McGrath <mcgrathr@google.com>
Date: Thu, 13 Feb 2014 23:57:00 -0000
Message-ID: <CAB=4xhrqVxTXepHrBAkupdp-5RvjZUfRiw-MThwqGt1x1dghaQ@mail.gmail.com>
Subject: Re: [PATCH] x86: Use ud2 assembly mnemonic when available.
To: Andrew Pinski <pinskia@gmail.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Content-Type: text/plain; charset=UTF-8
X-SW-Source: 2014-02/txt/msg00871.txt.bz2

Did you read the patch?  It uses an empirical configure check to
discover if the assembler does in fact support ud2.