X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f
X-Recipient: djgpp AT delorie DOT com
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=+CUFjC+ncn342TGevXYxDDuiKEbpFgIBUiye3EvXkWI=;
        b=YcuymWR9me569dAbZci6MPnPD9SxCzX5g3wAfwtQVNnYSO8DJ86ruHKu3PNnr4uzZD
         jMZu8WE/D23G2XJ8Qq0AbZHHiNxsKLvSviBQ7v1Rz/1X0I7bEv/UkbiyIapjA0/Uaov1
         WL1WZqRH5LpYzv2eC6ymXrt5KrN+epXS36U+lM0bYKmAIRohaCUn8EH0nQUy8/Rm/5an
         ZUFrfeZ7GMxobnYEfqSrq7SbZSMM/oM2rflPgytch3Il/aiGnx+6YKdo9bwSWeyhIJ+2
         veJdI1R2X6/JU43CVRLwSE7SSyshMjG54TQmBwuZ2ybk4Hdwx7FM6f2OUMWLOhbVQOu7
         /Fag==
MIME-Version: 1.0
X-Received: by 10.42.102.142 with SMTP id i14mr27625093ico.90.1431806188550;
 Sat, 16 May 2015 12:56:28 -0700 (PDT)
In-Reply-To: <55579278.8090301@iki.fi>
References: <201505042003 DOT t44K3odg011007 AT delorie DOT com>
	<CAA2C=vAjN-HamFRWCQak=QF_NPjR5-TBYZw1U5707MO0b=qXkw AT mail DOT gmail DOT com>
	<554DF584 DOT 4020309 AT iki DOT fi>
	<CAA2C=vDaOJb_RW2bQEFoM_cqwp7yhzwX-CB328r5GCCi6XcooA AT mail DOT gmail DOT com>
	<55501DAD DOT 1080604 AT iki DOT fi>
	<CAA2C=vAvMW-yquZLSN=Z39NU24Kqf7urjan90801i7BDTdqOvQ AT mail DOT gmail DOT com>
	<55579278 DOT 8090301 AT iki DOT fi>
Date: Sat, 16 May 2015 22:56:28 +0300
Message-ID: <CAA2C=vBaQKzmch_buxFm20DJLcG+zv6d6803+qMEx=baA4Frog@mail.gmail.com>
Subject: Re: ANNOUNCE: DJGPP 2.05 beta 1
From: "Ozkan Sezer (sezeroz AT gmail DOT com)" <djgpp AT delorie DOT com>
To: djgpp AT delorie DOT com
Content-Type: text/plain; charset=UTF-8
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On 5/16/15, Andris Pavenis (andris DOT pavenis AT iki DOT fi) <djgpp AT delorie DOT com> wrote:
> On 05/11/2015 11:12 AM, Ozkan Sezer (sezeroz AT gmail DOT com) wrote:
>> [adding list back to CC]
>>
>> On 5/11/15, Andris Pavenis <andris DOT pavenis AT iki DOT fi> wrote:
>> [...]
>>> You also mentioned stdbool.h and float.h issues (no patches yet). I do
>>> not
>>> think we should touch
>>> them now before actual 2.05 release. Also including GCC own header and
>>> ones
>>> modified by
>>> fixincludes in GCC build process before system ones is way how it is
>>> done
>>> (not only for DJGPP but also
>>> for other targets).
>> For float.h issue:  Well, -nostdinc means -nostdinc so I think that we
>> should be consistent with it.  For gcc >= 4.8 maybe define our _rdtsc()
>> as __builtin_ia32_rdtsc()??  What was the exact problem with _rdtsc()
>> with gcc >= 4.8?
> If we define own _rdtsc() we get duplicate definition of it when GCC own
> header x86intrin.h is also
> included (for new GCC version). That was the reason why I used GCC defined
> function instead
> of DJGPP one.
>
> There is additional problem that GCC header files *intrin.h are not OK when
> -Wcast-qual is being used.
> The problem is triggered when building DJGPP tests but not when building
> libc itself.
>

Can you please show the error or warning messages form each
problematic case?

I tried to reproduce the problems: commented out the -I$(GCC_INC_DIR)
additions to CFLAGS in both src/ and tests/makefile.in, compiled src
using my gcc5 cross-compiler and got no errors or warnings for _rdtsc()
Tried compiling the test programs: since I am on linux, had to do some
voodoo in the makefiles by changing gcc and ld to cross- versions and
by replacing rem.com with /bin/true, they just compiled. (of course,
no run tests, and found other issues, but no _rdtsc() issues.)