From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23081 invoked by alias); 22 Jul 2010 20:25:44 -0000 Received: (qmail 23072 invoked by uid 22791); 22 Jul 2010 20:25:43 -0000 X-SWARE-Spam-Status: No, hits=-1.9 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from mail-yx0-f175.google.com (HELO mail-yx0-f175.google.com) (209.85.213.175) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 22 Jul 2010 20:25:39 +0000 Received: by yxi11 with SMTP id 11so3129644yxi.20 for ; Thu, 22 Jul 2010 13:25:37 -0700 (PDT) MIME-Version: 1.0 Received: by 10.150.63.16 with SMTP id l16mr4864458yba.153.1279830337447; Thu, 22 Jul 2010 13:25:37 -0700 (PDT) Received: by 10.229.190.137 with HTTP; Thu, 22 Jul 2010 13:25:35 -0700 (PDT) In-Reply-To: <4C48A4B5.2090708@redhat.com> References: <4C486B20.6070404@redhat.com> <4C486C44.20507@redhat.com> <4C48A4B5.2090708@redhat.com> Date: Thu, 22 Jul 2010 20:25:00 -0000 Message-ID: Subject: Re: [patch win32]: fix for PR target/41943 From: NightStrike To: Richard Henderson Cc: Ozkan Sezer , Richard Guenther , Kai Tietz , Danny Smith , Dave Korn , gcc-patches@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: 2010-07/txt/msg01781.txt.bz2 On Thu, Jul 22, 2010 at 4:06 PM, Richard Henderson wrote: > On 07/22/2010 12:36 PM, NightStrike wrote: >> On Thu, Jul 22, 2010 at 12:05 PM, Richard Henderson wro= te: >>> On 07/22/2010 09:02 AM, Ozkan Sezer wrote: >>>>> We're not going to do that either. =A0The include order for all gcc is >>>>> gcc-private > fixincludes > system. >>>>> >>>> >>>> That patch doesn't change the order unconditionally. Why is a >>>> target option is unacceptable? >>> >>> Because I think it's conceptually flawed. >> >> Isn't it conceptually flawed to have a fixinclude header system that >> is broken for a target platform? > > Not conceptually, no. =A0That's a mere bug. Then can we fix gcc's headers to work with Win64?