From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12506 invoked by alias); 2 May 2014 17:49:27 -0000 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 Received: (qmail 12488 invoked by uid 89); 2 May 2014 17:49:26 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2 X-Spam-User: qpsmtpd, 3 recipients X-HELO: relay1.mentorg.com Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 02 May 2014 17:49:24 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1WgHaK-0000CH-M1 from joseph_myers@mentor.com ; Fri, 02 May 2014 10:49:20 -0700 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Fri, 2 May 2014 10:49:20 -0700 Received: from digraph.polyomino.org.uk (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.2.247.3; Fri, 2 May 2014 18:49:18 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.76) (envelope-from ) id 1WgHaG-0001Pm-V5; Fri, 02 May 2014 17:49:17 +0000 Date: Fri, 02 May 2014 17:49:00 -0000 From: "Joseph S. Myers" To: John Marino CC: , Jonathan Wakely , Gerald Pfeifer , , "Eric Botcazou (gnu.org)" Subject: Re: Contributing new gcc targets: i386-*-dragonfly and x86-64-*-dragonfly In-Reply-To: <5362DC9B.8090709@marino.st> Message-ID: References: <5352D100.9040108@marino.st> <5362DC9B.8090709@marino.st> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2014-05/txt/msg00109.txt.bz2 On Fri, 2 May 2014, John Marino wrote: > So given the track record (building itself, building base, building > 21,000 software ports) over a couple of years I think any issues this > could have caused would have been seen and identified by now. These issues aren't generally obvious (given that the ISO C conformance modes aren't used that often, and when they are that doesn't mean the application is using POSIX types for something else). > > (I don't know what the FreeBSD defines, but it at least > > seems possible from the name that it is only defining things in the > > implementation namespace, with the public being what then > > includes and does "typedef __foo_t foo_t;" or similar to > > provide the public POSIX types that aren't in ISO C.) > > Here are the headers in question: > http://grok.dragonflybsd.org/xref/freebsd/sys/sys/_types.h That seems OK for inclusion, as long as the is OK. > http://grok.dragonflybsd.org/xref/dragonfly/sys/sys/types.h That's definitely not correct to include in ; it defines lots of types outside the ISO C namespace. -- Joseph S. Myers joseph@codesourcery.com