From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23696 invoked by alias); 16 Mar 2010 20:53:40 -0000 Received: (qmail 23687 invoked by uid 22791); 16 Mar 2010 20:53:40 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from vsmtp14.tin.it (HELO vsmtp14.tin.it) (212.216.176.118) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 16 Mar 2010 20:53:35 +0000 Received: from [192.168.0.4] (79.33.222.108) by vsmtp14.tin.it (8.5.113) id 4B990FC2006F5B20; Tue, 16 Mar 2010 21:53:32 +0100 Message-ID: <4B9FEFCA.2060308@oracle.com> Date: Tue, 16 Mar 2010 20:58:00 -0000 From: Paolo Carlini User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.8) Gecko/20100228 SUSE/3.0.3-1.1.1 Thunderbird/3.0.3 MIME-Version: 1.0 To: "H.J. Lu" CC: "gcc@gcc.gnu.org" , Jason Merrill Subject: Re: Why is __i686 undefined for x86_64 -m32 (in mainline) References: <4B9FDCC1.2080201@oracle.com> <6dc9ffc81003161253g6f2ef24dv605118dbc7664aa1@mail.gmail.com> <4B9FE683.2080903@oracle.com> <6dc9ffc81003161340o721cd497w5a63fb6ff9c24b0e@mail.gmail.com> In-Reply-To: <6dc9ffc81003161340o721cd497w5a63fb6ff9c24b0e@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org X-SW-Source: 2010-03/txt/msg00199.txt.bz2 On 03/16/2010 09:40 PM, H.J. Lu wrote: > We never defined __i686 for -m32 by default on x86_64. Here is > a patch to define __i686 for -m32 if the processor supports it. > If I understand correctly the logic underlying the recent work in this area, I think we certainly want your patch, because otherwise we have kind of an inconsistent situation: the i686 facilites *are* available, but __i686 is undefined. Maybe the patch should go to gcc-patches to... Thanks, Paolo.