From owner-svn-src-head@freebsd.org Thu Jul 5 02:03:56 2018 Return-Path: Delivered-To: svn-src-head@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96E591038198 for ; Thu, 5 Jul 2018 02:03:56 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) Received: from sonic304-23.consmr.mail.gq1.yahoo.com (sonic304-23.consmr.mail.gq1.yahoo.com [98.137.68.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 20B3480785 for ; Thu, 5 Jul 2018 02:03:55 +0000 (UTC) (envelope-from marklmi26-fbsd@yahoo.com) X-YMail-OSG: SyNll8cVM1lYCcogehcOUy5HJJ1UC6F6qufzX9G51bUWGAT4DEFPG2NqYuLFhU5 55PBjIXVaT.iF9Iv6Rvf0xctMksM66rgY6Q261_rk_Dg8Dxibd3iDSlTr0.ucuewIv2IR0U_Xuj3 0QOr4ZDi6iqItr6nTcMfok6zRpA.JSMJo.VNTEWvuy3aizGblW1vmGWLEfurCOmn2sOtAp1TSJ_9 doYIi85oC3qjKYcLWMUWZXOeCOO_1rWjoDfjWMIBc3tmYP_fn0KCDtQUJirlF_0gr8usd_wh.qHC gv_7X1_vv57lGIiGPEHwXhaqHFDamvPS.ElXDoVPjoSKe2oh193n645xFzo9elhF2yGX5MgiylLV wpb1GNXjI9CgfIdTy76Zvk6BXmXWH1ByfwiDbkLPOIrwdjDqBp2vA8GQUo6Iukc1rbNNd.NuLE3a 5D29RGA_dCmMQSiS5yqXXAMhZm44BF_srInG7lzsvfq83Z2lOO7TUnfh_LSF._DCdANlSqH67tz1 HMIrfP3IJusf3x4LNgusTEpv4x6u5gT2LIGNb5lqBiwsL.wZOei3iiwPa.CYxNLkVvu_RMLytF7I WFN4SnyavbJcbP0towue_H4rBrWrGuB3sFq01Xw07tAdIWB7a25_J_bvGvJktoTsQBXepFqG57Zi UrY9UtJTfHEKLaQQQn8kPbysboHwAkkaLVmSkkoKqOp7dlT3tzVGX74Zj7QOwFEZQiLkd3.u_Yc5 mPZVrBvTM4THlWZ1IF4ow6HixL.NP107UcTx80st18m2aO56KfZLsH7723R7.8huYpj5JDjpqqF4 ARIaBQr.yLVmtGiHvGxZ1RlLkWLUOcHQuMm2xIUk6RcrFRdGtYLvDv5QggRUOeLw6m4f8za0uz0K iwHo.h4D6vT57Pr2iEgQgmUmsjp8aLwqxOH3zIcPmBfA2NRPgCObAwRIoU.Nyixpp.uSnLw0I3Df YRMe2zwDp15g6a_2HLZCW.zpFRo6pixPp8E3rKoRI.TJSlHOgWRVIP2JxbhhBkhMuN4RJ Received: from sonic.gate.mail.ne1.yahoo.com by sonic304.consmr.mail.gq1.yahoo.com with HTTP; Thu, 5 Jul 2018 02:03:49 +0000 Received: from ip70-189-131-151.lv.lv.cox.net (EHLO [192.168.0.105]) ([70.189.131.151]) by smtp417.mail.gq1.yahoo.com (Oath Hermes SMTP Server) with ESMTPA ID 695dbe83b0f58e3bcd3a4919b1e4c523; Thu, 05 Jul 2018 02:03:47 +0000 (UTC) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: svn commit: r335888 - in head: contrib/blacklist/bin lib/libpjdlog sbin/hastd Message-Id: <1DED9D35-81AF-4814-9CE0-8556193524DF@yahoo.com> Date: Wed, 4 Jul 2018 19:03:46 -0700 To: Eitan Adler , svn-src-head@freebsd.org X-Mailer: Apple Mail (2.3445.8.2) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jul 2018 02:03:56 -0000 Eitan Adler lists at eitanadler.com wrote on Thu Jul 5 00:56:02 UTC 2018 : > On Tue, 3 Jul 2018 at 08:22, John Baldwin > wrote: > > since GCC usually breaks > > them. > > > Could you explain what you mean or point to a prior conversation? I'll take a stab at it without giving much for specific code examples. I do not claim the wording gives complete coverage but it should suggest some types of problems to expect. A) Gcc considers various FreeBSD definitions wrong by their criteria and attempts to override them. (That is what the Gcc "include-fixed" headers are for relative to FreeBSD. The issue is not unique to FreeBSD.) B) FreeBSD considers various Gcc definitions wrong by its criteria and attempts to override them. (FreeBSD, being an OS, would normally have the larger set of definitions overall. For example Gcc likely would not consider FreeBSD's _STANDALONE distinctions for max_align_t, say. [I've not checked the details. Only illustrative of a potential example.]) The mixing of code with (A) and (B) tends to be problematical. One way is that if the details for Gcc or FreeBSD change, things tend to end up mis-matched (at least until both sides adjust) even if they were working together correctly before. But even without that there are frequently problems with various details as they have been. Part of the overall issue is that FredBSD targets multiple standards, not just language standards, and various standards are not in full agreement. Gcc does not necessarily target the same set of standards or have the same selections for dealing with potential conflicts for what it does target. There are also issues of file conflicts, such as the area with float.h (from C) for Gcc also having altivec.h (not from C) and FreeBSD having its own file of the name --and the system-clang compiler source also having one. The 3 altivec.h files serve different purposes and are not alternatives for each other, despite the common name. Having Gcc (as a cross compiler) build system-clang with __ALTIVEC__ defined and picking out clang's altivec.h would be painful. (Currently targeting powerpc64 that way does not build system-clang with __ALTIVEC__ defined. The lack avoids the file issue but does not cover altivec correctly in the built clang.) (A) has been a difficult area for a long time and sometime back a ways was finally disabled in various Gcc ports. Even without (A), there are issues like the altivec.h issue that can end up involved. === Mark Millard marklmi at yahoo.com ( dsl-only.net went away in early 2018-Mar)