From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 02:46:13 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 25DC1F45 for ; Sun, 29 Mar 2015 02:46:13 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D54B8E55 for ; Sun, 29 Mar 2015 02:46:12 +0000 (UTC) Received: (qmail 30853 invoked from network); 29 Mar 2015 02:46:05 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 29 Mar 2015 02:46:05 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Sat, 28 Mar 2015 22:46:05 -0400 (EDT) Received: (qmail 7239 invoked from network); 29 Mar 2015 02:46:05 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 29 Mar 2015 02:46:05 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id CD95D1C439E; Sat, 28 Mar 2015 19:45:58 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: svn commit: r280636 - head/include Date: Sat, 28 Mar 2015 19:46:03 -0700 Message-Id: <111667CF-2A20-48CE-80F7-3F89FD274EB6@dsl-only.net> To: brde@optusnet.com.au Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-toolchain@freebsd.org, dim@FreeBSD.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 02:46:13 -0000 With reference to Dimitry Andric's Thu Mar 26 14:41:43 UTC 2015 note ... > On 26 Mar 2015, at 14:20, Tijl Coosemans wrote: > >=20 > > On Thu, 26 Mar 2015 17:37:53 +1100 (EST) Bruce Evans wrote: > >> On Wed, 25 Mar 2015, Pedro Giffuni wrote: > ... > >>> The reason why I had to revert the change is actually a systematic > >>> bug in gcc: during it's build process gcc generates a new cdefs.h > >>> from our headers. Attempting to use an older gcc from ports > >>> that was build with the broken mono-parameter __nonnull() ended > >>> up causing breakage in any code using signal.h or pthreads.h. > >>=20 > >> I see. gcc's "fixed" headers cause lots of problems. > >=20 > > I've complained about this multiple times in the past. The gcc = ports > > should not install these "fixed" headers. >=20 > Indeed. See also this recent discussion on -current: >=20 > = https://lists.freebsd.org/pipermail/freebsd-current/2015-March/055111.html= >=20 > where a "fixed" stdio.h (from a gcc port) causes trouble. >=20 > -Dimitry >=20 Preface: I do not want to be taken as indicating that GCC manipulation = of headers to make alternates is a good thing: it is not. I expect that = such creates lots of problems, as has been indicated. But I also maintain that the code sighted in = https://lists.freebsd.org/pipermail/freebsd-current/2015-March/055111.html= also has a problem relative to the C language standards (various = vintages), independent of any gcc header manipulation of the C standard = headers or FreeBSD headers. Setting up the context for the point: The code references the type name = va_list from a #include'd header () that is not from a C = standard in order to declare a function that is not from a C standard = (__xvprintf). The point: That code does so before any #include happens in = the #include sequence. Under the C standards one must include a standard = header before one's own code can validly refer to anything that the = standard header officially defines or declares. For the C standard headers themselves (various C standard vintages): is supposed to declare the likes of vfprintf, vprintf, and = vsprintf but not the public name va_list, just using a = private-named/anonymous synonym for the type to declare the functions. = Also is not supposed to include . The standard = headers have mutual independence (so include-order-independence) and = idempotent status (include-repeatability) only relative to each other, = not relative to one's own code that references the standard header = content. is the only C standard header that is supposed to define the = public name va_list (and so the one publicly available synonym for the = type in question). Where I get this from: Much of my background information for this and = the terminology that I use for the C library is from The Standard C = Library by P. J. Plauger, Copyright 1992. But I've not noticed any later = ANSI/ISO/IEC material indicating that the above material has changed = status in more recent vintages of the standard. I could be wrong since = I've not tried to be comprehensive about analyzing all the changes. I = have a copy of BS ISO/IEC 9899:1999 (with Technical Corrigendum 1 = incorporated and with the Revision 5.10 C Rationale) but not of the C11 = vintage of the standard. I'll shut-up on this point after this note (unless I get a = question/request) and I'll leave it to official FreeBSD folks for any = further consideration of what to do about the code sighted in = https://lists.freebsd.org/pipermail/freebsd-current/2015-March/055111.html= . Attempting to present my claim a 3rd time seems enough, likely = overkill already. I sent this note to freebsd-toolchain as it seemed more relevant than = freebsd-current for the issue involved. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 05:05:41 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CA2B8F26 for ; Sun, 29 Mar 2015 05:05:41 +0000 (UTC) Received: from mail-pd0-f169.google.com (mail-pd0-f169.google.com [209.85.192.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 94152D03 for ; Sun, 29 Mar 2015 05:05:41 +0000 (UTC) Received: by pdbni2 with SMTP id ni2so139828308pdb.1 for ; Sat, 28 Mar 2015 22:05:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=6st44eeoR7OQTk82/+UBd9qIl/mqCgfYe67qhsGfV7Q=; b=EQpQd94cWS1Hpq1LDgispsVqAC2D7ehd3oA3KpyTQj8KG6psaajnXNw56i1LyMNBBV N/ahROzXEmtsRuzektz9bYbCE25OuqQR/Vg2DZTe8kTJyHuku4oIesxGI1A80uiug9C0 IKk+y0Esnhv9p2mYi1uiyrMTUlrBmYGHlo5MTRNrCMlRAMx+Zt2lsRk2P18aTuuvWLS/ e4YPMYrjtV2bZwGzy95AyGph8S+eVAzT2hF1j+N8DCc9yqMsFFyfowNxBRV4EG+32dtd jIheL8QMixBnGGJBM3W8xxOKi377TexUWQyBqLs+6Br52BhjJFCIOxCJFzVmXfGfGJao OIfQ== X-Gm-Message-State: ALoCoQnsS1Rr/tl0VABPoTUTHzKUP8K/6Lq6BRXff3o6+dGXGh37jph9EhQ4pTlkU4O+Z5d0tMiR X-Received: by 10.70.54.130 with SMTP id j2mr47858974pdp.122.1427603840010; Sat, 28 Mar 2015 21:37:20 -0700 (PDT) Received: from lgwl-achen.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id o17sm6487583pdj.26.2015.03.28.21.37.18 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 28 Mar 2015 21:37:19 -0700 (PDT) Sender: Warner Losh Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_0507C6D9-DC61-4DCE-A5C6-02152AA25B0E"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> Date: Sat, 28 Mar 2015 22:37:16 -0600 Message-Id: <2232E613-6248-4A78-BCB3-2D82AF8EC094@bsdimp.com> References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> To: Dimitry Andric X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 05:05:41 -0000 --Apple-Mail=_0507C6D9-DC61-4DCE-A5C6-02152AA25B0E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 28, 2015, at 5:33 PM, Dimitry Andric wrote: >=20 > On 29 Mar 2015, at 00:05, Craig Rodrigues wrote: >>=20 >> To work around the problems build rescue, this time I used a build = host >> running FreeBSD-CURRENT at svn revision r280353 >>=20 >> I took this patch for libc++ and applied it to my tree: >>=20 >> http://reviews.llvm.org/D8461 >=20 > I've only got one minor remark left on that fix, which is that it > doesn't work for gcc 4.7. Once we either say that version of gcc is > just buggy and can't be helped, or have some other way of fixing the > original problem, I'll import it. >=20 >=20 >=20 >> I used this script to build with gcc 4.9: >>=20 >> = https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-buil= d.sh >>=20 >> Buildling sys/i386/boot2 failed: > ... >> output: fmt=3Dbin size=3D21ef text=3D200 data=3D1fef org=3D0 entry=3D0 >> -1007 bytes available >> *** Error code 1 >=20 > Oof, this is going to be hard to fix. For some reason, boot2 is one = of > those programs that keeps getting worse (i.e. larger) with *each* new > compiler version, be it gcc or clang! >=20 > The last few times when we imported a new clang version, we had to = jump > through several hoops, and attempted to shrink the code again with > various cleanups. Even then, we don't have a lot of headroom. >=20 > If it is now also becoming a problem with gcc 4.9, we should really > start looking for a more permanent solution, e.g.: > * Getting rid of the 7680 byte limit (seems to be impossible?) > * Rewrite most of (or all of) boot2 in assembly The 7680 byte limit is a hard limit. Rewriting in assembler is possible, but just using the 4.2.1-compiled .s = file might be a good place to start. Warner --Apple-Mail=_0507C6D9-DC61-4DCE-A5C6-02152AA25B0E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIbBAEBCgAGBQJVF4F8AAoJEGwc0Sh9sBEARpcP+KzDBa6DY1Z9HxQmwWLawrCL uku9dXdY7nHII3R4Rc4kccliV65RoY1ajVtP4t+yRQURpDyUPv11wYPCu9knqkyH cTCpDfinY//APg+IY1VHKaoGKAjTeOyf8Hsfvxz/qMqA45VPYHH6ZD/OHNv1fqlb hTk+YbO3OWdPZO0cLH5m/yj29/d+BPbIvViAkqrvKxDTeYT+8R4fzKZYN6hfQXSP 15j3qXwUaFhgsonzmgeM1q/c8LJZYmuA6nhlS8qGf2/SIWeoaoHttdTSVEGIoW3b TSx0G/WwFJ3Ndwr7+MsIerv3rfQdLAPNOcK8DKhzpINKU2RdDwO0jUcIZ3KVI80y vPfZXxINCZx5DKIprooROV9EdEg6wFGxSiaMFiA+RpwWMnkCeY7hRSlf0afs4AMY 1FIiGppmXy+21l83AJJSET+H4PEJggDMGuJlsKJQFDcEWs66LGZ8cPYSMNMAXvpB fenjWPht94Mk3af1QBrtYgBQJXWeSmdPsQfnAxmJTHw22Xjv+RWqQQK7A0GAR1bH B/DQn2kBUUEIBDF0Ie+8bjEx891dREgythlv3O1pcuavbb94mHe2UA+8U1vfahJ8 ZA3jd+b+9IwkiRiapg6V1elrQ3pp1Obc71e9Z+Mq2+up7fKZiOlz57PvS2g01vYP /OAr56eIQ7xZGKHymAs= =O8Dy -----END PGP SIGNATURE----- --Apple-Mail=_0507C6D9-DC61-4DCE-A5C6-02152AA25B0E-- From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 05:08:44 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CC27191; Sun, 29 Mar 2015 05:08:44 +0000 (UTC) Received: from mail104.syd.optusnet.com.au (mail104.syd.optusnet.com.au [211.29.132.246]) by mx1.freebsd.org (Postfix) with ESMTP id 5CAE9D21; Sun, 29 Mar 2015 05:08:44 +0000 (UTC) Received: from c211-30-166-197.carlnfd1.nsw.optusnet.com.au (c211-30-166-197.carlnfd1.nsw.optusnet.com.au [211.30.166.197]) by mail104.syd.optusnet.com.au (Postfix) with ESMTPS id 3612342706F; Sun, 29 Mar 2015 16:08:34 +1100 (AEDT) Date: Sun, 29 Mar 2015 16:08:33 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Mark Millard Subject: Re: svn commit: r280636 - head/include In-Reply-To: <111667CF-2A20-48CE-80F7-3F89FD274EB6@dsl-only.net> Message-ID: <20150329142917.P1402@besplex.bde.org> References: <111667CF-2A20-48CE-80F7-3F89FD274EB6@dsl-only.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Optus-CM-Score: 0 X-Optus-CM-Analysis: v=2.1 cv=ZuzUdbLG c=1 sm=1 tr=0 a=KA6XNC2GZCFrdESI5ZmdjQ==:117 a=PO7r1zJSAAAA:8 a=kj9zAlcOel0A:10 a=JzwRw_2MAAAA:8 a=6I5d2MoRAAAA:8 a=hWZVuA9nwej52J9Q4EUA:9 a=CjuIK1q_8ugA:10 a=mDKAPUMXjBQA:10 Cc: freebsd-toolchain@freebsd.org, dim@freebsd.org, brde@optusnet.com.au X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 05:08:44 -0000 On Sat, 28 Mar 2015, Mark Millard wrote: > With reference to Dimitry Andric's Thu Mar 26 14:41:43 UTC 2015 note ... >>> [... gcc's "fixing" of headers] >> Indeed. See also this recent discussion on -current: >> >> https://lists.freebsd.org/pipermail/freebsd-current/2015-March/055111.html >> >> where a "fixed" stdio.h (from a gcc port) causes trouble. > > Preface: I do not want to be taken as indicating that GCC manipulation of headers to make alternates is a good thing: it is not. I expect that such creates lots of problems, as has been indicated. > > But I also maintain that the code sighted in https://lists.freebsd.org/pipermail/freebsd-current/2015-March/055111.html also has a problem relative to the C language standards (various vintages), independent of any gcc header manipulation of the C standard headers or FreeBSD headers. > > Setting up the context for the point: The code references the type name va_list from a #include'd header () that is not from a C standard in order to declare a function that is not from a C standard (__xvprintf). is nonstandard, so it can do anything it wants, including requiring users of it to do certain things although that is of low quality. It does do the latter. stdio.h is fairly careful about namespace pollution, but printf.h has mounds of namespace pollution. It is not documented in any man page, and I don't like it so I try not to look at it and don't remember what it is supposed to do. Outside of libraries, it is only used in a single place in /usr/src (hastd). So it appears to be an implementation detail that escaped. It might be clean enough for an implementation detail. It has 4 namespace errors and 1 or 4 style bugs in the line that declares __xvprintf(). Almost all the identifiers have 1 or 2 bugs: X int __xvprintf(FILE *fp, const char *fmt0, va_list ap); - "int" is correct - after "int", there is the style bug not indenting the function name. All the prototypes in this file have this bug. stdio uses the very strict KNF indentation of 1 tab, then 1 space to line after the function names after putting a "*" in front of some of them - "__xvprintf" is correct - "FILE" is correct. This file has stdio.h as a prerequisite (though it includes stdio.h itself, perhaps for its broken conversion to a public header) - "fp" is broken since it is in the application namespace - "fp" is a style bug in strict KNF. Strict KNF disallows names for parameters in prototypes to avoid the previous bug in a way that I don't like. The originators of this style didn't like names with the necessary number of underscores (1). - "fmt0" and "ap" have the same 2 bugs as "fp" - "va_list" is more fundamentally broken. It is not always declared in stdio.h, so it cannot be used here. In C99, stdio.h is not permitted to declared it. I forget if C99 always leaves it in the application namespace unless is included. POSIX broke this in some cases, and FreeBSD broke it in more cases (see below). Apparently, gcc causes further problems by "fixing" some cases. Indeed, gcc48 "fixes" the broken declaration of va_list to one of __not_va_list__, and fixes the non-broken use of __va_list to use of __gnu_va_list. gcc can hard-code __gnu_va_list like this, but FreeBSD cannot. FreeBSD's __va_list is a macro that expands to __gnu_va_list iff that is correct. __not_va_list__ seems to be completely broken. Sometimes it is correct for stdio.h to declare va_list, and the "fix" breaks these cases. printf.h should take the same care as stdio.h here. For va_list, this is just to use __va_list like stdio.h does in 9 places. Most of the other bugs can be fixed by removing the parameter names. stdio.h used to be careful with parameter names, but now has bugs like missing parentheses in almost all of the uses of the parameter names in the __cplusplus section at the end of the file (these are macro parameters, so their names don't need underscores). The only obvious bugs in parameters in old code is missing parentheses for fropen() and fwopen(). The brokenness of va_list in is: - POSIX.1-2001 is broken by specifying va_list to be declared in for the XSI case - some time after the 2004 version on the web, but before a 2007 draft version, POSIX completed this breakage by specifying va_list to be declared in unconditionally. It marks this as a C extension of course - C11 didn't break this, at least in the n1570.pdf draft. It still doesn't have it in stdio.h, and says to include both and before using each of the varargs functions in . Using these functions without including may even be an error if their va_list parameter is just passed to another function. FreeBSD's implementation using the __va_list spelling doesn't force an error in this case. - FreeBSD broke this for 2001 POSIX until before the version of POSIX that completed the breakage, by declaring va_list in stdio.h for all versions of POSIX >= 200112, instead of for all versions of POSIX >= 200809 or whenever it was that the bug became standard. This is in addition to declaring it for XSI like it used to be. FreeBSD never declared this under __BSD_VISIBLE like it does for the smaller XSI bugs. Declaring things for convenience in multiple headers just gives portability problems. Many headers were misdesigned, so the multiple declarations are needed for historical reasons, but stdio.h only has this bug in recent versions. > The point: That code does so before any #include happens in the #include sequence. Under the C standards one must include a standard header before one's own code can validly refer to anything that the standard header officially defines or declares. That would be correct for an application header, but since printf.h is a public header it should use __va_list and not export everything in stdarg.h. (The POSIX breakage doesn't even avoid the requirement to include stdarg.h for most uses, since not many uses need only va_list and the POSIX breakage is limited to the va_list symbol.) Since printf.h is new and unportable, it can also declare va_list unconditionally without affecting portability , but that alone is as useless as when stdio.h declares it alone. > For the C standard headers themselves (various C standard vintages): > > is supposed to declare the likes of vfprintf, vprintf, and vsprintf but not the public name va_list, just using a private-named/anonymous synonym for the type to declare the functions. Also is not supposed to include . The standard headers have mutual independence (so include-order-independence) and idempotent status (include-repeatability) only relative to each other, not relative to one's own code that references the standard header content. Indeed, but printf.h is not incorrect in requiring stdio.h to declare va_list. It can simply only support POSIX >= 200809 or whatever, so that the above doesn't apply to stdio.h and stdio.h is required to declare va_list. If it were documented, then its documentation could say this. gcc's "fix" is clearly broken in this case for applications too. > Where I get this from: Much of my background information for this and the terminology that I use for the C library is from The Standard C Library by P. J. Plauger, Copyright 1992. I learned a lot from that too. Also from glibc at the same time. Both are very careful about namespaces. I try to be careful about namespaces without being so ugly. One method for being not so ugly for the declaration of varargs functions in stdio.h is to hard-code the type underlying va_list instead of macroizing it. But that only works well for a single compiler on a single system for a short time. > But I've not noticed any later ANSI/ISO/IEC material indicating that the above material has changed status in more recent vintages of the standard. I could be wrong since I've not tried to be comprehensive about analyzing all the changes. I have a copy of BS ISO/IEC 9899:1999 (with Technical Corrigendum 1 incorporated and with the Revision 5.10 C Rationale) but not of the C11 vintage of the standard. Unfortunately, XSI always was broken/sloppy with almost all extensions, and POSIX standardized many old mistakes that it left out in 1988, and standards are now too large for anyone to understand (gcc is doing well to "fix" only 1 bug per large ifdef-tangled header). Details are just easier and less expensive to find on the web. Bruce From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 08:22:42 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A5EA48F for ; Sun, 29 Mar 2015 08:22:42 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 569E89A for ; Sun, 29 Mar 2015 08:22:41 +0000 (UTC) Received: (qmail 26049 invoked from network); 29 Mar 2015 08:22:40 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 29 Mar 2015 08:22:40 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Sun, 29 Mar 2015 04:22:40 -0400 (EDT) Received: (qmail 6622 invoked from network); 29 Mar 2015 08:22:39 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 29 Mar 2015 08:22:39 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 37388B1E008; Sun, 29 Mar 2015 01:13:06 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: FYI: Things that I've noticed for powerpc64-xtoolchain-gcc... Date: Sun, 29 Mar 2015 01:13:05 -0700 Message-Id: <056FF51B-CB8A-42E9-A7BA-B0A022F2640C@dsl-only.net> To: rodrigc@FreeBSD.org Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) Cc: freebsd-toolchain@freebsd.org X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 08:22:42 -0000 You [Craig Rodrigues] seem to be checking some ??-xtoolchain-gcc things = officially. I've some user-experience notes from happening to use = powerpc64-xtoolchain-gcc in my exploration of FreeBSD. Hopefully some of = it might be of interest. It groups together information from various = notices as I was doing the explorations. I've been exploring FreeBSD, in part using powerpc64-xtoolchain-gcc = --but on a powerpc64 11.0-CURRENT environment for the points at hand: A = form of self-hosting xtoolchain use. As stands I'm limited to powerpc64 = and powerpc contexts for FreeBSD, PowerMacs specifically. So I might = over infer general ??-xtoolchain-gcc properties. My use is not generally of the grab-source and buildworld/buildkernel = from scratch kind of context. The closest I came to that was rebuilding = a gcc 4.2.1 built powerpc64 11.0-CURRENT to be a powerpc64-gcc based = 11.0-current that had libc++ in use. After that I've updated (svnlite update -r??????) and rebuilt a newer = 11.0-CURRENT. I'm not sure if the continuous integration or other ??-xtoolchain-gcc = testing checks on rebuild-for-update kind of context or not. One of the = things of note for me is specific to that kind of context where headers = and libraries temporarily have both old and new vintages around and the = right ones need to be used in specific stages. Other aspects of my use = might also go outside the range of your activity as well. The primary things that I've run into include: A) Rebuilds from updated sources were picking up old headers (from, for = example, /usr/include) and old libraries, not just for legacy/ where = such makes sense. B) I had a specific problem originally with atf-c++ finding the C++ = standard library headers. I added a specific -I for what was = ${WORLDTMP}/usr/include/c++/v1 in order for it to find the files. I also = put in a matching -L for /usr/obj/usr/src/lib/libc++ . C) powerpc64-gcc automatically looks in /usr/local/include for header = files (like most such ports) and this can pick up the wrong file(s). I = ended up using the manual policy of renaming /usr/local/include/iconv.h = during buildworld/buildkernel so that it would not be found and used = where the build should have found a file with different content from my = /usr/src/... area (or its WORLDTMP copy). D) I've been limited to WITHOUT_BOOT=3D WITHOUT_LIB32=3D by being unable = to get the 32-bit environment activity to work: = CROSS_TOOLCHAIN=3Dpowerpc64-gcc use did not allow the -melf32ppc_fbsd . = Does targeting i386 for BOOT and LIB32 from amd64 have a similar problem = with -melf_i386_fbsd ? E) I've been limited to WITHOUT_GCC_BOOTSTRAP=3D by XCC being a full = path making the build environment ignore WITH_GCC_BOOTSTRAP=3D . = Similarly WITH_GCC=3D does not actually cause gcc 4.2.1 to be built. (I = wanted WITHOUT_GNUCXX=3D in order to try libc++ only. So I've not tried = WITH_GNUCXX=3D .) F) I've been limited to WITHOUT_CLANG_BOOTSTRAP=3D WITHOUT_CLANG=3D = WITHOUT_LLDB=3D by various issues when clang related builds are = involved. I'll not go into details. G) Last I tried it powerpc64-xtoolchain-gcc does not correctly install = itself automatically when one attempts to install it in a powerpc64-host = context. (It installs fine on a powerpc (non-64) host context.) This may = be associated with the same points that make the distinction between = /usr/obj/powerpc.powerpc64/usr/src/ (on/in powerpc (non-64)) and = /usr/obj/usr/src/ (on/in powerpc64) as a default path: in part the = errors were empty file name prefixes vs. filled-in prefixes. H) After the gcc 4.2.1 -> 4.9.1 bootstrap I had to rebuild powerpc64-gcc = in order to get the -pg compiles to always work: without that at least = one required example of such a compile crashed the compiler every time = it was tried. All -pg compiles worked fine after the rebuild. (I used = gcc5 to rebuild 4.9.1 because of (G) ending up involved otherwise.) = Before, when still booted from the gcc-4.2.1-based world, the original = gcc 4.9.1 compiler did not crash for -pg compiles. I) Trying to use powerpc64-xtoolchain-gcc from a powerpc (non-64) host = does not work. One aspect is tool chain related: C/C++/assembler usage = need to be told to be 64-bit such that, for example, __powerpc64__ ends = up defined for pre-processor use. That is not happening and incorrect = processor generated files result. For example the assembler reports = syntax errors from lack of definitions related to TOC use for powerpc64. There are some work arounds involved for things very powerpc64/powerpc = context specific, such as some Makefile*'s forcing use of CC:=3Dgcc . = I've not noted such things above: The above targets what I'd guess might = be more general issues. I've also not noted when 11.0-CURRENT has = required a few files to have specific versions picked out that did not = match the snapshot I was generally using at the time. My current context for this is: > # freebsd-version -ku; uname -apKU > 11.0-CURRENT > 11.0-CURRENT > FreeBSD FBSDG5C0 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r280598M: Fri = Mar 27 18:26:08 PDT 2015 = root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc = powerpc64 1100066 1100066 > # dmesg | head > ... > FreeBSD 11.0-CURRENT #0 r280598M: Fri Mar 27 18:26:08 PDT 2015 > root@FBSDG5C0:/usr/obj/usr/src/sys/GENERIC64vtsc-NODEBUG powerpc > gcc version 4.9.1 (FreeBSD Ports Collection for powerpc64)=20 > ... I originally bootstrapped using -r279514. After that I attempted = rebuilding 279514 various times exploring what I could enable = successfully vs. what I could not. -r280598 was my first attempt to = svnlite upgrade then rebuild. The 4.2.1 gcc is not present. Nor has clang been built: 3.4.1 was = removed by make delete-old after the initial bootstrap. I'm using = powerpc64-gcc as the only system compiler after the bootstrap. (This = fits with (E) above.) > make -j 8 CROSS_TOOLCHAIN=3Dpowerpc64-gcc \ > WITHOUT_CLANG_BOOTSTRAP=3D WITHOUT_CLANG=3D WITHOUT_CLANG_IS_CC=3D \ > WITHOUT_LLDB=3D \ > WITHOUT_GCC_BOOTSTRAP=3D WITHOUT_GCC=3D WITHOUT_GNUCXX=3D \ > WITHOUT_BOOT=3D WITHOUT_LIB32=3D \ > buildworld buildkernel \ > KERNCONF=3DGENERIC64vtsc-NODEBUG \ > TARGET=3Dpowerpc TARGET_ARCH=3Dpowerpc64 For the below: Remember, no 4.2.1 gcc and no clang. So powerpc64-gcc = also has to cover what those would normally be used for, not just the = XCC, XCXX, XCPP usage. (powerpc and powerpc64 via clang is not a = supported combination yet anyway.) > # more /etc/src.conf=20 > NO_WERROR=3D > WITH_LIBCPLUSPLUS=3D > CC=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-gcc > CXX=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-g++ > CPP=3D/usr/local/bin/powerpc64-portbld-freebsd11.0-cpp > CROSS_BINUTILS_PREFIX=3D/usr/local/powerpc64-freebsd/bin/ > X_COMPILER_TYPE=3Dgcc > #CFLAGS+=3D-L/usr/obj/usr/src/tmp/usr/lib/. > # The order of the two CXXFLAGS additions below is important. > CXXFLAGS+=3D-I/usr/obj/usr/src/tmp/usr/include/c++/v1/. -std=3Dgnu++11 = -L/usr/obj/usr/src/lib/libc++/. > CXXFLAGS+=3D-I/usr/include/c++/v1/. -std=3Dgnu++11 -L/usr/lib/. (I make no claim that the above is a general solution but with some care = about how to do builds it has allowed the experiments that I've done. I = sometimes have used /usr/srcC/ instead of /usr/src/ : I have two = 11.0-CURRENT source trees.) > # more /etc/make.conf=20 > WRKDIRPREFIX=3D/usr/obj/portswork > #WITH_DEBUG=3D > MALLOC_PRODUCTION=3D > # svnlite st /usr/src --no-ignore > ? /usr/src/.snap > ? /usr/src/restoresymtable > M /usr/src/sys/ddb/db_main.c > M /usr/src/sys/ddb/db_script.c > ? /usr/src/sys/powerpc/conf/GENERIC64vtsc > ? /usr/src/sys/powerpc/conf/GENERIC64vtsc-NODEBUG > ? /usr/src/sys/powerpc/conf/GENERICvtsc > ? /usr/src/sys/powerpc/conf/GENERICvtsc-NODEBUG > M /usr/src/sys/powerpc/ofw/ofw_machdep.c > M /usr/src/sys/powerpc/ofw/ofwcall64.S All of the above files that are relevant existed and were in use long = before I started the powerpc64-xtoolchain-gcc related explorations. = ofw_machdep.c is tied to a PowerMac-specific change for reliable = booting. The db_'s and ofwcall64.S are tied to getting information from = early-boot crashes if I get any more. The GENERIC*'s relate to that = early-information gathering and to disabling ps3 so that I can then also = have both vt and sc enabled. As this has been an exploration of the unfamiliar, I've had false = starts, backtracking, and the like. While I've learned a bunch I doubt = that I could start over and get to where I am by a step-by-step = procedure that avoided backtracking, pondering, retries, and so on. In = some respects I've been lucky that certain types of changes did not = happen between my original and upgraded vintages: things would not have = worked that did work. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 08:28:18 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA2AC541; Sun, 29 Mar 2015 08:28:18 +0000 (UTC) Received: from vlakno.cz (mail.vlakno.cz [91.217.96.224]) by mx1.freebsd.org (Postfix) with ESMTP id 6C519D5; Sun, 29 Mar 2015 08:28:17 +0000 (UTC) Received: by vlakno.cz (Postfix, from userid 1002) id 23CCB1D9572A; Sun, 29 Mar 2015 10:27:34 +0200 (CEST) Date: Sun, 29 Mar 2015 10:27:34 +0200 From: Roman Divacky To: Dimitry Andric Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 Message-ID: <20150329082734.GA13058@vlakno.cz> References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 08:28:18 -0000 > > I used this script to build with gcc 4.9: > > > > https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-build.sh > > > > Buildling sys/i386/boot2 failed: > ... > > output: fmt=bin size=21ef text=200 data=1fef org=0 entry=0 > > -1007 bytes available > > *** Error code 1 > > Oof, this is going to be hard to fix. For some reason, boot2 is one of > those programs that keeps getting worse (i.e. larger) with *each* new > compiler version, be it gcc or clang! > > The last few times when we imported a new clang version, we had to jump > through several hoops, and attempted to shrink the code again with > various cleanups. Even then, we don't have a lot of headroom. > > If it is now also becoming a problem with gcc 4.9, we should really > start looking for a more permanent solution, e.g.: > * Getting rid of the 7680 byte limit (seems to be impossible?) > * Rewrite most of (or all of) boot2 in assembly We can also get rid of UFS1 support... That shrinks the code a lot. From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 18:04:41 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F2A7726A for ; Sun, 29 Mar 2015 18:04:41 +0000 (UTC) Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BB9B4213 for ; Sun, 29 Mar 2015 18:04:41 +0000 (UTC) Received: by pacwe9 with SMTP id we9so145171455pac.1 for ; Sun, 29 Mar 2015 11:04:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=POvIiJc6q8PuL0KV2DT3Mt1SvTZD6RncD/Akmq8gHaY=; b=RrQt7H21hVJhHYFKrRQnWZVcWchUO2eO5HWC6Kk70zAmoqtFbyt0Mg4B7y6fXeaj/a Cnw4VIciysgUap/KeaULpX0CtYwkNd7S9Dmc06sAf3OxYAZkPaD1sPVMPRBzSg7n8EVc KTTAHl43wPYvxIjlbdiOYMew7vVd/xeiSL7FITQUVKwqB7//kZvMc6htS1wErqZPXwJ2 1gb8mv7MphvabJXC34UFVG1AO/TnDjY4sKCwGEepZqvM84pwwESUWhIq3ixwRCJjGBI2 a4Hmku3g6Uu+EvhRwNuvTQud5iP1CgeAIVV+fTbHnLjch+fE7tadNOkiMxwFbZRea+XG NGHg== X-Gm-Message-State: ALoCoQmp2bih/Osu3utIZZC/4OXQbEWcDy3CoeKFSxnE3MYoNH3eB1P5fFmYf8cj1MtsweHdlmmV X-Received: by 10.70.102.101 with SMTP id fn5mr52586103pdb.131.1427652275372; Sun, 29 Mar 2015 11:04:35 -0700 (PDT) Received: from lgwl-achen.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id om6sm8097092pdb.40.2015.03.29.11.04.33 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 29 Mar 2015 11:04:34 -0700 (PDT) Sender: Warner Losh Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_A96F48DD-9F5F-44DB-A5D1-2CE1502149AE"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: <20150329082734.GA13058@vlakno.cz> Date: Sun, 29 Mar 2015 12:04:31 -0600 Message-Id: References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> <20150329082734.GA13058@vlakno.cz> To: Roman Divacky X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain , Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 18:04:42 -0000 --Apple-Mail=_A96F48DD-9F5F-44DB-A5D1-2CE1502149AE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 29, 2015, at 2:27 AM, Roman Divacky = wrote: >=20 >>> I used this script to build with gcc 4.9: >>>=20 >>> = https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-buil= d.sh >>>=20 >>> Buildling sys/i386/boot2 failed: >> ... >>> output: fmt=3Dbin size=3D21ef text=3D200 data=3D1fef org=3D0 entry=3D0= >>> -1007 bytes available >>> *** Error code 1 >>=20 >> Oof, this is going to be hard to fix. For some reason, boot2 is one = of >> those programs that keeps getting worse (i.e. larger) with *each* new >> compiler version, be it gcc or clang! >>=20 >> The last few times when we imported a new clang version, we had to = jump >> through several hoops, and attempted to shrink the code again with >> various cleanups. Even then, we don't have a lot of headroom. >>=20 >> If it is now also becoming a problem with gcc 4.9, we should really >> start looking for a more permanent solution, e.g.: >> * Getting rid of the 7680 byte limit (seems to be impossible?) >> * Rewrite most of (or all of) boot2 in assembly >=20 > We can also get rid of UFS1 support... That shrinks the code a lot. No we can=E2=80=99t. And that=E2=80=99s kinda the useless decision to = make if you look at where the 8k limit comes from. UFS1 imposes the 8k limit. UFS2 has no such limit, but there=E2=80=99s = some issues with some old installs listing 8k as the size to fit into the = disklabel reserves of the time. If we built a UFS1-only boot2, that would fit in the 7.5k we have left to play with. We could then build a UFS2-only boot2 that would easily fit in the like 32k limit that UFS2 has. The only reason we went to supporting both was to have something universal. Since it requires a reformat to go from UFS1 -> UFS2 we wanted the transition to be as smooth as possible so you didn=E2=80=99t = have to add boot blocks into the mix. Now the only people that use UFS1 are people with really old systems that are never going to upgrade, or people building new systems with UFS1 because they are space constrained (for whatever reasons that we=E2=80=99re not going to debate here: they are still real). All typical installs are UFS2. As such, with a bit of automation in our boot block writing, and we = should be in good shape. So no, we can=E2=80=99t get rid of UFS1 support and have all our = problems be solved. However, we likely can solve most of the issues by moving away from a single image. Warner --Apple-Mail=_A96F48DD-9F5F-44DB-A5D1-2CE1502149AE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVGD6vAAoJEGwc0Sh9sBEAOCUQANHGNvoPEMMT3AVpZ7X+SDlh xGj3WEqn+HkGoGYrmaNuFuas21RgCAALK05q1WgJw1HGvYXsT0E4dFMEBQkY9G2k veP+IqX4vJzcFnE4XpLRUr/59bAvOljHVNDVZ/qFLwVkE9VdrZS158r664QNFCC1 i++B4roNUE12Ew8vqYspei5nojEAg/PU6scUJXh5zpitmEyFOf+yYu4mPKeb0Nz/ j+cnj6NqYBc/Unfu7+GhFfhzAnDNqC3YaruZifxuZQH5cv3K94CE+nwg3YqLc0B2 vyUCi2wDR2rHwe9KOXmM9BDpDuM+1Qk32jZNOSjEeY3s3Ywgq5y20ZSm3BqXuipB +TM+x+c2q0RGDouQbXlbr8HBRqseXdAPaS4hI7SzxC37Rmja4JixuXdO4NQJo8aT aXRhpUHM0UBcZutAmwk4I5zpoReowax5vfl6ePbMYzA8VkcG/vKflDpCVPYm7A+v bGKty/4hTwYg+5lDsYxLEGJiJReZeOmhU14v9kbqPlv6dXwX/a6+qg2wewSVG5D5 r5Iw64Alm7zBld00BzGsnU2aGZVBjf7FKSG4h7MNfjyMLp+QisdkJYFdqTELL8Pp aQpfB/yGY0H6PZ/1JkaBMwAghbsD+gh2F6oIIV05VnQl20BW6KFnwVn5z5FHrYWw 384tREhodceyLacoeetv =IwfO -----END PGP SIGNATURE----- --Apple-Mail=_A96F48DD-9F5F-44DB-A5D1-2CE1502149AE-- From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 20:29:48 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF96E1E2; Sun, 29 Mar 2015 20:29:48 +0000 (UTC) Received: from mail-la0-x22b.google.com (mail-la0-x22b.google.com [IPv6:2a00:1450:4010:c03::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3B80A309; Sun, 29 Mar 2015 20:29:48 +0000 (UTC) Received: by labe2 with SMTP id e2so103705326lab.3; Sun, 29 Mar 2015 13:29:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Cal+6UGJnrCcjPE0BFOK9iYwrV012S7AyA/mOGaZE7I=; b=Snw4gNibXFP7eUyfEKUfT5qb6UqP1DnvO3FQ9P7oNQC51awOA2Icqg8+/Kz1nuMWZx TpeoNCSN5DuaU4SInSRbG/z/qe8WACnEGw5F8kZ5o20dl3nAF5UL/vEEWES9ze3y6Lh8 MqRuNlLxNFScALuvUfPM2dAahIr/GPJxYigkfPhaKEJG9QaybNbWLmiY0yS/MT71v7RK 1C9ou2Z8bJrJZxMvmw3UpDPeOc05kwn71j2n4gZO7zWZvOa4wa/itaV47IxBGXR4Fn5Y GxBG/yNqmxYV1jD08l2SJnAjaT6uOnUMZ95oYdXD8kzVgyikZUQQatzLtouK+9D0IFbZ AMRg== MIME-Version: 1.0 X-Received: by 10.112.166.36 with SMTP id zd4mr10574624lbb.59.1427660986284; Sun, 29 Mar 2015 13:29:46 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Sun, 29 Mar 2015 13:29:46 -0700 (PDT) In-Reply-To: References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> <20150329082734.GA13058@vlakno.cz> Date: Sun, 29 Mar 2015 13:29:46 -0700 X-Google-Sender-Auth: XvaJ4bBMrggolZH2Vdbxnqj_I6g Message-ID: Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 From: Craig Rodrigues To: Warner Losh Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain , Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 20:29:48 -0000 On Sun, Mar 29, 2015 at 11:04 AM, Warner Losh wrote: > > If we built a UFS1-only boot2, that would fit in the 7.5k we have left > to play with. We could then build a UFS2-only boot2 that would easily > fit in the like 32k limit that UFS2 has. > > The only reason we went to supporting both was to have something > universal. Since it requires a reformat to go from UFS1 -> UFS2 we > wanted the transition to be as smooth as possible so you didn't have > to add boot blocks into the mix. > > Now the only people that use UFS1 are people with really old systems > that are never going to upgrade, or people building new systems with > UFS1 because they are space constrained (for whatever reasons that > we're not going to debate here: they are still real). > In the past 5 years, I have worked on some embedded systems where UFS1 was chosen because of very low memory and disk space requirements. So those systems are real and out there. Just out of curiousity, what is it about newer compilers that cause the size of boot2 to increase so much? Could we do some silly things like removing/reducing the use of printf() to save some more bytes, in order to buy us more time, before having to rewrite everything? :) -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 20:39:11 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BACF6489 for ; Sun, 29 Mar 2015 20:39:11 +0000 (UTC) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3C4C9400 for ; Sun, 29 Mar 2015 20:39:11 +0000 (UTC) Received: by lagg8 with SMTP id g8so103914282lag.1 for ; Sun, 29 Mar 2015 13:39:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=SzLxOPLpbV0csTiQLQ6a7kYDW7gHhogkkEwCZOk/nrU=; b=Es5ArCfHOR5dPHwwRCniouPRP+CfvjNdCcPMsVRaYyY8e3fruOtk3LlUarfUNyEKWV F3/GFY2jowviJZK9rxeFy9kxtFgezsTGiw6CJ0wa3MlRV/u8l6aG/nt3+9P2vcajeWqy OoH8YRNqv/AhaKOBgJ/e8r2/l/KHqxeWIPoRq7V9Kz1gxbcmeBMtBDRpZvYnYp9QxMqC u/8Fw6NDM3hLq+Ik+0CiWxbHb66pyrQbXFbTHeN4f+hGgahJu6Wn+jmEarEHp8S+OcwZ 5vMGHgTD/8DXH+oyLrOexJqXVfIgbIJJnyBAa4hAqtK6Za6/5cbKnQX/b/Dmo/+2psuq 7r9w== MIME-Version: 1.0 X-Received: by 10.152.36.169 with SMTP id r9mr3125491laj.29.1427661549343; Sun, 29 Mar 2015 13:39:09 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Sun, 29 Mar 2015 13:39:09 -0700 (PDT) Date: Sun, 29 Mar 2015 13:39:09 -0700 X-Google-Sender-Auth: LEHoRDM-O6SlWtWLahdJpCBPy7I Message-ID: Subject: Failed to build usr.bin/clang/clang with gcc 4.9 From: Craig Rodrigues To: FreeBSD Toolchain Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 20:39:11 -0000 Hi, When building with gcc 4.9, I am getting unresolved symbols at link time when building usr.bin/clang/clang. Here is one error message: /usr/obj/opt2/branches/head/usr.bin/clang/clang/../../../lib/clang/libclangcodegen/libclang codegen.a(ModuleBuilder.o): In function `(anonymous namespace)::CodeGeneratorImpl::HandleTranslationUnit(clang::ASTContext&)': ModuleBuilder.cpp:(.text+0x113): undefined reference to `clang::CodeGen::CodeGenModule::clear()' There are many more errors like that in my full build log here: https://people.freebsd.org/~rodrigc/gcc/buildworld.2015_03_29.log.txt Any ideas? -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 20:52:38 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6449A7CE; Sun, 29 Mar 2015 20:52:38 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 20EEC7F8; Sun, 29 Mar 2015 20:52:38 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::64fe:5f0d:c4ae:7330] (unknown [IPv6:2001:7b8:3a7:0:64fe:5f0d:c4ae:7330]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 7FBE75C2E; Sun, 29 Mar 2015 22:52:33 +0200 (CEST) Subject: Re: Failed to build usr.bin/clang/clang with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_C1BF6574-52E3-4773-A6AB-00DD8BC70F06"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b6 From: Dimitry Andric In-Reply-To: Date: Sun, 29 Mar 2015 22:52:24 +0200 Message-Id: <09AB8734-8EE3-4772-84C6-49D9D4B6105B@FreeBSD.org> References: To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 20:52:38 -0000 --Apple-Mail=_C1BF6574-52E3-4773-A6AB-00DD8BC70F06 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 29 Mar 2015, at 22:39, Craig Rodrigues wrote: >=20 > When building with gcc 4.9, I am getting unresolved symbols at link > time when building usr.bin/clang/clang. Here is one error message: >=20 > = /usr/obj/opt2/branches/head/usr.bin/clang/clang/../../../lib/clang/libclan= gcodegen/libclang > codegen.a(ModuleBuilder.o): In function `(anonymous > = namespace)::CodeGeneratorImpl::HandleTranslationUnit(clang::ASTContext&)':= > ModuleBuilder.cpp:(.text+0x113): undefined reference to > `clang::CodeGen::CodeGenModule::clear()' >=20 > There are many more errors like that in my full build log here: >=20 > https://people.freebsd.org/~rodrigc/gcc/buildworld.2015_03_29.log.txt For some reason, many of your libraries aren't being built: >>> stage 4.2: building libraries ... =3D=3D=3D> lib/libwrap (all) =3D=3D=3D> lib/libxo (all) =3D=3D=3D> lib/liby (all) =3D=3D=3D> lib/atf (all) =3D=3D=3D> lib/atf/libatf-c (all) =3D=3D=3D> lib/atf/libatf-c++ (all) =3D=3D=3D> lib/clang (all) =3D=3D=3D> lib/clang/libclanganalysis (all) =3D=3D=3D> lib/clang/libclangarcmigrate (all) =3D=3D=3D> lib/clang/libclangast (all) =3D=3D=3D> lib/clang/libclangbasic (all) =3D=3D=3D> lib/clang/libclangcodegen (all) =3D=3D=3D> lib/clang/libclangdriver (all) =3D=3D=3D> lib/clang/libclangedit (all) =3D=3D=3D> lib/clang/libclangfrontend (all) And none of these prints any compilation command lines? Are you running with make -s, by any chance? If so, try removing it so we can see how the various source files are being compiled. Also, do any of the libclang*.a files under /usr/obj look sane? E.g., do they contain any object files, and if so, why are the symbols you showed missing? -Dimitry --Apple-Mail=_C1BF6574-52E3-4773-A6AB-00DD8BC70F06 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlUYZhAACgkQsF6jCi4glqPYqgCgiYvgWICwfeCqv/mMO7DUCUzM yWcAoLHPHUSQGqIZ665uziYfPyHdKk5y =pYh8 -----END PGP SIGNATURE----- --Apple-Mail=_C1BF6574-52E3-4773-A6AB-00DD8BC70F06-- From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 21:45:33 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5158CED4; Sun, 29 Mar 2015 21:45:33 +0000 (UTC) Received: from st11p02mm-asmtp002.mac.com (st11p02mm-asmtpout002.mac.com [17.172.220.237]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 222A8E29; Sun, 29 Mar 2015 21:45:32 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (c-73-162-13-215.hsd1.ca.comcast.net [73.162.13.215]) by st11p02mm-asmtp002.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NLZ00887TQY2050@st11p02mm-asmtp002.mac.com>; Sun, 29 Mar 2015 21:45:01 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-03-29_03:2015-03-28,2015-03-29,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1503290229 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 From: Rui Paulo In-reply-to: Date: Sun, 29 Mar 2015 14:44:58 -0700 Content-transfer-encoding: quoted-printable Message-id: References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> <20150329082734.GA13058@vlakno.cz> To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain , Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 21:45:33 -0000 On Mar 29, 2015, at 13:29, Craig Rodrigues wrote: >=20 > Just out of curiousity, what is it about newer compilers that cause > the size of boot2 to increase so much? Code generation is different, especially with regards to optimisations. = Longer code might be faster because the compiler decided to inline a few = functions. Unfortunately, I never saw any difference between -Os and = -O2 in all of my tests (boot2 and other code). -- Rui Paulo From owner-freebsd-toolchain@FreeBSD.ORG Sun Mar 29 23:04:55 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C70EBA91 for ; Sun, 29 Mar 2015 23:04:55 +0000 (UTC) Received: from mail-pa0-f46.google.com (mail-pa0-f46.google.com [209.85.220.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8EBC7917 for ; Sun, 29 Mar 2015 23:04:55 +0000 (UTC) Received: by padcy3 with SMTP id cy3so149145814pad.3 for ; Sun, 29 Mar 2015 16:04:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=DtdOJo3LkYCaxOGrMj8ccfwnzgTL+ffcxzLOCTlricg=; b=dwiMQdKmlwR1K4SUR2ZsZ4VzL2236l5J6CqAmnTjsXG5yrSHwKVuovAzVgrosV6Yil qWP3rEqgUp3pKJZWFMnGbZf1ZwCSNrOEnmgjUEz4c2uCHh7Kh8ByO7/W5aQwfGip2nXs dBEWIiQz7cu211vteiDQU6irc+GVUMjas9O2RV2iucD441PMIsnGSyevX3RA/KTFkdgx srbSm8ggY7nguqSGIiyG/WvMPVlUUJfY3TJHhgF3xiYuHNpvAkepv2CyGw7MuhwwlQhA ZDQHIRirdmPk9SfX++T9S4RB7JwvDlA+FT6AKl5GadweWOWo+rDbBriPtBNCt+of7CX3 xNiA== X-Gm-Message-State: ALoCoQmRZpbrZ4DQIyOyvijlrnoN9LmA6mD0qK03ccWf7uBrMR231TDwDdAQphNAWesAxuecmC+x X-Received: by 10.70.100.39 with SMTP id ev7mr53572371pdb.29.1427669813220; Sun, 29 Mar 2015 15:56:53 -0700 (PDT) Received: from lgwl-achen.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id d4sm8451263pdm.50.2015.03.29.15.56.51 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 29 Mar 2015 15:56:52 -0700 (PDT) Sender: Warner Losh Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_1EC3A099-7879-4FDA-830E-EFC1DD3D8E9F"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: Date: Sun, 29 Mar 2015 16:56:49 -0600 Message-Id: <7A9A90EA-E052-425E-BE90-9290B0CAB03F@bsdimp.com> References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> <20150329082734.GA13058@vlakno.cz> To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain , Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Mar 2015 23:04:55 -0000 --Apple-Mail=_1EC3A099-7879-4FDA-830E-EFC1DD3D8E9F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 > On Mar 29, 2015, at 2:29 PM, Craig Rodrigues = wrote: >=20 > On Sun, Mar 29, 2015 at 11:04 AM, Warner Losh wrote: >=20 > If we built a UFS1-only boot2, that would fit in the 7.5k we have left > to play with. We could then build a UFS2-only boot2 that would easily > fit in the like 32k limit that UFS2 has. >=20 > The only reason we went to supporting both was to have something > universal. Since it requires a reformat to go from UFS1 -> UFS2 we > wanted the transition to be as smooth as possible so you didn=92t have > to add boot blocks into the mix. >=20 > Now the only people that use UFS1 are people with really old systems > that are never going to upgrade, or people building new systems with > UFS1 because they are space constrained (for whatever reasons that > we=92re not going to debate here: they are still real). >=20 > In the past 5 years, I have worked on some embedded systems where UFS1 = was chosen because of very low memory and disk space requirements. > So those systems are real and out there. >=20 > Just out of curiousity, what is it about newer compilers that cause > the size of boot2 to increase so much? >=20 > Could we do some silly things like removing/reducing the use of = printf() > to save some more bytes, in order to buy us more time, before having > to rewrite everything? :) Removing printf isn=92t going to save us. It usually compiles to 80-120 = bytes. I think the only sane way forward is boot2.ufs1 an boot2.ufs2 plus maybe some safety belts in the boot block splatter programs to prevent brickification. Warner --Apple-Mail=_1EC3A099-7879-4FDA-830E-EFC1DD3D8E9F Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVGIMyAAoJEGwc0Sh9sBEA8lUP/itq1ITq5ycOuDbph6/xlXh3 OMKFzX3m8a2R8a0fXSO0SURNmwITRHCDlrJXOBege4SyAN51IQhu/tOxGlxHhnnG WRZ1QN3edlXKHRQ5EqmeEAyGQ7N0ZZbKTVp5l0utDdEhyNPB4tgumW92rYmzQWu7 icPbjLwQ3DMaXbLvUGpZLfRFXRy3lRbxVVId9ON4j3h7kxrmRXkPj6v4esuZ98Iu xImKXfUQdB6bCIztaaUMOdQrrqyBhYT+LCpCHO+7P545tjxoAaZGNOK/UgP7rvw4 P2yCN5Fspirdbfv8298omJmLkZE952Y2/dnR3paCGWJyESf7FNI8BM6XvppCrTCX N23P4GFMJuYyTlOO3yj/Q0R7U8GI8boqn98tKnAKcqcKmBONWXhJ2HaltUCsDDxV M/M6I8BN72A7JLKe884XZC20LEG8jT/VZIwM7hob/3MWdoCn1XHT7fJTVPxDpFAJ D1ksL2uXJxBEqu5Nm+tDJRDI4RJQ/wfY4nCUxzvZWq1WVVO4alTL5xvZDuY0tZah KT6baBrlmV2zZUzGJNXz3YpjWoeirNo+hs8/jbEMRKMWfu03PD5wptv0I4pkhx4w /4H0Hz4jeNZhGjyVZceZ84OwTAxFVmdP/9ubYY5UJiotLur979cf8+MyR2Snd+Le JOo0NThx9eU4kV8cFIFN =R4Z6 -----END PGP SIGNATURE----- --Apple-Mail=_1EC3A099-7879-4FDA-830E-EFC1DD3D8E9F-- From owner-freebsd-toolchain@FreeBSD.ORG Mon Mar 30 00:37:23 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B7C2467; Mon, 30 Mar 2015 00:37:23 +0000 (UTC) Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C4944164; Mon, 30 Mar 2015 00:37:22 +0000 (UTC) Received: by pdbni2 with SMTP id ni2so157971024pdb.1; Sun, 29 Mar 2015 17:37:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=EI0kd7C018moX8ljN0SoqGvJxqpkDIJjHi/qKRbIhpY=; b=WBkV5Qr3ydezjnuam1FtDythHDiuG7gV67+ztXO70akJMXfzL06eDH7AhMd1R6B+R3 sDrY4nrw6xm4IZLR5nDnwpWi640+cD9ixnGDwPuwp2HJ6MOeTl2mYOgTCt7Gt+PLgET8 Xqk+Ru1/BFyav/5sHhS5OQoJrX5ECCnClLBY4dRRfMll6ZvdYCN2G0Fob6tKWAaNsYsL 0n5M+JLgjrXRntsk5OMGJz5sOupEEBcvegqz9w6pCfVCARuCTjwvYoESiNke6NUS8JjA jnhgNlHVu7PW3PiKuGy/T8ejmI4RS3kgvZZeX3IqWZNGCPs/zqmYu7tjOX3QDlImbie/ PGOg== X-Received: by 10.68.90.132 with SMTP id bw4mr53347655pbb.102.1427675842160; Sun, 29 Mar 2015 17:37:22 -0700 (PDT) Received: from [192.168.20.11] (c-98-247-240-204.hsd1.wa.comcast.net. [98.247.240.204]) by mx.google.com with ESMTPSA id hs4sm8556193pbc.79.2015.03.29.17.37.20 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 29 Mar 2015 17:37:21 -0700 (PDT) References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> <20150329082734.GA13058@vlakno.cz> <7A9A90EA-E052-425E-BE90-9290B0CAB03F@bsdimp.com> Mime-Version: 1.0 (1.0) In-Reply-To: <7A9A90EA-E052-425E-BE90-9290B0CAB03F@bsdimp.com> Content-Type: text/plain; charset=cp932 Content-Transfer-Encoding: quoted-printable Message-Id: <32F42F43-0AFA-4562-B845-4612D123742E@gmail.com> X-Mailer: iPhone Mail (12D508) From: Garrett Cooper Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 Date: Sun, 29 Mar 2015 17:37:18 -0700 To: Warner Losh Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain , Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 00:37:23 -0000 > On Mar 29, 2015, at 15:56, Warner Losh wrote: >=20 >> On Mar 29, 2015, at 2:29 PM, Craig Rodrigues wrote:= >>=20 >> On Sun, Mar 29, 2015 at 11:04 AM, Warner Losh wrote: >>=20 >> If we built a UFS1-only boot2, that would fit in the 7.5k we have left >> to play with. We could then build a UFS2-only boot2 that would easily >> fit in the like 32k limit that UFS2 has. >>=20 >> The only reason we went to supporting both was to have something >> universal. Since it requires a reformat to go from UFS1 -> UFS2 we >> wanted the transition to be as smooth as possible so you didn=81ft have >> to add boot blocks into the mix. >>=20 >> Now the only people that use UFS1 are people with really old systems >> that are never going to upgrade, or people building new systems with >> UFS1 because they are space constrained (for whatever reasons that >> we=81fre not going to debate here: they are still real). >>=20 >> In the past 5 years, I have worked on some embedded systems where UFS1 wa= s chosen because of very low memory and disk space requirements. >> So those systems are real and out there. >>=20 >> Just out of curiousity, what is it about newer compilers that cause >> the size of boot2 to increase so much? >>=20 >> Could we do some silly things like removing/reducing the use of printf() >> to save some more bytes, in order to buy us more time, before having >> to rewrite everything? :) >=20 > Removing printf isn=81ft going to save us. It usually compiles to 80-120 b= ytes. >=20 > I think the only sane way forward is boot2.ufs1 an boot2.ufs2 plus maybe > some safety belts in the boot block splatter programs to prevent > brickification. Since the proposal to split up the code by filesystems is on the table, woul= d it make sense to do something similar for zfs? Thanks!= From owner-freebsd-toolchain@FreeBSD.ORG Mon Mar 30 03:52:13 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B8FB5FD2 for ; Mon, 30 Mar 2015 03:52:13 +0000 (UTC) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7DBB3927 for ; Mon, 30 Mar 2015 03:52:13 +0000 (UTC) Received: by pacgg7 with SMTP id gg7so25295167pac.0 for ; Sun, 29 Mar 2015 20:52:07 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=sMZSGRYLaJp6stMxonAVDTmz0AKvuyHLHSvchZBvfEQ=; b=mq2EI1RWqHG3BYEH0njaOTK8ryzJw7j2o7Ej8ZbZ1Y2wg3VGTmfcqQX1ZzuP6szdrr G/rxQOn52kLYqIR8AIrqd3VNpoBRK14TYed0kA80QB3wA4ujp43VsU4ovspRV20EAJxO LW7w9jm5zZjLK6Z0mdgFcryavm0R9YrRKbDQE/Ylbv1GHodg1/etG2wXrY9vuYWXfd7o hH70M0s+n0oM9Qr4BcrJg2OmvtdQXazO0N6QznMlkXTmvewOorDeaab/MGMoryMt6law IWezQaYd4sz8Oo7TUKMq44HfAh8q66cJG+0mEGyBvZElOr9OkCgzvbAxQowbixwY/3LP UuDA== X-Gm-Message-State: ALoCoQnNp2xI1cH/nHuKH2Ih+zeGDDQvklM7DFqVgvcw5LKvwfq/7+ehqP82rEcVCxuqX6iDIV33 X-Received: by 10.68.237.165 with SMTP id vd5mr54482239pbc.144.1427687527816; Sun, 29 Mar 2015 20:52:07 -0700 (PDT) Received: from lgwl-achen.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id gl2sm8852353pbc.52.2015.03.29.20.52.05 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 29 Mar 2015 20:52:06 -0700 (PDT) Sender: Warner Losh Subject: Re: Fails to build sys/i386/boot2 with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_18A0EAD2-F155-45FC-A4B3-A0A4DB254BBE"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: <32F42F43-0AFA-4562-B845-4612D123742E@gmail.com> Date: Sun, 29 Mar 2015 21:52:03 -0600 Message-Id: References: <20683705-0EBA-4B8F-A0CE-9C06B8003BBE@FreeBSD.org> <20150329082734.GA13058@vlakno.cz> <7A9A90EA-E052-425E-BE90-9290B0CAB03F@bsdimp.com> <32F42F43-0AFA-4562-B845-4612D123742E@gmail.com> To: Garrett Cooper X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain , Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 03:52:13 -0000 --Apple-Mail=_18A0EAD2-F155-45FC-A4B3-A0A4DB254BBE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=cp932 > On Mar 29, 2015, at 6:37 PM, Garrett Cooper = wrote: >=20 >>=20 >> On Mar 29, 2015, at 15:56, Warner Losh wrote: >>=20 >>> On Mar 29, 2015, at 2:29 PM, Craig Rodrigues = wrote: >>>=20 >>> On Sun, Mar 29, 2015 at 11:04 AM, Warner Losh = wrote: >>>=20 >>> If we built a UFS1-only boot2, that would fit in the 7.5k we have = left >>> to play with. We could then build a UFS2-only boot2 that would = easily >>> fit in the like 32k limit that UFS2 has. >>>=20 >>> The only reason we went to supporting both was to have something >>> universal. Since it requires a reformat to go from UFS1 -> UFS2 we >>> wanted the transition to be as smooth as possible so you didn=81ft = have >>> to add boot blocks into the mix. >>>=20 >>> Now the only people that use UFS1 are people with really old systems >>> that are never going to upgrade, or people building new systems with >>> UFS1 because they are space constrained (for whatever reasons that >>> we=81fre not going to debate here: they are still real). >>>=20 >>> In the past 5 years, I have worked on some embedded systems where = UFS1 was chosen because of very low memory and disk space requirements. >>> So those systems are real and out there. >>>=20 >>> Just out of curiousity, what is it about newer compilers that cause >>> the size of boot2 to increase so much? >>>=20 >>> Could we do some silly things like removing/reducing the use of = printf() >>> to save some more bytes, in order to buy us more time, before having >>> to rewrite everything? :) >>=20 >> Removing printf isn=81ft going to save us. It usually compiles to = 80-120 bytes. >>=20 >> I think the only sane way forward is boot2.ufs1 an boot2.ufs2 plus = maybe >> some safety belts in the boot block splatter programs to prevent >> brickification. >=20 > Since the proposal to split up the code by filesystems is on the = table, would it make sense to do something similar for zfs? > Thanks! zfs isn=81ft in boot2 by default, just ufs1 and ufs2, so I on=81ft = understand the question. Warner --Apple-Mail=_18A0EAD2-F155-45FC-A4B3-A0A4DB254BBE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVGMhkAAoJEGwc0Sh9sBEAFHUP/3UsnL3nIxS3QFrmIaOiz0K1 qJgpojqBhPGpTIoc01Sixh4WUJUk16J7hL5e3iDITrR10NkWYn+bYGYvG+/kEZfR gfX9N1vMmBlc39OvUANgoDd5lJZ2slI9Jp2PEwcr1gh/ofS2G1OwZkcVcd2xc478 pwpGI35i0V5yB547t3BFEnwmY1bjNvZyYfhA8Kkk/MNmytufwmm196mjetBsgWO+ vvQXbLIbRCJ6ZaIVqom4hceJwRzwLxaSyttssIkB+N/wMC+RDizjeBhx8+Rg1nTT aFSka9uThEkeikrTRfWA5Md+PF+s194AEKdfXOLLktYnJip+/5nGseloz+X4j01n ul6ZMhZEZNPqX6enI3jVa1GK7XnQAyaAfZMcXpSOdqlLlrqalDA0ibntbhpr5cw4 atkN9xzMO38RBTTm9cijobpWZTONT+pT4Gc+Rmy+ppVshawWeRha6WlX8/ZbX4xb y6avqi7y3i4Nx348LBbh7vfDxsP4xel/H7nNp67JJEVegkCOmEFaCp3+jZd8Hyfx 1yrFARzYCHTErAnzvQXOy0cSUxllajXx1J+GaXewGI66sdXaf0Gku3ixTfvksHd+ dBuCDN+VXQaDFs6hpCTYP2Upzv+HDXaPLvdcZfbeZ2ujRjhUmOOWFkuSMBKvhxxY zGNzO4fKDKE9Iy9IkWRH =6RBF -----END PGP SIGNATURE----- --Apple-Mail=_18A0EAD2-F155-45FC-A4B3-A0A4DB254BBE-- From owner-freebsd-toolchain@FreeBSD.ORG Mon Mar 30 16:08:05 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 31693B27; Mon, 30 Mar 2015 16:08:05 +0000 (UTC) Received: from mail-la0-x22c.google.com (mail-la0-x22c.google.com [IPv6:2a00:1450:4010:c03::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A5371883; Mon, 30 Mar 2015 16:08:04 +0000 (UTC) Received: by lajy8 with SMTP id y8so6918419laj.0; Mon, 30 Mar 2015 09:08:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=aFdpCm5X89FcLNw6her0/26SjRBHPSycF4amyEohwjw=; b=kDqxAne6GPsQxdeblTCgkl0P8cH7vx5rWxMiGBV4enGvdiKHSbklsJSXd5W+lISpuv jQ1JaWpPlmNNOI4qCP7ooT1PkP15b+5uMTqlfPWnYU8n/ZjgmicJqFUMsBw6ENLLZepf PH+DzrZtFcQfR+V84MYB4eQ0AeCoEUumU8BMDFbcRxX5Li7h6GJeVtOttJNqzWzv4kTv NNh6aBwiuQTDbZrgagLfBFPNBwjMwGLK4vlETbM4XndPDu+0OhavsCZrT6sEuj7wnCHA 7rlpOAj9cqZFdxZHKXDq+2Vr0PieyXJugCGOSGPacKwTPVVe39GgQRt3z1mvY7iNMC8W hUdQ== MIME-Version: 1.0 X-Received: by 10.112.26.209 with SMTP id n17mr27042106lbg.84.1427731682836; Mon, 30 Mar 2015 09:08:02 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Mon, 30 Mar 2015 09:08:02 -0700 (PDT) In-Reply-To: <09AB8734-8EE3-4772-84C6-49D9D4B6105B@FreeBSD.org> References: <09AB8734-8EE3-4772-84C6-49D9D4B6105B@FreeBSD.org> Date: Mon, 30 Mar 2015 09:08:02 -0700 X-Google-Sender-Auth: 24RZnbdNDgl239dEXF4kJ_L6odw Message-ID: Subject: Re: Failed to build usr.bin/clang/clang with gcc 4.9 From: Craig Rodrigues To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 16:08:05 -0000 On Sun, Mar 29, 2015 at 1:52 PM, Dimitry Andric wrote: > > > And none of these prints any compilation command lines? Are you running > with make -s, by any chance? If so, try removing it so we can see how > the various source files are being compiled. I am not using make -s. If you look at the log file, the full make invocation I used is captured at the top of the log file. I used NO_CLEAN and NO_KERNELCLEAN. I wiped out the object tree, and tried again. I managed to successfully buildworld, as long as I skipped building all the boot directories. Here is the new log file: https://people.freebsd.org/~rodrigc/gcc/buildworld.2015_03_29_2.log.txt There are many warnings which need to be cleaned up over time. I saw this one which looked a bit weird: /usr/local/bin/x86_64-freebsd-ld: error in /usr/obj/opt2/branches/head/lib32/usr/lib32/crt1.o(.eh_frame); no .eh_frame_hdr table will be created. -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Mon Mar 30 17:38:46 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2E3865D8 for ; Mon, 30 Mar 2015 17:38:46 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D70D7AF for ; Mon, 30 Mar 2015 17:38:46 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2UHcjZ8051389 for ; Mon, 30 Mar 2015 17:38:45 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2UHcjru051388; Mon, 30 Mar 2015 17:38:45 GMT (envelope-from root) Date: Mon, 30 Mar 2015 17:38:45 +0000 To: freebsd-toolchain@freebsd.org From: "emaste (Ed Maste)" Subject: [Differential] [Closed] D2156: Switch to ELF toolchain readelf Message-ID: X-Priority: 3 Thread-Topic: D2156: Switch to ELF toolchain readelf X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZWFkMTA4MTdiZGZmMTA5ZWZhZDAyYzE2ZjY0IFUZiiU= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 17:38:46 -0000 emaste closed this revision. emaste updated this revision to Diff 4515. emaste added a comment. Closed by commit rS280859 (authored by @emaste). CHANGED PRIOR TO COMMIT https://reviews.freebsd.org/D2156?vs=4461&id=4515#toc REVISION DETAIL https://reviews.freebsd.org/D2156 AFFECTED FILES head/gnu/usr.bin/binutils/Makefile head/usr.bin/Makefile To: emaste, imp, bapt, rpaulo Cc: freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Mon Mar 30 23:20:03 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id AA4D0514 for ; Mon, 30 Mar 2015 23:20:03 +0000 (UTC) Received: from mail1.sandvine.com (mail1.sandvine.com [64.7.137.165]) by mx1.freebsd.org (Postfix) with ESMTP id 5D20895A for ; Mon, 30 Mar 2015 23:20:03 +0000 (UTC) Received: from BLR-EXCHP-2.sandvine.com (192.168.196.172) by WTL-EXCHP-3.sandvine.com (192.168.196.177) with Microsoft SMTP Server (TLS) id 14.3.195.1; Mon, 30 Mar 2015 19:18:56 -0400 Received: from WTL-EXCHP-1.sandvine.com ([fe80::ac6b:cc1e:f2ff:93aa]) by blr-exchp-2.sandvine.com ([fe80::6c6d:7108:c63c:9055%14]) with mapi id 14.03.0181.006; Mon, 30 Mar 2015 19:18:55 -0400 From: Kenan Ali To: "freebsd-toolchain@freebsd.org" Subject: Compiling LLDB Thread-Topic: Compiling LLDB Thread-Index: AdBrPsPugm7kiNiFT1Gd7TmEVsRA+w== Date: Mon, 30 Mar 2015 23:18:54 +0000 Message-ID: <9A38D7D9218ED246802DA890D11AF6120EF108@wtl-exchp-1.sandvine.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.200.113] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Mar 2015 23:20:03 -0000 Hi, I would like to see if I could get involved with contributing to the kernel= core support for LLDB under FreeBSD. I'm running a FreeBSD-head build (on = a VM) from a week or two ago, and I'm following the instructions from here:= https://wiki.freebsd.org/lldb Once I get to the 'ninja lldb' step, it seems that I always end up with the= following error: CC: error: unable to execute command: Killed CC: error: linker command failed due to signal (use -v to see invocation) Ninja: build stopped: subcommand failed. I've tried passing the '-v' flag to ninja, which lists a large invocation b= efore spewing out the errors above. However, I cannot seem to figure out ho= w to get the '-v' command passed to LLVM's linker. Neither ninja's help out= put or some basic Googling seem to be helping me diagnose this issue, so I = was wondering if anyone here could help? From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 01:53:41 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 079625D8 for ; Tue, 31 Mar 2015 01:53:41 +0000 (UTC) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C91FEBD4 for ; Tue, 31 Mar 2015 01:53:40 +0000 (UTC) Received: by iedfl3 with SMTP id fl3so5494809ied.1 for ; Mon, 30 Mar 2015 18:53:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=IKjmz5R62guuMwc90v1EZtWfsmCvgcTwWboCohwGV3g=; b=tUKL96SFKz0sfQ8OjUnb0g4QYLPRXRA7j8HoAR+pyJn9Ib5VHCyM9Ar/OZCFxuo8U8 9kwFY/zcierJOXARVDHqM+2EvDCKnbjtzKmHqnfd2xpPwZ++RE59A5TqlYCZSY3gEC8d 7dmRUYlkumUXymoXLLwXCzAPrDDySRniA1eMrjWweLemrfEpHSTeBKjtA78/svjPVZNI ePiC5wLrjmAGIgQB5+RQVna8o43AS/Oqc7p9xlC84Psj4U6QtJjDPgoxqrbObG5hAd6s tzY28h4/fLsTfxkqzmS3mNe5V5ploSUfYQxXtFmydUj95et729BwTvOqUs8xF675DWcT 7VNQ== X-Received: by 10.107.15.155 with SMTP id 27mr53109059iop.49.1427766819941; Mon, 30 Mar 2015 18:53:39 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.158.19 with HTTP; Mon, 30 Mar 2015 18:53:19 -0700 (PDT) In-Reply-To: <9A38D7D9218ED246802DA890D11AF6120EF108@wtl-exchp-1.sandvine.com> References: <9A38D7D9218ED246802DA890D11AF6120EF108@wtl-exchp-1.sandvine.com> From: Ed Maste Date: Mon, 30 Mar 2015 21:53:19 -0400 X-Google-Sender-Auth: G7BLmxYt4T66wN0QSlGYu06ulgs Message-ID: Subject: Re: Compiling LLDB To: Kenan Ali Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-toolchain@freebsd.org" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 01:53:41 -0000 On 30 March 2015 at 19:18, Kenan Ali wrote: > Hi, > > I would like to see if I could get involved with contributing to the kern= el core support for LLDB under FreeBSD. I'm running a FreeBSD-head build (o= n a VM) from a week or two ago, and I'm following the instructions from her= e: https://wiki.freebsd.org/lldb > > Once I get to the 'ninja lldb' step, it seems that I always end up with t= he following error: > > CC: error: unable to execute command: Killed > CC: error: linker command failed due to signal (use -v to see invocation) > Ninja: build stopped: subcommand failed. > > I've tried passing the '-v' flag to ninja, which lists a large invocation= before spewing out the errors above. However, I cannot seem to figure out = how to get the '-v' command passed to LLVM's linker. Neither ninja's help o= utput or some basic Googling seem to be helping me diagnose this issue, so = I was wondering if anyone here could help? I'd suggest checking /var/log/messages for further information. Is this i386 or amd64, how much memory does your build host have, and are you compiling with debug information or no? If had to guess, you're running out of memory (or running into ulimit) during linking, and the process is being killed as a result. From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 09:01:30 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E1C2F30C; Tue, 31 Mar 2015 09:01:30 +0000 (UTC) Received: from theravensnest.org (theraven.freebsd.your.org [216.14.102.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "cloud.theravensnest.org", Issuer "StartCom Class 1 Primary Intermediate Server CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id A4C8B7B; Tue, 31 Mar 2015 09:01:29 +0000 (UTC) Received: from [192.168.0.7] (cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61]) (authenticated bits=0) by theravensnest.org (8.15.1/8.14.9) with ESMTPSA id t2V8rqK8085863 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Mar 2015 09:01:23 GMT (envelope-from theraven@FreeBSD.org) X-Authentication-Warning: theravensnest.org: Host cpc16-cmbg15-2-0-cust60.5-4.cable.virginm.net [86.5.162.61] claimed to be [192.168.0.7] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Compiling LLDB From: David Chisnall In-Reply-To: Date: Tue, 31 Mar 2015 09:41:49 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9A38D7D9218ED246802DA890D11AF6120EF108@wtl-exchp-1.sandvine.com> To: Ed Maste X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-toolchain@freebsd.org" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 09:01:31 -0000 On 31 Mar 2015, at 02:53, Ed Maste wrote: >=20 > I'd suggest checking /var/log/messages for further information. Is > this i386 or amd64, how much memory does your build host have, and are > you compiling with debug information or no? If had to guess, you're > running out of memory (or running into ulimit) during linking, and the > process is being killed as a result. Ninja defaults to using a large number of concurrent processes, which = can exacerbate this. If you are on a 32-bit system, or only have 4GB or = so of RAM (or have <2GB per core), you may want to explicitly do ninja = -j1 to get a serial build. Your best bet is probably something like: $ ninja -k100 $ ninja -j1 The first will do a parallel build of everything that doesn't crash. = The second will do a serial build of whatever's left. It's also = possible to configure different pools for Ninja, though I'm not sure = that this is exposed via the CMake interface yet. This mechanism exists = to allow you to say things like 'only run one link job at a time', which = can improve matters. You may also find that using gold from ports (or = possibly lld, which I believe can now link lldb) will improve matters. David From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 17:17:10 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4E88C710; Tue, 31 Mar 2015 17:17:10 +0000 (UTC) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BE71F62A; Tue, 31 Mar 2015 17:17:09 +0000 (UTC) Received: by lbbzk7 with SMTP id zk7so1334820lbb.0; Tue, 31 Mar 2015 10:17:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=DV3A2TLdY2nLED5Qsv5sFSedoDLDh+ePzh2h1kltk+Y=; b=k4lurGGdHab8IMw347Zb52T9vJwD5sNWfsW20lYg7yQGQYl1fmaqoxEaL6HaialEzq WL1IY26R/wb8XwSSov4Wu2qQmr0wrIyta6qpAbr3fCNoUvezTCsHK64KMWbY7KHQPA7X 9O6LPIqaHvKTb/CUgxsL9Jp/Y5is7tJsOvs5X8tpSMOGxX12oF0cNjQTec5wezWxxVfP KcaGZhTXbedqxNc0to6X+ZMLT+hl4IFT2B0pv2v5JT+e550pLFYX692g+0+AJJ4/Xdzx IO82+0rFVW+SxKZ1DI8AQmhUSL7nfjx+SG8x6aqREiTMlpT52WyMQ/92nlOHP3Kfi+cK JOag== MIME-Version: 1.0 X-Received: by 10.152.234.108 with SMTP id ud12mr31826335lac.81.1427822227736; Tue, 31 Mar 2015 10:17:07 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Tue, 31 Mar 2015 10:17:07 -0700 (PDT) In-Reply-To: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> Date: Tue, 31 Mar 2015 10:17:07 -0700 X-Google-Sender-Auth: 9PNOY5RVA2ryP3lv21f-mECJIp4 Message-ID: Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import From: Craig Rodrigues To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 17:17:10 -0000 On Mon, Mar 23, 2015 at 12:12 AM, Dimitry Andric wrote: > > On 23 Mar 2015, at 01:49, Craig Rodrigues wrote: > > > > Hi, > > > > I tried to build HEAD with gcc 4.9.1 after the latest clang 3.6.0 import, > > and am getting > > new build failures related to C++ such as: > > > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/include/c++/v1/type_traits:881:87: > > error: use of deleted function > > 'clang::Sema::TypoExprState::TypoExprState(const > > clang::Sema::TypoExprState&)' > > > > sizeof(__is_convertible_imp::__test<_T2>(__is_convertible_imp::__source<_T1>())) > > == 1 > > > > See full build logs here: > > https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/21/console > > > > Any ideas what the problem might be? > > Yes, this is a bug in libc++, when compiling it with newer versions of > gcc. I reported this upstream some time ago: https://llvm.org/PR22771 > > Still haven't had enough time to test Eric Fiselier's patch for it. I > hope I see the bottom of my TODO list anytime soon... > > -Dimitry > Hi, I just updated my tree to include your latest fixes such as r28064. I'm still getting this: from /builds/FreeBSD_HEAD_external_toolchain_gcc/lib/clang/libclangast/../../../contrib/llvm/tools/clang/lib/AST/DeclBase.cpp:14: /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/include/c++/v1/type_traits:845:28: error: initializing argument 1 of 'char std::__1::__is_convertible_imp::__test(_Tp) [with _Tp = clang::StoredDeclsList]' template char __test(_Tp); ^ *** [DeclBase.o] Error code 1 make[6]: stopped in /builds/FreeBSD_HEAD_external_toolchain_gcc/lib/clang/libclangast Any ideas? See: https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/27/console -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 18:13:55 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D5C091C; Tue, 31 Mar 2015 18:13:55 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 27479D6C; Tue, 31 Mar 2015 18:13:54 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::e062:65ef:5878:a9d3] (unknown [IPv6:2001:7b8:3a7:0:e062:65ef:5878:a9d3]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 6064F5C2E; Tue, 31 Mar 2015 20:13:45 +0200 (CEST) Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_4F11C213-DF08-46ED-B591-D011577B147C"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b6 From: Dimitry Andric In-Reply-To: Date: Tue, 31 Mar 2015 20:13:32 +0200 Message-Id: References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 18:13:55 -0000 --Apple-Mail=_4F11C213-DF08-46ED-B591-D011577B147C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 31 Mar 2015, at 19:17, Craig Rodrigues wrote: >=20 > On Mon, Mar 23, 2015 at 12:12 AM, Dimitry Andric = wrote: ... > > Yes, this is a bug in libc++, when compiling it with newer versions = of > > gcc. I reported this upstream some time ago: = https://llvm.org/PR22771 > > > > Still haven't had enough time to test Eric Fiselier's patch for it. = I > > hope I see the bottom of my TODO list anytime soon... > > > > -Dimitry > > >=20 > Hi, >=20 > I just updated my tree to include your latest fixes such as r28064. >=20 > I'm still getting this: >=20 > from = /builds/FreeBSD_HEAD_external_toolchain_gcc/lib/clang/libclangast/../../..= /contrib/llvm/tools/clang/lib/AST/DeclBase.cpp:14: > = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/tmp/usr/include/c++/v1/type_traits:845:28: error: = initializing argument 1 of 'char = std::__1::__is_convertible_imp::__test(_Tp) [with _Tp =3D = clang::StoredDeclsList]' > template char __test(_Tp); > ^ > *** [DeclBase.o] Error code 1 >=20 > make[6]: stopped in = /builds/FreeBSD_HEAD_external_toolchain_gcc/lib/clang/libclangast >=20 > Any ideas? Yes, see your log: Started by user rodrigc Building remotely on jenkins10a.freebsd.org (FreeBSD-10) in workspace = /builds/FreeBSD_HEAD_external_toolchain_gcc Updating svn://svn.freebsd.org/base/head at revision = '2015-03-31T00:49:32.815 +0000' [...] G contrib/libc++/include/type_traits U contrib/libarchive/libarchive/archive_read_disk_posix.c At revision 280872 [...] but then: + patch Hmm... Looks like a unified diff to me... The text leading up to this was: -------------------------- |Index: contrib/libc++/include/type_traits |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D |--- contrib/libc++/include/type_traits (revision 280762) |+++ contrib/libc++/include/type_traits (working copy) -------------------------- Patching file contrib/libc++/include/type_traits using Plan A... Reversed (or previously applied) patch detected! Assume -R? [y] Hunk #1 succeeded at 842. Hunk #2 succeeded at 877. Hmm... Ignoring the trailing garbage. done E.g., it undoes the change to type_traits that was merged in the = subversion update. -Dimitry --Apple-Mail=_4F11C213-DF08-46ED-B591-D011577B147C Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlUa49cACgkQsF6jCi4glqOY0QCcCwb1SxmlXjV1WmLLXzRZCGcX gWUAoNuMWe/0rLL2X2wzDIMMh+dq/3Eo =YR6C -----END PGP SIGNATURE----- --Apple-Mail=_4F11C213-DF08-46ED-B591-D011577B147C-- From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 18:20:13 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 438CAB07; Tue, 31 Mar 2015 18:20:13 +0000 (UTC) Received: from tensor.andric.com (unknown [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EEBA7E08; Tue, 31 Mar 2015 18:20:12 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::e062:65ef:5878:a9d3] (unknown [IPv6:2001:7b8:3a7:0:e062:65ef:5878:a9d3]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 283B05C2E; Tue, 31 Mar 2015 20:20:08 +0200 (CEST) Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_BC62B6B8-0EC4-4E0D-93FA-38B32C1B0F80"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b6 From: Dimitry Andric In-Reply-To: Date: Tue, 31 Mar 2015 20:20:07 +0200 Message-Id: References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 18:20:13 -0000 --Apple-Mail=_BC62B6B8-0EC4-4E0D-93FA-38B32C1B0F80 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 31 Mar 2015, at 20:13, Dimitry Andric wrote: ... > but then: >=20 > + patch > Hmm... Looks like a unified diff to me... > The text leading up to this was: > -------------------------- > |Index: contrib/libc++/include/type_traits > |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > |--- contrib/libc++/include/type_traits (revision 280762) > |+++ contrib/libc++/include/type_traits (working copy) > -------------------------- > Patching file contrib/libc++/include/type_traits using Plan A... > Reversed (or previously applied) patch detected! Assume -R? [y] > Hunk #1 succeeded at 842. > Hunk #2 succeeded at 877. > Hmm... Ignoring the trailing garbage. > done >=20 > E.g., it undoes the change to type_traits that was merged in the = subversion update. Btw, please use patch -f for this, so it will error out, instead of accidentally reversing a patch. -Dimitry --Apple-Mail=_BC62B6B8-0EC4-4E0D-93FA-38B32C1B0F80 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlUa5VcACgkQsF6jCi4glqMkIACfaw2dUgF9cb7OqvXXI6ATwsHc I3cAoIadYMqkWmZY/fb4smWvZ3n93Lag =CqmC -----END PGP SIGNATURE----- --Apple-Mail=_BC62B6B8-0EC4-4E0D-93FA-38B32C1B0F80-- From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 19:38:03 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 921DFD4; Tue, 31 Mar 2015 19:38:03 +0000 (UTC) Received: from mail-lb0-x231.google.com (mail-lb0-x231.google.com [IPv6:2a00:1450:4010:c04::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0EB77A94; Tue, 31 Mar 2015 19:38:03 +0000 (UTC) Received: by lboc7 with SMTP id c7so20400027lbo.1; Tue, 31 Mar 2015 12:38:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=ycYNczISryhkpxPrSCr6pL4R8uX0S/oVxw527qr3cNw=; b=yQi82iTXqm1NSDtyF5ojC0JeARQwDhV5Yeo3OIsKejmVzzifescC4Kq6yQ2d3G1eba vKGIi1p+Te7lsZv6J3EA/bsavqAzvLC3GOlye/giyyYyNgPptO+LCUJh+YGo+/drxZYN MGNxgT1Hq+gNfyUVsVkSQZEVNrojMJP/UReEK9rz6E0b8fwfM7dmy7YVJYBmcsGbag7B Lf/xOIjFyimOz1ecfJ5ZFqd1oPrc0Uoao9nt4RkEijvOY5rw9RxYS8J7SRrF8N0AK0YE FSAY+yObJ9KhhnH01GwlcNXdy4aBtjClAPgcCJPH46FGq1Ttg42yseoNV/SXjjubG3RA rm9Q== MIME-Version: 1.0 X-Received: by 10.152.163.2 with SMTP id ye2mr5738350lab.89.1427830681127; Tue, 31 Mar 2015 12:38:01 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Tue, 31 Mar 2015 12:38:01 -0700 (PDT) In-Reply-To: References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> Date: Tue, 31 Mar 2015 12:38:01 -0700 X-Google-Sender-Auth: 3MQaGLn54dWTXPvOa6U9FagufJM Message-ID: Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import From: Craig Rodrigues To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 19:38:03 -0000 On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric wrote: > On 31 Mar 2015, at 20:13, Dimitry Andric wrote: > ... > > but then: > > > > + patch > > Hmm... Looks like a unified diff to me... > > The text leading up to this was: > > -------------------------- > > |Index: contrib/libc++/include/type_traits > > |=================================================================== > > |--- contrib/libc++/include/type_traits (revision 280762) > > |+++ contrib/libc++/include/type_traits (working copy) > > -------------------------- > > Patching file contrib/libc++/include/type_traits using Plan A... > > Reversed (or previously applied) patch detected! Assume -R? [y] > > Hunk #1 succeeded at 842. > > Hunk #2 succeeded at 877. > > Hmm... Ignoring the trailing garbage. > > done > > > > E.g., it undoes the change to type_traits that was merged in the > subversion update. > > OK, I undid the patch. Now the clang and libc++ parts build, but I'm still getting problems building rescue: https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/29/console -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 19:48:44 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A0B5E410; Tue, 31 Mar 2015 19:48:44 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 559CABFE; Tue, 31 Mar 2015 19:48:44 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::e062:65ef:5878:a9d3] (unknown [IPv6:2001:7b8:3a7:0:e062:65ef:5878:a9d3]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id DE37A5C2E; Tue, 31 Mar 2015 21:48:41 +0200 (CEST) Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_26FD496B-F52B-4A56-A9FE-4C104843AB22"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b6 From: Dimitry Andric In-Reply-To: Date: Tue, 31 Mar 2015 21:48:30 +0200 Message-Id: <5B103C77-EA63-4C04-95FE-B138CF46F01C@FreeBSD.org> References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 19:48:44 -0000 --Apple-Mail=_26FD496B-F52B-4A56-A9FE-4C104843AB22 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii On 31 Mar 2015, at 21:38, Craig Rodrigues wrote: >=20 > On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric = wrote: >=20 >> On 31 Mar 2015, at 20:13, Dimitry Andric wrote: >> ... >>> but then: >>>=20 >>> + patch >>> Hmm... Looks like a unified diff to me... >>> The text leading up to this was: >>> -------------------------- >>> |Index: contrib/libc++/include/type_traits >>> |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>> |--- contrib/libc++/include/type_traits (revision 280762) >>> |+++ contrib/libc++/include/type_traits (working copy) >>> -------------------------- >>> Patching file contrib/libc++/include/type_traits using Plan A... >>> Reversed (or previously applied) patch detected! Assume -R? [y] >>> Hunk #1 succeeded at 842. >>> Hunk #2 succeeded at 877. >>> Hmm... Ignoring the trailing garbage. >>> done >>>=20 >>> E.g., it undoes the change to type_traits that was merged in the >> subversion update. >>=20 >>=20 > OK, I undid the patch. Now the clang and libc++ parts build, but I'm > still getting problems building rescue: >=20 > = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/29/con= sole Hm, that is strange. I have just completed a build with amd64-xtoolchain-gcc, and apart from boot2, everything worked... What does readelf say when you run it on the cat.lo file which is complained about in the log? And what happens if you delete it, and restart the build? -Dimitry --Apple-Mail=_26FD496B-F52B-4A56-A9FE-4C104843AB22 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlUa+hgACgkQsF6jCi4glqNRAQCdHXqzyRYb742ai7Z3+PBKEs4Y j4IAoIgiiMuotuwzph2zH8jVkwkQENV2 =rkRX -----END PGP SIGNATURE----- --Apple-Mail=_26FD496B-F52B-4A56-A9FE-4C104843AB22-- From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 20:06:10 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1AE71B31; Tue, 31 Mar 2015 20:06:10 +0000 (UTC) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A023E6D; Tue, 31 Mar 2015 20:06:09 +0000 (UTC) Received: by lagg8 with SMTP id g8so21345300lag.1; Tue, 31 Mar 2015 13:06:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=UWtsFIuY4sNHZlNVEtoSkn11sC+LhbgaAjj1iiHX8QY=; b=SDIS+9/AwOnT6imrel38rbIt2krPD1+og7gljtxJPGfBF/JRXpmV3STV2UTNAQTY6M giOq4weFQMK01m4y6NrBnCpRZJ9KZr2dEDGJrwFIvM//pDT27IAPV6Ah1Yvrc8dlj9eh I/Z9UOB33qpdsH33PFrX1sACM+s0dG1xUmMR8ubsphQ8EisiWvw9JovsBqmHftj4kTAS S8+7ZHJ5huBAmMZ60Awhx36wEJV1PO9OIPalyu5lzQby9CDfHrwqzExnNlrHCXLhUM2t Or6XMhCAZu5P8lcBTWZG6nxIxz+yMo62rUQ5ztYNk926dOAMq9voZr/7IUyoVJk01wj7 //mA== MIME-Version: 1.0 X-Received: by 10.152.120.163 with SMTP id ld3mr15872649lab.59.1427832367756; Tue, 31 Mar 2015 13:06:07 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Tue, 31 Mar 2015 13:06:07 -0700 (PDT) In-Reply-To: <5B103C77-EA63-4C04-95FE-B138CF46F01C@FreeBSD.org> References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> <5B103C77-EA63-4C04-95FE-B138CF46F01C@FreeBSD.org> Date: Tue, 31 Mar 2015 13:06:07 -0700 X-Google-Sender-Auth: X3OijqC1bDxXGZD6q0Rg7bTWrn4 Message-ID: Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import From: Craig Rodrigues To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 20:06:10 -0000 On Tue, Mar 31, 2015 at 12:48 PM, Dimitry Andric wrote: > On 31 Mar 2015, at 21:38, Craig Rodrigues wrote: > > > > On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric > wrote: > > > >> On 31 Mar 2015, at 20:13, Dimitry Andric wrote: > >> ... > >>> but then: > >>> > >>> + patch > >>> Hmm... Looks like a unified diff to me... > >>> The text leading up to this was: > >>> -------------------------- > >>> |Index: contrib/libc++/include/type_traits > >>> |=================================================================== > >>> |--- contrib/libc++/include/type_traits (revision 280762) > >>> |+++ contrib/libc++/include/type_traits (working copy) > >>> -------------------------- > >>> Patching file contrib/libc++/include/type_traits using Plan A... > >>> Reversed (or previously applied) patch detected! Assume -R? [y] > >>> Hunk #1 succeeded at 842. > >>> Hunk #2 succeeded at 877. > >>> Hmm... Ignoring the trailing garbage. > >>> done > >>> > >>> E.g., it undoes the change to type_traits that was merged in the > >> subversion update. > >> > >> > > OK, I undid the patch. Now the clang and libc++ parts build, but I'm > > still getting problems building rescue: > > > > > https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/29/console > > Hm, that is strange. I have just completed a build with > amd64-xtoolchain-gcc, and apart from boot2, everything worked... > > What does readelf say when you run it on the cat.lo file which is > complained about in the log? And what happens if you delete it, and > restart the build? > See: https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 20:41:20 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B5812F0; Tue, 31 Mar 2015 20:41:20 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB21F334; Tue, 31 Mar 2015 20:41:19 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::e062:65ef:5878:a9d3] (unknown [IPv6:2001:7b8:3a7:0:e062:65ef:5878:a9d3]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id D1E385C2E; Tue, 31 Mar 2015 22:41:17 +0200 (CEST) Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_2916CDB8-4F2A-42C6-9023-D632F101B8AA"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b6 From: Dimitry Andric In-Reply-To: Date: Tue, 31 Mar 2015 22:41:09 +0200 Message-Id: References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> <5B103C77-EA63-4C04-95FE-B138CF46F01C@FreeBSD.org> To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 20:41:20 -0000 --Apple-Mail=_2916CDB8-4F2A-42C6-9023-D632F101B8AA Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 31 Mar 2015, at 22:06, Craig Rodrigues wrote: >=20 > On Tue, Mar 31, 2015 at 12:48 PM, Dimitry Andric = wrote: > On 31 Mar 2015, at 21:38, Craig Rodrigues wrote: > > > > On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric = wrote: > > > >> On 31 Mar 2015, at 20:13, Dimitry Andric wrote: > >> ... > >>> but then: > >>> > >>> + patch > >>> Hmm... Looks like a unified diff to me... > >>> The text leading up to this was: > >>> -------------------------- > >>> |Index: contrib/libc++/include/type_traits > >>> = |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > >>> |--- contrib/libc++/include/type_traits (revision 280762) > >>> |+++ contrib/libc++/include/type_traits (working copy) > >>> -------------------------- > >>> Patching file contrib/libc++/include/type_traits using Plan A... > >>> Reversed (or previously applied) patch detected! Assume -R? [y] > >>> Hunk #1 succeeded at 842. > >>> Hunk #2 succeeded at 877. > >>> Hmm... Ignoring the trailing garbage. > >>> done > >>> > >>> E.g., it undoes the change to type_traits that was merged in the > >> subversion update. > >> > >> > > OK, I undid the patch. Now the clang and libc++ parts build, but = I'm > > still getting problems building rescue: > > > > = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/29/con= sole >=20 > Hm, that is strange. I have just completed a build with > amd64-xtoolchain-gcc, and apart from boot2, everything worked... >=20 > What does readelf say when you run it on the cat.lo file which is > complained about in the log? And what happens if you delete it, and > restart the build? >=20 > See: > = https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.ht= ml I'm suspecting this might have something to do with crunchide, or least, the copy of crunchide that is run for this: --- cat.lo --- /usr/local/x86_64-freebsd/bin/ld -dc -r -o cat.lo cat_stub.o = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue//builds/FreeBSD_HEAD_external_toolchain_gcc= /bin/cat/cat.o crunchide -k _crunched_cat_stub cat.lo If I look at my own build logs, it seems to pick the crunchide executable in /usr/bin, and Makefile.inc1 does *not* build it during the cross-tools stage if ${TARGET_ARCH} is the same as ${MACHINE_ARCH}: .if ${TARGET_ARCH} !=3D ${MACHINE_ARCH} .if ${MK_RESCUE} !=3D "no" || defined(RELEASEDIR) _crunchide=3D usr.sbin/crunch/crunchide .endif However, this does not explain why my /usr/bin/crunchide seems to not screw up cat.lo, while yours does. As far as I can see, we're both building this on a stable/10 amd64 box... Maybe, as a hack, you can force cross-tools to build crunchide, by patching Makefile.inc1 to ignore the arch check, and see what that results in? -Dimitry --Apple-Mail=_2916CDB8-4F2A-42C6-9023-D632F101B8AA Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlUbBmwACgkQsF6jCi4glqP1YgCaApVuba12Mk2MEgu5bZPE5C9Q 1O0AoMdPRUEX/XXpoKI5luqUgBooMhyl =c1P8 -----END PGP SIGNATURE----- --Apple-Mail=_2916CDB8-4F2A-42C6-9023-D632F101B8AA-- From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 20:43:57 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B342735C; Tue, 31 Mar 2015 20:43:57 +0000 (UTC) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 20CC0349; Tue, 31 Mar 2015 20:43:57 +0000 (UTC) Received: by lajy8 with SMTP id y8so22003265laj.0; Tue, 31 Mar 2015 13:43:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tgOg5TRSa9dHqz/NEIQiXU392nOIU7PEBS3Yg6oorJQ=; b=ldLIl8iggAtRgITy6sXVhOyMlmpxybuCXXtOiTZeAqyef3FsgtdfHdQHszgB7mv1My wkSOLiKe0gM+EIhgvOpt2cAdmoswZC52LAwU8ne77QyWs51zesAKO1skJpq9VnjvRKzz tyrIWV/xbFUIqA5+NfMPxlyjy+DLZQ4rNwrNEZNJqNkYCVKY2G0mWgQNm8hNMtrfBSkp az2rwf4VS9bFAYoc8x4kyTm8vDGY7leDc7G3/13R2LYykBIZWyGdGKmbVzQ5MUkZBsh8 4ZrazSRVj9zpqDiY/QdPtRz032ssDae3EZDeiKaT/3CElEI/onwAJNFRTPDbyTAckkcQ qyqA== MIME-Version: 1.0 X-Received: by 10.152.234.108 with SMTP id ud12mr32610584lac.81.1427834635120; Tue, 31 Mar 2015 13:43:55 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Tue, 31 Mar 2015 13:43:55 -0700 (PDT) In-Reply-To: References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> <5B103C77-EA63-4C04-95FE-B138CF46F01C@FreeBSD.org> Date: Tue, 31 Mar 2015 13:43:55 -0700 X-Google-Sender-Auth: 572U2nCJfA2v5UaNLbAKHqEBVcY Message-ID: Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import From: Craig Rodrigues To: Dimitry Andric Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 20:43:57 -0000 On Tue, Mar 31, 2015 at 1:41 PM, Dimitry Andric wrote: > On 31 Mar 2015, at 22:06, Craig Rodrigues wrote: > > > > On Tue, Mar 31, 2015 at 12:48 PM, Dimitry Andric > wrote: > > On 31 Mar 2015, at 21:38, Craig Rodrigues wrote: > > > > > > On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric > wrote: > > > > > >> On 31 Mar 2015, at 20:13, Dimitry Andric wrote: > > >> ... > > >>> but then: > > >>> > > >>> + patch > > >>> Hmm... Looks like a unified diff to me... > > >>> The text leading up to this was: > > >>> -------------------------- > > >>> |Index: contrib/libc++/include/type_traits > > >>> |=================================================================== > > >>> |--- contrib/libc++/include/type_traits (revision 280762) > > >>> |+++ contrib/libc++/include/type_traits (working copy) > > >>> -------------------------- > > >>> Patching file contrib/libc++/include/type_traits using Plan A... > > >>> Reversed (or previously applied) patch detected! Assume -R? [y] > > >>> Hunk #1 succeeded at 842. > > >>> Hunk #2 succeeded at 877. > > >>> Hmm... Ignoring the trailing garbage. > > >>> done > > >>> > > >>> E.g., it undoes the change to type_traits that was merged in the > > >> subversion update. > > >> > > >> > > > OK, I undid the patch. Now the clang and libc++ parts build, but I'm > > > still getting problems building rescue: > > > > > > > https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/29/console > > > > Hm, that is strange. I have just completed a build with > > amd64-xtoolchain-gcc, and apart from boot2, everything worked... > > > > What does readelf say when you run it on the cat.lo file which is > > complained about in the log? And what happens if you delete it, and > > restart the build? > > > > See: > > > https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html > > I'm suspecting this might have something to do with crunchide, or least, > the copy of crunchide that is run for this: > > --- cat.lo --- > /usr/local/x86_64-freebsd/bin/ld -dc -r -o cat.lo cat_stub.o > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue//builds/FreeBSD_HEAD_external_toolchain_gcc/bin/cat/cat.o > crunchide -k _crunched_cat_stub cat.lo > > If I look at my own build logs, it seems to pick the crunchide > executable in /usr/bin, and Makefile.inc1 does *not* build it during the > cross-tools stage if ${TARGET_ARCH} is the same as ${MACHINE_ARCH}: > > .if ${TARGET_ARCH} != ${MACHINE_ARCH} > .if ${MK_RESCUE} != "no" || defined(RELEASEDIR) > _crunchide= usr.sbin/crunch/crunchide > .endif > > However, this does not explain why my /usr/bin/crunchide seems to not > screw up cat.lo, while yours does. As far as I can see, we're both > building this on a stable/10 amd64 box... > > Maybe, as a hack, you can force cross-tools to build crunchide, by > patching Makefile.inc1 to ignore the arch check, and see what that > results in? > Well my build host is 10.1-RELEASE, so maybe there are changes that went into 10-STABLE after 10.1 that prevent this from working. I'll give a shot at hacking things and let you know how far I get. -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 20:54:13 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1D595DC for ; Tue, 31 Mar 2015 20:54:13 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60FCE61E for ; Tue, 31 Mar 2015 20:54:13 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2VKsCW9014931 for ; Tue, 31 Mar 2015 20:54:12 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2VKsCm3014930; Tue, 31 Mar 2015 20:54:12 GMT (envelope-from root) Date: Tue, 31 Mar 2015 20:54:12 +0000 To: freebsd-toolchain@freebsd.org From: "dim (Dimitry Andric)" Subject: [Differential] [Request, 37 lines] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5 X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 20:54:13 -0000 dim created this revision. dim added reviewers: imp, bapt, rodrigc. dim added a subscriber: freebsd-toolchain. Herald added a subscriber: imp. REVISION SUMMARY When I tried replicating Craig Rodrigues's efforts at building head with the amd64-xtoolchain-gcc package, I noticed that during the build32 stage it still uses the base system ld and objcopy: [...] --- lib/csu/i386-elf__L --- ld -m elf_i386_fbsd -Y P,/usr/obj/home/dim/head/lib32/usr/lib32 -o crt1.o -r crt1_s.o crt1_c.o [...] --- lib/csu/i386-elf__L --- objcopy --localize-symbol _start1 crt1.o [...] --- lib/csu/i386-elf__L --- ld -m elf_i386_fbsd -Y P,/usr/obj/home/dim/head/lib32/usr/lib32 -o Scrt1.o -r crt1_s.o Scrt1_c.o [...] --- lib/csu/i386-elf__L --- objcopy --localize-symbol _start1 Scrt1.o And a bunch more of those. I went through the various Makefiles I could find, replacing literal 'objcopy' with ${OBJCOPY}, which fixes the case for objcopy. Also, I changed LD=${LD} and AS=${AS} to use their X variants in the definition of LIB32WMAKEFLAGS in Makefile.inc1, and added OBJCOPY=${XOBJCOPY} to the list. Together, these changes should ensure that the cross tools are always used instead of the base system tools. TEST PLAN A make universe is probably required, at least. BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 AFFECTED FILES Makefile.inc1 lib/csu/i386-elf/Makefile sys/boot/i386/boot2/Makefile sys/boot/i386/gptboot/Makefile sys/boot/i386/gptzfsboot/Makefile sys/boot/i386/zfsboot/Makefile sys/boot/mips/beri/boot2/Makefile sys/boot/pc98/boot0.5/Makefile sys/boot/pc98/boot0/Makefile sys/boot/pc98/boot2/Makefile To: dim, imp, bapt, rodrigc Cc: imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 20:59:48 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B153D99A for ; Tue, 31 Mar 2015 20:59:48 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8E0FB67B for ; Tue, 31 Mar 2015 20:59:48 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2VKxm2g019411 for ; Tue, 31 Mar 2015 20:59:48 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2VKxmdn019410; Tue, 31 Mar 2015 20:59:48 GMT (envelope-from root) Date: Tue, 31 Mar 2015 20:59:48 +0000 To: freebsd-toolchain@freebsd.org From: "bapt (Baptiste Daroussin)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbCsQ= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 20:59:48 -0000 bapt added inline comments. INLINE COMMENTS Makefile.inc1:416 You should probably test if XAS if defined: something like AS=${XAS:U${AS}} and so on Makefile.inc1:426 Same apply here REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, imp, bapt, rodrigc Cc: imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 21:04:13 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 81687A33; Tue, 31 Mar 2015 21:04:13 +0000 (UTC) Received: from mail-lb0-x22c.google.com (mail-lb0-x22c.google.com [IPv6:2a00:1450:4010:c04::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 1EE6C79C; Tue, 31 Mar 2015 21:04:13 +0000 (UTC) Received: by lbbzk7 with SMTP id zk7so5708386lbb.0; Tue, 31 Mar 2015 14:04:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=7IKOlT5FnZnWDTMatjIu/S5rHxVG99J0HbMDw1MzL/M=; b=d5PArDS+e3B1fploO0SZ4WSN2fV3FpRuGvXlugsxHofSHAUEdE8mP/aol5cgP+x8dv bQD/ClBOw+OeYCN+CdXKgdJ//vKyNShlwt0qLymq8bco6kUwhTTLohTqnb416YhE57rS HxfAK8OMo6VwDOB/GIQhr6fy1JJPXkZU53QEMIgWoIHpf9MdzTMKQYHBbYCSRiRm5DZM JM8WOJ4S1SUBBMuBbFg0pN0PLfJGjX4Bvjhqtg+8sl6fXQm0tf+Gy6dVlQ+M1hCJUeND FNg9exlzliqc6pFysc+AyyrTfrRrZ8kvp8jqGhROoG7s37/LPKMGZDyiwhhk7PWGUpka +SWw== MIME-Version: 1.0 X-Received: by 10.112.166.36 with SMTP id zd4mr6172521lbb.59.1427835851258; Tue, 31 Mar 2015 14:04:11 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Tue, 31 Mar 2015 14:04:11 -0700 (PDT) Date: Tue, 31 Mar 2015 14:04:11 -0700 X-Google-Sender-Auth: g5SJe6KYnczH5XrKHzgACtbZwqU Message-ID: Subject: Kernel compilation failures with gcc 4.9 From: Craig Rodrigues To: FreeBSD Toolchain , "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 21:04:13 -0000 Hi, I put this in make.conf: NO_WERROR=yes WERROR= WITHOUT_BOOT=yes WITHOUT_RESCUE=yes and used this script to build: https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-build.sh I managed to build a lot of stuff, but then got build failures in the aesni part of the kernel build. See the full build log here: https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/30/console I think this is the error: In file included from /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/mm_malloc.h:27:0, from /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/xmmintrin.h:34, from /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/emmintrin.h:31, from /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/wmmintrin.h:31, from /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/modules/aesni/../../crypto/aesni/aesni_ghash.c:74: /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/include/stdlib.h:93:7: error: conflicting types for 'free' void free(void *); ^ In file included from /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/crypto/aesni/aesni.h:33:0, from /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/modules/aesni/../../crypto/aesni/aesni_ghash.c:69: /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/sys/malloc.h:177:6: note: previous declaration of 'free' was here void free(void *addr, struct malloc_type *type); Any ideas? -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 21:07:22 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EFC0DCB9 for ; Tue, 31 Mar 2015 21:07:22 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B329E7D6 for ; Tue, 31 Mar 2015 21:07:22 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2VL7MIr028256 for ; Tue, 31 Mar 2015 21:07:22 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2VL7M8s028255; Tue, 31 Mar 2015 21:07:22 GMT (envelope-from root) Date: Tue, 31 Mar 2015 21:07:22 +0000 To: freebsd-toolchain@freebsd.org From: "dim (Dimitry Andric)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <9dad4bfd380916be7ee8cf6166c533e5@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbDIo= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 21:07:23 -0000 dim added inline comments. INLINE COMMENTS Makefile.inc1:416 These are also unconditionally used in the previous block for WMAKENV, e.g.: ``` WMAKEENV+= CC="${XCC} ${XCFLAGS}" CXX="${XCXX} ${XCFLAGS} ${XCXXFLAGS}" \ DEPFLAGS="${DEPFLAGS}" \ CPP="${XCPP} ${XCFLAGS}" \ AS="${XAS}" AR="${XAR}" LD="${XLD}" NM=${XNM} \ OBJDUMP=${XOBJDUMP} OBJCOPY="${XOBJCOPY}" \ RANLIB=${XRANLIB} STRINGS=${XSTRINGS} \ SIZE="${XSIZE}" ``` and just before that, they are unconditionally defined: ``` XCOMPILERS= CC CXX CPP .for COMPILER in ${XCOMPILERS} .if defined(CROSS_COMPILER_PREFIX) X${COMPILER}?= ${CROSS_COMPILER_PREFIX}${${COMPILER}} .else X${COMPILER}?= ${${COMPILER}} .endif .endfor XBINUTILS= AS AR LD NM OBJCOPY OBJDUMP RANLIB SIZE STRINGS .for BINUTIL in ${XBINUTILS} .if defined(CROSS_BINUTILS_PREFIX) X${BINUTIL}?= ${CROSS_BINUTILS_PREFIX}${${BINUTIL}} .else X${BINUTIL}?= ${${BINUTIL}} .endif .endfor ``` So I think it is unnecessary to check them again. REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, imp, bapt, rodrigc Cc: imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 21:19:31 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BE20B306 for ; Tue, 31 Mar 2015 21:19:31 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 9B7EF935 for ; Tue, 31 Mar 2015 21:19:31 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t2VLJV2l040771 for ; Tue, 31 Mar 2015 21:19:31 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t2VLJVlr040770; Tue, 31 Mar 2015 21:19:31 GMT (envelope-from root) Date: Tue, 31 Mar 2015 21:19:31 +0000 To: freebsd-toolchain@freebsd.org From: "bapt (Baptiste Daroussin)" Subject: [Differential] [Accepted] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <61f9de33fd5a07a342559ea8da3e2d93@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbD2M= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 21:19:31 -0000 bapt accepted this revision. bapt added a comment. This revision is now accepted and ready to land. yup you are right This looks ok for me I still would be more confident with @imp reviewing as well :) BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, imp, rodrigc, bapt Cc: imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 23:53:52 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B4581471; Tue, 31 Mar 2015 23:53:52 +0000 (UTC) Received: from st11p02mm-asmtp001.mac.com (st11p02mm-asmtpout001.mac.com [17.172.220.236]) (using TLSv1.2 with cipher DHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 86321CAE; Tue, 31 Mar 2015 23:53:52 +0000 (UTC) Received: from fukuyama.hsd1.ca.comcast.net (c-73-162-13-215.hsd1.ca.comcast.net [73.162.13.215]) by st11p02mm-asmtp001.mac.com (Oracle Communications Messaging Server 7.0.5.35.0 64bit (built Dec 4 2014)) with ESMTPSA id <0NM300NXTP0H1N10@st11p02mm-asmtp001.mac.com>; Tue, 31 Mar 2015 23:53:07 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.13.68,1.0.33,0.0.0000 definitions=2015-03-31_06:2015-03-31,2015-03-31,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1412110000 definitions=main-1503310205 Content-type: text/plain; charset=us-ascii MIME-version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Kernel compilation failures with gcc 4.9 From: Rui Paulo In-reply-to: Date: Tue, 31 Mar 2015 16:53:05 -0700 Content-transfer-encoding: quoted-printable Message-id: <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> References: To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 23:53:52 -0000 On Mar 31, 2015, at 14:04, Craig Rodrigues wrote: >=20 > Hi, >=20 > I put this in make.conf: >=20 > NO_WERROR=3Dyes > WERROR=3D > WITHOUT_BOOT=3Dyes > WITHOUT_RESCUE=3Dyes >=20 > and used this script to build: > = https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-buil= d.sh >=20 > I managed to build a lot of stuff, but then got build failures > in the aesni part of the kernel build. >=20 > See the full build log here: > = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/30/con= sole >=20 > I think this is the error: >=20 > In file included from > = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/mm_malloc.h:27= :0, > from > = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/xmmintrin.h:34= , > from > = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/emmintrin.h:31= , > from > = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/wmmintrin.h:31= , > from > = /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/modules/aesni/../../crypto= /aesni/aesni_ghash.c:74: > = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/tmp/usr/include/stdlib.h:93:7: > error: conflicting types for 'free' void free(void *); >=20 > ^ > In file included from > = /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/crypto/aesni/aesni.h:33:0,= > from > = /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/modules/aesni/../../crypto= /aesni/aesni_ghash.c:69: > /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/sys/malloc.h:177:6: = note: > previous declaration of 'free' was here > void free(void *addr, struct malloc_type *type); It shouldn't be using the stdlib when it's built with -ffreestanding or = -nostdlib. Can you make sure? -- Rui Paulo From owner-freebsd-toolchain@FreeBSD.ORG Tue Mar 31 23:55:16 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 351264C5 for ; Tue, 31 Mar 2015 23:55:16 +0000 (UTC) Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F3E83CB6 for ; Tue, 31 Mar 2015 23:55:15 +0000 (UTC) Received: by pdbni2 with SMTP id ni2so36106236pdb.1 for ; Tue, 31 Mar 2015 16:55:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=s7a8xSg4vQjncpidFFF7m978s8TR7mwaRaFZv5Q0wj4=; b=IZp0qjvRTiAsKOYbbexLyC+9u0rcvohcZlEY77a2VnarGZ5foMyU1Jn6yR1RnD5OG6 fA/Z2T0R0E1iLvgMyaQyHO1QWlExqZcoBp+6nEdKhtzTb1umYzsaSojiTp0OlQ6vh3MH s6WTAWWT1+LPh/qbR6E3qQxNxtABDR1GbEWcnyYbFf8vJaKs8bs3y7U3IuFfvaWe11yV W0y+16ob7rK3na2dX2xk2QCVX/cxAOR2CKeuAqsWcuekhyo+mQd0aLHWXAt1ndLgMiMx P56MWrGxO4cI9l6pXxQ8gi7lhJYw8NGyPsnYl7EyQY3DmOpxDdFE13GmqJjk1dgjX3VA NNlA== X-Gm-Message-State: ALoCoQnvf95bXC3ByoUeJPvb6nGAOmmRqA/RPTrF/tFE7j5A9Oy+GJU3M3pllsW6EaBdjXerNzGY X-Received: by 10.68.253.162 with SMTP id ab2mr72840644pbd.62.1427846114559; Tue, 31 Mar 2015 16:55:14 -0700 (PDT) Received: from [10.64.25.92] ([69.53.236.236]) by mx.google.com with ESMTPSA id jh2sm83600pbb.25.2015.03.31.16.55.13 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 31 Mar 2015 16:55:13 -0700 (PDT) Sender: Warner Losh Subject: Re: Kernel compilation failures with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_C0E93C42-95B1-40C9-B4B3-0A853D27E9F8"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> Date: Tue, 31 Mar 2015 16:55:11 -0700 Message-Id: <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com> References: <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> To: Rui Paulo X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Mar 2015 23:55:16 -0000 --Apple-Mail=_C0E93C42-95B1-40C9-B4B3-0A853D27E9F8 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii > On Mar 31, 2015, at 4:53 PM, Rui Paulo wrote: >=20 > On Mar 31, 2015, at 14:04, Craig Rodrigues = wrote: >>=20 >> Hi, >>=20 >> I put this in make.conf: >>=20 >> NO_WERROR=3Dyes >> WERROR=3D >> WITHOUT_BOOT=3Dyes >> WITHOUT_RESCUE=3Dyes >>=20 >> and used this script to build: >> = https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-buil= d.sh >>=20 >> I managed to build a lot of stuff, but then got build failures >> in the aesni part of the kernel build. >>=20 >> See the full build log here: >> = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/30/con= sole >>=20 >> I think this is the error: >>=20 >> In file included from >> = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/mm_malloc.h:27= :0, >> from >> = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/xmmintrin.h:34= , >> from >> = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/emmintrin.h:31= , >> from >> = /usr/local/lib/gcc/x86_64-portbld-freebsd10.0/4.9.1/include/wmmintrin.h:31= , >> from >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/modules/aesni/../../crypto= /aesni/aesni_ghash.c:74: >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/tmp/usr/include/stdlib.h:93:7: >> error: conflicting types for 'free' void free(void *); >>=20 >> ^ >> In file included from >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/crypto/aesni/aesni.h:33:0,= >> from >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/modules/aesni/../../crypto= /aesni/aesni_ghash.c:69: >> /builds/FreeBSD_HEAD_external_toolchain_gcc/sys/sys/malloc.h:177:6: = note: >> previous declaration of 'free' was here >> void free(void *addr, struct malloc_type *type); >=20 > It shouldn't be using the stdlib when it's built with -ffreestanding = or -nostdlib. Can you make sure? The AES stuff breaks the rules, and this is a consequence of it :( That = stuff should be fixed. Warner --Apple-Mail=_C0E93C42-95B1-40C9-B4B3-0A853D27E9F8 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVGzPgAAoJEGwc0Sh9sBEA1BUP/363846JF4o82RYk7qaVyCTK ZPqqOKsKJI8qWR0Gf/agCFCJ1c4h9HpdXlK6+f9b+LGBDisWtQgpAFYCVKW2U2TY u5NsiijhoLqTRSitRkjhL36MCr4oxw634tz7JDJ5Y5pRxZX4K4HFpSzn3fbh4sHc U1err29Th85ZdrfuhMSU9fWjw7r0K+wWeo/xinZ+H5n45LWX8bR9rrEZpH2JgD5D I8PwCFX/1pmxLC2C3jID+C2wJCIy0i3q9bCCrAASAbTcGBdO7dBiiB317+pBCaID 7rT93cjiCGVJyiGL/3El59Qxsxr1cEfuy6lx6wZLSHkFd3r7uEkFLlXRvpdHE+wR UI9Ir/WOiIaEzlT+kVKsiwWgc0qxj/io8BlrP0eDXiLcQHCpg0s/BBj9L7vjfv5d Gv0KM+QD4Pnt/sohhkomD5C0eA216P/mqyaPmqpIMAqcOc9EzX0bQTvXudNHoPOE IIGhXV8Rz6Ec+1Q/Biga+1jeoOQVQ4d5wsYV5673tYcfzCgeMi/9HwrYJxOpPYaQ QDWU/xvYRKqw5dTJinH/eOQzxSbt2yLRunDEVsdCKtL0OU/doVcdT6EJVVU3vW9t eB4Jt42kzcK+gX2bpV1iAekJvgsEBTEr65GOfH89+3iZQaVhTPirOQvSHayxYF/s T/NnP1kkDPrBdGTEs47H =M8nU -----END PGP SIGNATURE----- --Apple-Mail=_C0E93C42-95B1-40C9-B4B3-0A853D27E9F8-- From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 00:00:06 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6351A563 for ; Wed, 1 Apr 2015 00:00:06 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 417FCCE3 for ; Wed, 1 Apr 2015 00:00:06 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t31006uN011136 for ; Wed, 1 Apr 2015 00:00:06 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t31005du011135; Wed, 1 Apr 2015 00:00:06 GMT (envelope-from root) Date: Wed, 1 Apr 2015 00:00:05 +0000 To: freebsd-toolchain@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Updated] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbNQU= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 00:00:06 -0000 imp added a comment. >>! In D2187#7, @bapt wrote: > yup you are right > > This looks ok for me I still would be more confident with @imp reviewing as well :) Using Xfoo unconditionally is good. BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, bapt, imp Cc: imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 00:03:06 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B18E1710 for ; Wed, 1 Apr 2015 00:03:06 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 89255D96 for ; Wed, 1 Apr 2015 00:03:06 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t31036MM015995 for ; Wed, 1 Apr 2015 00:03:06 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t310369Q015994; Wed, 1 Apr 2015 00:03:06 GMT (envelope-from root) Date: Wed, 1 Apr 2015 00:03:06 +0000 To: freebsd-toolchain@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <0ea86e7037e358c525bdce6e1fd8d822@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbNbo= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 00:03:06 -0000 imp added a comment. Where is OBJCOPY defined? BRANCH /head INLINE COMMENTS Makefile.inc1:416 Do we need a similar change for powerpc? Using Xfoo unconditionally is cool. REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, bapt, imp Cc: imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 00:03:21 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC1C0737; Wed, 1 Apr 2015 00:03:21 +0000 (UTC) Received: from mail-qg0-x22e.google.com (mail-qg0-x22e.google.com [IPv6:2607:f8b0:400d:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7726CD9A; Wed, 1 Apr 2015 00:03:21 +0000 (UTC) Received: by qgfa8 with SMTP id a8so29765586qgf.0; Tue, 31 Mar 2015 17:03:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=z8CiBqKLIuZUDoApyGWgcMKUtiBgS5RAXTDK4yHkuWQ=; b=Ayys7k4+iqRZQRDaKnXhC3k8cJtRPmalyHX92KZD1IYr+wQQMqvrCh4KXoiANjVLcK fxcvWKOSsnhLGJkqaSw+TN9Lu1XvswkdyFcHenoKWEUMLMyqXJGm2j25ykZrqJSQM3RS AZ/iVnUQXc3WftI1WIvvlrDwqmFUwUl6MzwhhhKdWuBea5DBx/VRzp+x7NAgw7Y9sD+4 F06GWmN0eUgUgT0eqJTBZC1B50xLv04PrAcPbkh4E7oKQrSi1nhK/CTs85jGKFscGBLp D0TTF+KEX2NXCSVsZvuD4fEB+rHa2V5P76oX3CW6XxlGoghoKPWgFXg5+mGgr175vPkG FDrw== MIME-Version: 1.0 X-Received: by 10.140.238.78 with SMTP id j75mr53233639qhc.96.1427846600599; Tue, 31 Mar 2015 17:03:20 -0700 (PDT) Received: by 10.140.94.99 with HTTP; Tue, 31 Mar 2015 17:03:20 -0700 (PDT) Date: Tue, 31 Mar 2015 17:03:20 -0700 Message-ID: Subject: profile_rt from llvm folks? From: NGie Cooper To: Dimitry Andric , Ed Maste , rdivacky@FreeBSD.org Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-toolchain@freebsd.org" , Benno Rice X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 00:03:21 -0000 Hi all, We've recently integrated a version of profile_rt from the llvm folks internally to replace gcov for code coverage. I was wondering if there was a plan to replace the copy of gcov in FreeBSD with the same (either in the base system, ports, or both). Thanks! From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 00:09:24 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DA6009AB for ; Wed, 1 Apr 2015 00:09:24 +0000 (UTC) Received: from mail-pa0-f47.google.com (mail-pa0-f47.google.com [209.85.220.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 996BADF2 for ; Wed, 1 Apr 2015 00:09:24 +0000 (UTC) Received: by padcy3 with SMTP id cy3so34503105pad.3 for ; Tue, 31 Mar 2015 17:09:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=r9xwD9RhAZqbKjbYAzlPzb4K0/MHYKCNKH/OJEttFb0=; b=kVj6+8EccyrK4fog3nVGIVhFkVlZa8jAXaNmxVsg6A3PqWcouO5iNwYgFdAQlK4sfl Kh7K3zTtqGiLESKk79hxsp8KVrZ+pJ+JvYs6TSSEw1L2yQ6FBtj9nqwmU4tRN2su3/0/ 0JcYFDvZtTKu1lSC+8Gf7xWxF9Nh9CZTXyvRoA+k26bM5LTuV52EoiVdyrz43ECy86WP jaIokxk4AhZLAkO5z6dMPRCqTYyh+u2Q+OGk2Hmfk1A8BxYl/SBQFFQLf91AUS7fFPuh gsRNv0Xs8RuwVY3ls4Ag6eBbPKXPRogbA3fKdfckgyWxTKWPLhS/LDXXqIHe0Ng8XPKW onKQ== X-Gm-Message-State: ALoCoQnGfwB0Nzu3/6pFF4aNvTtmtJ291iPdGnQyoRgjCLRgEA7zTFMYQ/hruI9eYnFjWABD3A8f X-Received: by 10.68.239.104 with SMTP id vr8mr72202450pbc.96.1427846957965; Tue, 31 Mar 2015 17:09:17 -0700 (PDT) Received: from [10.64.25.92] ([69.53.236.236]) by mx.google.com with ESMTPSA id ll2sm104628pbc.11.2015.03.31.17.09.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 31 Mar 2015 17:09:17 -0700 (PDT) Sender: Warner Losh Subject: Re: CROSS_TOOLCHAIN=amd64-gcc fails to build after clang 3.6.0 import Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_FB9CC06F-C844-4257-B1D1-900E604A1EA7"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: Date: Tue, 31 Mar 2015 17:09:15 -0700 Message-Id: <94264E89-1AED-4704-A922-A11D05EEFE34@bsdimp.com> References: <5F90BE99-E82C-4444-9E4C-5963B40AA3B0@FreeBSD.org> <5B103C77-EA63-4C04-95FE-B138CF46F01C@FreeBSD.org> To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain , Dimitry Andric X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 00:09:24 -0000 --Apple-Mail=_FB9CC06F-C844-4257-B1D1-900E604A1EA7 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Mar 31, 2015, at 1:43 PM, Craig Rodrigues = wrote: >=20 > On Tue, Mar 31, 2015 at 1:41 PM, Dimitry Andric = wrote: >=20 >> On 31 Mar 2015, at 22:06, Craig Rodrigues = wrote: >>>=20 >>> On Tue, Mar 31, 2015 at 12:48 PM, Dimitry Andric >> wrote: >>> On 31 Mar 2015, at 21:38, Craig Rodrigues = wrote: >>>>=20 >>>> On Tue, Mar 31, 2015 at 11:20 AM, Dimitry Andric >> wrote: >>>>=20 >>>>> On 31 Mar 2015, at 20:13, Dimitry Andric wrote: >>>>> ... >>>>>> but then: >>>>>>=20 >>>>>> + patch >>>>>> Hmm... Looks like a unified diff to me... >>>>>> The text leading up to this was: >>>>>> -------------------------- >>>>>> |Index: contrib/libc++/include/type_traits >>>>>> = |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >>>>>> |--- contrib/libc++/include/type_traits (revision 280762) >>>>>> |+++ contrib/libc++/include/type_traits (working copy) >>>>>> -------------------------- >>>>>> Patching file contrib/libc++/include/type_traits using Plan A... >>>>>> Reversed (or previously applied) patch detected! Assume -R? [y] >>>>>> Hunk #1 succeeded at 842. >>>>>> Hunk #2 succeeded at 877. >>>>>> Hmm... Ignoring the trailing garbage. >>>>>> done >>>>>>=20 >>>>>> E.g., it undoes the change to type_traits that was merged in the >>>>> subversion update. >>>>>=20 >>>>>=20 >>>> OK, I undid the patch. Now the clang and libc++ parts build, but = I'm >>>> still getting problems building rescue: >>>>=20 >>>>=20 >> = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/29/con= sole >>>=20 >>> Hm, that is strange. I have just completed a build with >>> amd64-xtoolchain-gcc, and apart from boot2, everything worked... >>>=20 >>> What does readelf say when you run it on the cat.lo file which is >>> complained about in the log? And what happens if you delete it, and >>> restart the build? >>>=20 >>> See: >>>=20 >> = https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.ht= ml >>=20 >> I'm suspecting this might have something to do with crunchide, or = least, >> the copy of crunchide that is run for this: >>=20 >> --- cat.lo --- >> /usr/local/x86_64-freebsd/bin/ld -dc -r -o cat.lo cat_stub.o >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue//builds/FreeBSD_HEAD_external_toolchain_gcc= /bin/cat/cat.o >> crunchide -k _crunched_cat_stub cat.lo >>=20 >> If I look at my own build logs, it seems to pick the crunchide >> executable in /usr/bin, and Makefile.inc1 does *not* build it during = the >> cross-tools stage if ${TARGET_ARCH} is the same as ${MACHINE_ARCH}: >>=20 >> .if ${TARGET_ARCH} !=3D ${MACHINE_ARCH} >> .if ${MK_RESCUE} !=3D "no" || defined(RELEASEDIR) >> _crunchide=3D usr.sbin/crunch/crunchide >> .endif >>=20 >> However, this does not explain why my /usr/bin/crunchide seems to not >> screw up cat.lo, while yours does. As far as I can see, we're both >> building this on a stable/10 amd64 box... >>=20 >=20 >> Maybe, as a hack, you can force cross-tools to build crunchide, by >> patching Makefile.inc1 to ignore the arch check, and see what that >> results in? >>=20 >=20 >=20 >=20 > Well my build host is 10.1-RELEASE, so maybe there are changes > that went into 10-STABLE after 10.1 that prevent this from working. >=20 > I'll give a shot at hacking things and let you know how far I get. BTW, we don=E2=80=99t officially support 4.8 / 4.9 yet. There are things = that are known to be broken with it, and since we don=E2=80=99t tinderbox it, = it is likely that we=E2=80=99ll break it over and over again=E2=80=A6 When I was building it, as a test, I used WITHOUT_RESCUE. Warner --Apple-Mail=_FB9CC06F-C844-4257-B1D1-900E604A1EA7 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVGzcsAAoJEGwc0Sh9sBEAw3EP/2jxzkUgh5O9rP1Ej/bbkJJN ejsgEUS0/r2lb8x9jGXgVZZRq12mKx90IeWmxXXcIsZydhGT5ybBGw/kzwW1NYu4 h1ZQQeq07kvb5vuQXJeQoKhK65U/ff9OtgyAdqFWckHr2fpGJio3u3bhdm6Xnysq qaxfTLHmueRzLex7Sf4Qria6ovgvGw1GZNTOOea3SwNif25IZLgnn2odU+l+jsGN 3hONKV+/36BuJX1eoJyz6Ofmcjl5VRezPUAwDGPGAiCGnYL0xjkMYsccKx4Intsg yN9plR0VYtpJYYvxbPz3Q+4pmv/c8NvtzE7eKua3E0ansIdMHfI9mUG63bFJoRqI OpDBQTHPBOhsWjITyhQtj860ZAtnUFZ4PkBwt2dBmXGr60HGqIbkFV/sRneSINl8 FjM6cU4rZKGh7RTXZJ6y6w4VbfA90qMlt9hx5lxuGXwIY8iK5Fw0TSrQzkx7Qqco BiZmhLAngYGG0c2HW3CWNotqKdkYoYdFE2z4aAJZfcv4NNu1ifqKeBtRuEh++eOR JXIFxLTm5vmeBeEIz6KSIq/eREfUXOTWqpxWQvhmFcFTrtnQQ4u5jBTWSSZOpHWe bJ2BLkfgpDQm23Kuw6tSSfd2x5SZi90oGG38KGFluLP8T/HrXLGMlmHAsObxBvQL Mux8APFKvSLfOVc2onqr =vB+X -----END PGP SIGNATURE----- --Apple-Mail=_FB9CC06F-C844-4257-B1D1-900E604A1EA7-- From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 00:46:07 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 53E80708 for ; Wed, 1 Apr 2015 00:46:07 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3006A243 for ; Wed, 1 Apr 2015 00:46:07 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t310k67q060818 for ; Wed, 1 Apr 2015 00:46:06 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t310k6G4060817; Wed, 1 Apr 2015 00:46:06 GMT (envelope-from root) Date: Wed, 1 Apr 2015 00:46:06 +0000 To: freebsd-toolchain@freebsd.org From: "emaste (Ed Maste)" Subject: [Differential] [Accepted] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <203b0a2a0cd1eb0d66819804871250fb@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbP84= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 00:46:07 -0000 emaste added a subscriber: emaste. emaste accepted this revision. emaste added a reviewer: emaste. emaste added a comment. Agreed it would be nice to have @imp sign off, but looks good to me. BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, bapt, imp, emaste Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 00:49:23 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 50D67891 for ; Wed, 1 Apr 2015 00:49:23 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2DBB02A5 for ; Wed, 1 Apr 2015 00:49:23 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t310nMik063257 for ; Wed, 1 Apr 2015 00:49:22 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t310nM8Y063256; Wed, 1 Apr 2015 00:49:22 GMT (envelope-from root) Date: Wed, 1 Apr 2015 00:49:22 +0000 To: freebsd-toolchain@freebsd.org From: "emaste (Ed Maste)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbQJI= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 00:49:23 -0000 emaste added a comment. >>! In D2187#11, @imp wrote: > Where is OBJCOPY defined? In share/mk/sys.mk, as long as `if !defined(%POSIX)` BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, bapt, imp, emaste Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 02:28:20 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 845F3734; Wed, 1 Apr 2015 02:28:20 +0000 (UTC) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0285DF53; Wed, 1 Apr 2015 02:28:20 +0000 (UTC) Received: by labe2 with SMTP id e2so26417561lab.3; Tue, 31 Mar 2015 19:28:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=G2D1nLD74kj4Wt9UKe/18zt0vqoBMKMiv91uz+CCIng=; b=0zygj0DNO2jZj6rePzLudfaqDkkZUwmaQlr0Fuox44oWxqc+sODUrqoIMFVs9O5Rj9 IssqEDTnAO1Khcul3RpRE9tzKtyjMTT6DRWp7uCzwRVzNJ7teRZVvKXdEks5VsWLGr5W lzaLmVMlXfKCppzFO8zzEzdcG8C38vP7bIkvO51ry+BwxX185nr5/Q8m1RNU2cpwtkv8 lMmCC08x1neiCA4uuqnfDzyfFzQ6FDdxoZAhlByahk6BCvkmMApLuUB2blyvyXzH8roW iROqxjxPnsbzm08vVhrlh4V/gLof6SyTD57nWz17j6Ar6dyWd48QiaRtM6No2QqHOuQY gqLQ== MIME-Version: 1.0 X-Received: by 10.112.17.8 with SMTP id k8mr33406694lbd.26.1427855297272; Tue, 31 Mar 2015 19:28:17 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Tue, 31 Mar 2015 19:28:17 -0700 (PDT) In-Reply-To: <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com> References: <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com> Date: Tue, 31 Mar 2015 19:28:17 -0700 X-Google-Sender-Auth: _VRGLA7q4r7i75zxTy3hbLsZYBQ Message-ID: Subject: Re: Kernel compilation failures with gcc 4.9 From: Craig Rodrigues To: John-Mark Gurny Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 02:28:20 -0000 On Tue, Mar 31, 2015 at 4:55 PM, Warner Losh wrote: > > > > > It shouldn't be using the stdlib when it's built with -ffreestanding or > -nostdlib. Can you make sure? > > The AES stuff breaks the rules, and this is a consequence of it :( That > stuff should be fixed. > > John-Mark, Do you have time to help fix compilation with gcc 4.9 of AESNI in the kernel? It currently does not compile with gcc 4.9. See my original bug report here: https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001577.html We are trying to fix the kernel build enough with gcc 4.9 so that we can at least set up a Jenkins continuous build (with -Werror turned off initially). Thanks. -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 03:38:30 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 850898A2 for ; Wed, 1 Apr 2015 03:38:30 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 625BDAB2 for ; Wed, 1 Apr 2015 03:38:30 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t313cUPH044011 for ; Wed, 1 Apr 2015 03:38:30 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t313cUUb044010; Wed, 1 Apr 2015 03:38:30 GMT (envelope-from root) Date: Wed, 1 Apr 2015 03:38:30 +0000 To: freebsd-toolchain@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Accepted] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbaDY= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 03:38:30 -0000 imp accepted this revision. BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, bapt, emaste, imp Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 05:11:00 2015 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2313B1A10; Wed, 1 Apr 2015 05:11:00 +0000 (UTC) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 957B8B37; Wed, 1 Apr 2015 05:10:53 +0000 (UTC) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t315ApFh004541 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Mar 2015 22:10:51 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t315ApEn004540; Tue, 31 Mar 2015 22:10:51 -0700 (PDT) (envelope-from jmg) Date: Tue, 31 Mar 2015 22:10:51 -0700 From: John-Mark Gurney To: Craig Rodrigues Subject: Re: Kernel compilation failures with gcc 4.9 Message-ID: <20150401051051.GT51048@funkthat.com> References: <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Tue, 31 Mar 2015 22:10:51 -0700 (PDT) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 05:11:00 -0000 Craig Rodrigues wrote this message on Tue, Mar 31, 2015 at 19:28 -0700: > On Tue, Mar 31, 2015 at 4:55 PM, Warner Losh wrote: > > > > It shouldn't be using the stdlib when it's built with -ffreestanding or > > -nostdlib. Can you make sure? > > > > The AES stuff breaks the rules, and this is a consequence of it :( That > > stuff should be fixed. > > Do you have time to help fix compilation with gcc 4.9 of AESNI in the > kernel? > It currently does not compile with gcc 4.9. > > See my original bug report here: > https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001577.html > > We are trying to fix the kernel build enough with gcc 4.9 so that > we can at least set up a Jenkins continuous build (with -Werror turned off > initially). This is an issue w/ gcc 4.9's headers... It is including stdlib.h, via mm_malloc.h which is conflicting w/ sys/malloc.h's version of free.. kan wrapped the include of mm_malloc.h in an #if __STDC_HOSTED__ which is why gcc 4.2 doesn't have the issue per my request a couple years ago: https://svnweb.freebsd.org/changeset/base/r242182 A similar fix needs to be applied here... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 06:12:22 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 21BE9AC5 for ; Wed, 1 Apr 2015 06:12:22 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F0304699 for ; Wed, 1 Apr 2015 06:12:21 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t316CLdH008238 for ; Wed, 1 Apr 2015 06:12:21 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t316CL3B008235; Wed, 1 Apr 2015 06:12:21 GMT (envelope-from root) Date: Wed, 1 Apr 2015 06:12:21 +0000 To: freebsd-toolchain@freebsd.org From: "rodrigc (Craig Rodrigues)" Subject: [Differential] [Accepted] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <0fb0c1b39f53a5e5610d96ab3484dd73@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbjEU= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 06:12:22 -0000 rodrigc accepted this revision. BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, bapt, emaste, imp, rodrigc Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 05:45:32 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 96FAB3B6 for ; Wed, 1 Apr 2015 05:45:32 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 711551AA for ; Wed, 1 Apr 2015 05:45:32 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t315jW54079062 for ; Wed, 1 Apr 2015 05:45:32 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t315jWTq079061; Wed, 1 Apr 2015 05:45:32 GMT (envelope-from root) Date: Wed, 1 Apr 2015 05:45:32 +0000 To: freebsd-toolchain@freebsd.org From: "dim (Dimitry Andric)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <142a8d2ec54f3449fcd630223d752145@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUbhfw= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 05:45:32 -0000 dim added inline comments. BRANCH /head INLINE COMMENTS Makefile.inc1:416 I just looked for the LD="${LD}" assignments, and replaced them all. Maybe, for consistency, we should add OBJCOPY=${XOBJCOPY} for the powerpc case too, but I'm not sure if it's used at all in the powerpc build... REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, bapt, emaste, imp Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 06:05:15 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C45458DF for ; Wed, 1 Apr 2015 06:05:15 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id A51223DA for ; Wed, 1 Apr 2015 06:05:15 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t3165FiR099729 for ; Wed, 1 Apr 2015 06:05:15 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t3165Flo099728; Wed, 1 Apr 2015 06:05:15 GMT (envelope-from root) Date: Wed, 1 Apr 2015 06:05:15 +0000 To: freebsd-toolchain@freebsd.org From: "rodrigc (Craig Rodrigues)" Subject: [Differential] [Closed] D1722: Add -s option to config Message-ID: X-Priority: 3 Thread-Topic: D1722: Add -s option to config X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZjRiYmMxMGJlOTMxNjdjYzA1ZTBiNzVjOTI3IFUbips= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 06:05:15 -0000 rodrigc closed this revision. rodrigc added a comment. Committed under rS277904 REVISION DETAIL https://reviews.freebsd.org/D1722 To: rodrigc, brooks, imp Cc: freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 14:59:52 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0B4BAA4D; Wed, 1 Apr 2015 14:59:52 +0000 (UTC) Received: from mail-lb0-x22f.google.com (mail-lb0-x22f.google.com [IPv6:2a00:1450:4010:c04::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 6E77C9B2; Wed, 1 Apr 2015 14:59:51 +0000 (UTC) Received: by lboc7 with SMTP id c7so38287921lbo.1; Wed, 01 Apr 2015 07:59:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=Xr+A1bcbG7zDBNjQxD4dL3IYDpvo7HrQoMbcH7vSCnU=; b=EsA6N5eOn8fCrrJGpIcLKFjJzFIiqjZzpq1pjSNa2kuITN2Vs06YtqrP/qIzF/rx38 gNgF4TwrsMd2iDM+/omLD7sn3o8Yzv3/uz4QRPZs4K8VDOJjxd0Qr1PQ8VT2/1+NerSa kODzxed+mevhuxvxLwUGmvhGmuOJASD2XGqBnqdCuNhAIHjdJNLl2HptiFbnjefXNttb lVZJPIlJbmBbkpO6szXAY5PyIV35AninopJJIdjI3dcezgofPXM/S7Ywn2ZDd8kO2abz NV75DsXPhup4AraKzItS6CNeQ/tpjvmfs1bZGeoxE2Y8/IhX1y7sgBfioxrruQj6caYo Zi4g== MIME-Version: 1.0 X-Received: by 10.152.163.2 with SMTP id ye2mr9605608lab.89.1427900389510; Wed, 01 Apr 2015 07:59:49 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Wed, 1 Apr 2015 07:59:49 -0700 (PDT) In-Reply-To: <20150401051051.GT51048@funkthat.com> References: <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com> <20150401051051.GT51048@funkthat.com> Date: Wed, 1 Apr 2015 07:59:49 -0700 X-Google-Sender-Auth: X2aIgN5nkjp652e1v-c1u4RwYdE Message-ID: Subject: Re: Kernel compilation failures with gcc 4.9 From: Craig Rodrigues To: John-Mark Gurney Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 14:59:52 -0000 On Tue, Mar 31, 2015 at 10:10 PM, John-Mark Gurney wrote: > > > This is an issue w/ gcc 4.9's headers... It is including stdlib.h, > via mm_malloc.h which is conflicting w/ sys/malloc.h's version of free.. > > kan wrapped the include of mm_malloc.h in an #if __STDC_HOSTED__ which is > why gcc 4.2 doesn't have the issue per my request a couple years ago: > https://svnweb.freebsd.org/changeset/base/r242182 > > A similar fix needs to be applied here... Interesting, so r242182 does this inside the gcc header file itself: --- head/contrib/gcc/config/i386/xmmintrin.h 2011/03/14 13:31:34 219639 +++ head/contrib/gcc/config/i386/xmmintrin.h 2012/10/27 17:39:36 242182 @@ -39,7 +39,9 @@ #include /* Get _mm_malloc () and _mm_free (). */ +#if __STDC_HOSTED__ #include +#endif We would need to apply the same patch to the gcc header file in gcc 4.9. I'm not sure if that will be allowed, since the direction we are going in is to support gcc as an external toolchain, unless we can push that change upstream to gcc. I'll let the toolchain@ team decide that one. The alternative is to patch the aesni header files. This patch is a bit gross, but I was able to compile an entire GENERIC kernel (including aesni) with gcc 4.9: Index: aesni/aesencdec.h =================================================================== --- aesni/aesencdec.h (revision 280912) +++ aesni/aesencdec.h (working copy) @@ -27,6 +27,11 @@ * */ +#ifdef _KERNEL +/* Suppress inclusion of gcc's mm_malloc.h header */ +#define _MM_MALLOC_H_INCLUDED 1 +#endif + #include static inline void Index: aesni/aesni_ghash.c =================================================================== --- aesni/aesni_ghash.c (revision 280912) +++ aesni/aesni_ghash.c (working copy) @@ -71,6 +71,11 @@ #include #endif +#ifdef _KERNEL +/* Suppress inclusion of gcc's mm_malloc.h header */ +#define _MM_MALLOC_H_INCLUDED 1 +#endif + #include #include #include Index: aesni/aesni_wrap.c =================================================================== --- aesni/aesni_wrap.c (revision 280912) +++ aesni/aesni_wrap.c (working copy) @@ -45,6 +45,11 @@ #include #include "aesencdec.h" +#ifdef _KERNEL +/* Suppress inclusion of gcc's mm_malloc.h header */ +#define _MM_MALLOC_H_INCLUDED 1 +#endif + #include MALLOC_DECLARE(M_AESNI); What's the best way to move forward on this? -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 15:01:55 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34A3FB32 for ; Wed, 1 Apr 2015 15:01:55 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1029FA6F for ; Wed, 1 Apr 2015 15:01:55 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t31F1sXx002045 for ; Wed, 1 Apr 2015 15:01:54 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t31F1sti002044; Wed, 1 Apr 2015 15:01:54 GMT (envelope-from root) Date: Wed, 1 Apr 2015 15:01:54 +0000 To: freebsd-toolchain@freebsd.org From: "imp (Warner Losh)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <0bc00c51a1fdf559825cc6a3f07b4efe@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUcCGI= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 15:01:55 -0000 imp added inline comments. BRANCH /head INLINE COMMENTS Makefile.inc1:416 The OBJCOPY was more my concern. Why do we need it for i386 on amd64 and nor for powerpc on powerpc64? REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, bapt, emaste, imp, rodrigc Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 15:14:12 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8682F304 for ; Wed, 1 Apr 2015 15:14:12 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 63CDCBE7 for ; Wed, 1 Apr 2015 15:14:12 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t31FEC8p014531 for ; Wed, 1 Apr 2015 15:14:12 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t31FECQj014528; Wed, 1 Apr 2015 15:14:12 GMT (envelope-from root) Date: Wed, 1 Apr 2015 15:14:12 +0000 To: freebsd-toolchain@freebsd.org From: "emaste (Ed Maste)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUcC0Q= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 15:14:12 -0000 emaste added inline comments. BRANCH /head INLINE COMMENTS Makefile.inc1:416 objcopy is used if you generate standalone debug. REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, bapt, emaste, imp, rodrigc Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 16:40:12 2015 Return-Path: Delivered-To: freebsd-toolchain@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2DA6B22E; Wed, 1 Apr 2015 16:40:12 +0000 (UTC) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id D64757E1; Wed, 1 Apr 2015 16:40:11 +0000 (UTC) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t31GeAAD013102 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 1 Apr 2015 09:40:10 -0700 (PDT) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t31GeAUq013101; Wed, 1 Apr 2015 09:40:10 -0700 (PDT) (envelope-from jmg) Date: Wed, 1 Apr 2015 09:40:10 -0700 From: John-Mark Gurney To: Craig Rodrigues Subject: Re: Kernel compilation failures with gcc 4.9 Message-ID: <20150401164010.GW51048@funkthat.com> References: <507CA323-8304-4FDB-A4B7-24A3683F265E@me.com> <1947119C-82A3-41C7-B9E5-98A99616F551@bsdimp.com> <20150401051051.GT51048@funkthat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Wed, 01 Apr 2015 09:40:10 -0700 (PDT) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 16:40:12 -0000 Craig Rodrigues wrote this message on Wed, Apr 01, 2015 at 07:59 -0700: > On Tue, Mar 31, 2015 at 10:10 PM, John-Mark Gurney wrote: > > > > > > This is an issue w/ gcc 4.9's headers... It is including stdlib.h, > > via mm_malloc.h which is conflicting w/ sys/malloc.h's version of free.. > > > > kan wrapped the include of mm_malloc.h in an #if __STDC_HOSTED__ which is > > why gcc 4.2 doesn't have the issue per my request a couple years ago: > > https://svnweb.freebsd.org/changeset/base/r242182 > > > > A similar fix needs to be applied here... > > > Interesting, so r242182 does this inside the gcc header file itself: > > --- head/contrib/gcc/config/i386/xmmintrin.h 2011/03/14 13:31:34 219639 > +++ head/contrib/gcc/config/i386/xmmintrin.h 2012/10/27 17:39:36 242182 > @@ -39,7 +39,9 @@ > #include > > /* Get _mm_malloc () and _mm_free (). */ > +#if __STDC_HOSTED__ > #include > +#endif > > > We would need to apply the same patch to the gcc header > file in gcc 4.9. I'm not sure if that will be allowed, since the > direction we are going in is to support gcc as an external toolchain, > unless we can push that change upstream to gcc. > I'll let the toolchain@ team decide that one. > > The alternative is to patch the aesni header files. This patch is > a bit gross, but I was able to compile an entire GENERIC kernel (including > aesni) with gcc 4.9: Yes, I did think of that... If we do this... We need to make sure to include a comment about this hack being for GCC, and/or we should probably make it dependant on GCC... Don't want to make things worse for compilers that do it properly... > +#define _MM_MALLOC_H_INCLUDED 1 -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 17:15:35 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 240752D1 for ; Wed, 1 Apr 2015 17:15:35 +0000 (UTC) Received: from mail-lb0-x22e.google.com (mail-lb0-x22e.google.com [IPv6:2a00:1450:4010:c04::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 95F0FC39 for ; Wed, 1 Apr 2015 17:15:34 +0000 (UTC) Received: by lbdc10 with SMTP id c10so41217856lbd.2 for ; Wed, 01 Apr 2015 10:15:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=HoeOLCO2l3cJSnusy//HjkIc+iRoVhVT59CrNX0530k=; b=cRkdZAjBAVFskj8LhgDTGFvX+JgaZFKDeKvFig+0xMRjZUsTI58QSShvvp9LcuSvIB Fj0708/ZR5zd2FRYRd0DWZdZoT+YO7K05eTg/fl+W8cW0O8dpVUKiNa1bZ7Nm8HXrLVt D4I4yRusG2iDrmcziIKi5k/ZvfBs9tooKXW+AXuB1NvSRCUS5sMZd6aUXTkVGDoFYZ8s n9iBkof+UgWgnbS8ZqyQNcb5MpnbGpMfHV1sqQL4rq5zWm4OrA44WGEWg8TSlMewq0Ze /SRkek4AdN5p1qtDZ80XylPn0WnMFNnFFGoIryFLyuYtgR+Ccoqh0jK05wzPGqz9MgA8 L0uQ== MIME-Version: 1.0 X-Received: by 10.112.170.132 with SMTP id am4mr36505045lbc.89.1427908531487; Wed, 01 Apr 2015 10:15:31 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Wed, 1 Apr 2015 10:15:31 -0700 (PDT) In-Reply-To: <056FF51B-CB8A-42E9-A7BA-B0A022F2640C@dsl-only.net> References: <056FF51B-CB8A-42E9-A7BA-B0A022F2640C@dsl-only.net> Date: Wed, 1 Apr 2015 10:15:31 -0700 X-Google-Sender-Auth: uIKpKoQc_8KHAHecaBZZKfzdShA Message-ID: Subject: Re: FYI: Things that I've noticed for powerpc64-xtoolchain-gcc... From: Craig Rodrigues To: Mark Millard Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 17:15:35 -0000 On Sun, Mar 29, 2015 at 1:13 AM, Mark Millard wrote: > You [Craig Rodrigues] seem to be checking some ??-xtoolchain-gcc things > officially. I've some user-experience notes from happening to use > powerpc64-xtoolchain-gcc in my exploration of FreeBSD. Hopefully some of it > might be of interest. It groups together information from various notices > as I was doing the explorations. > Thanks for doing these investigations. However, I have to say that your e-mails contain too much detail, and seem almost like rambling brain dumps. They are hard to follow, and I usually stop reading them about one quarter of the way through the e-mail. My mind can't absorb all the detail you are providing. I cannot speak for other people on the toolchain@ team, but I wouldn't be surprised if there are other people who feel the same as I do. In future, I suggest that you cut down your e-mails to be very concise. If you can extract the bare minimum of error message, and put that in the e-mail, with minimal discussion, that would be the best way to start. For your further analysis and full logs, put those on a web site. In your e-mail, you can put a URL pointer and tell people if they are still interested in looking at the problem, they can get the full logs and further analysis from your web site. It is even better if you can supply patches which you think fix the problem. That's the strategy that I have used, and I have found that it has worked very well, and the toolchain@ team has been super responsive. toolchain@ folks are very busy, so if you send e-mails which are more work to digest than the bugs they are trying to fix, they will tend to ignore your e-mails. -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 17:59:40 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ACC78DB7 for ; Wed, 1 Apr 2015 17:59:40 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 880E3141 for ; Wed, 1 Apr 2015 17:59:40 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t31Hxebi089812 for ; Wed, 1 Apr 2015 17:59:40 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t31HxeZ4089811; Wed, 1 Apr 2015 17:59:40 GMT (envelope-from root) Date: Wed, 1 Apr 2015 17:59:40 +0000 To: freebsd-toolchain@freebsd.org From: "dim (Dimitry Andric)" Subject: [Differential] [Updated, 38 lines] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <9071df57e702785128db44e1014d6c0e@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUcMgw= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 17:59:40 -0000 dim updated this revision to Diff 4577. dim added a comment. This revision now requires review to proceed. Add XOBJCOPY for powerpc too. CHANGES SINCE LAST UPDATE https://reviews.freebsd.org/D2187?vs=4554&id=4577 BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 AFFECTED FILES Makefile.inc1 lib/csu/i386-elf/Makefile sys/boot/i386/boot2/Makefile sys/boot/i386/gptboot/Makefile sys/boot/i386/gptzfsboot/Makefile sys/boot/i386/zfsboot/Makefile sys/boot/mips/beri/boot2/Makefile sys/boot/pc98/boot0.5/Makefile sys/boot/pc98/boot0/Makefile sys/boot/pc98/boot2/Makefile To: dim, rodrigc, imp, emaste, bapt Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 18:01:57 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43F35F35 for ; Wed, 1 Apr 2015 18:01:57 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 18627217 for ; Wed, 1 Apr 2015 18:01:57 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t31I1uin094269 for ; Wed, 1 Apr 2015 18:01:56 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t31I1uZ1094268; Wed, 1 Apr 2015 18:01:56 GMT (envelope-from root) Date: Wed, 1 Apr 2015 18:01:56 +0000 To: freebsd-toolchain@freebsd.org From: "emaste (Ed Maste)" Subject: [Differential] [Accepted] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUcMpQ= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 18:01:57 -0000 emaste accepted this revision. emaste added a comment. This revision is now accepted and ready to land. LGTM BRANCH /head REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, imp, bapt, emaste Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 18:02:43 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 84761F6F for ; Wed, 1 Apr 2015 18:02:43 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 60E65226 for ; Wed, 1 Apr 2015 18:02:43 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t31I2hWV094852 for ; Wed, 1 Apr 2015 18:02:43 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t31I2heC094851; Wed, 1 Apr 2015 18:02:43 GMT (envelope-from root) Date: Wed, 1 Apr 2015 18:02:43 +0000 To: freebsd-toolchain@freebsd.org From: "dim (Dimitry Andric)" Subject: [Differential] [Commented On] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUcMsM= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 18:02:43 -0000 dim added inline comments. BRANCH /head INLINE COMMENTS Makefile.inc1:427 Btw, I'm not sure about AS here, since it might not even be used in the 32 bit stage, and also I'm not sure of the syntax. Is it -a32? REVISION DETAIL https://reviews.freebsd.org/D2187 To: dim, rodrigc, imp, bapt, emaste Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 20:35:52 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0EA0AA41; Wed, 1 Apr 2015 20:35:52 +0000 (UTC) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "tensor.andric.com", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BCD8D6ED; Wed, 1 Apr 2015 20:35:51 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7::9c0:282a:9cc3:83a3] (unknown [IPv6:2001:7b8:3a7:0:9c0:282a:9cc3:83a3]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 50C7A5C2E; Wed, 1 Apr 2015 22:35:43 +0200 (CEST) Subject: Re: profile_rt from llvm folks? Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_205730C4-C09C-4491-A740-9A600AE75969"; protocol="application/pgp-signature"; micalg=pgp-sha1 X-Pgp-Agent: GPGMail 2.5b6 From: Dimitry Andric In-Reply-To: Date: Wed, 1 Apr 2015 22:35:35 +0200 Message-Id: <9C59EF67-014F-4EA1-B4F5-8E69A5C3E0FD@FreeBSD.org> References: To: NGie Cooper X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-toolchain@freebsd.org" , Benno Rice X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 20:35:52 -0000 --Apple-Mail=_205730C4-C09C-4491-A740-9A600AE75969 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii On 01 Apr 2015, at 02:03, NGie Cooper wrote: > > Hi all, > We've recently integrated a version of profile_rt from the llvm > folks internally to replace gcov for code coverage. I was wondering if > there was a plan to replace the copy of gcov in FreeBSD with the same > (either in the base system, ports, or both). I personally have no plans to do so, but the build of libprofile_rt.a was added in r276857, at least. -Dimitry --Apple-Mail=_205730C4-C09C-4491-A740-9A600AE75969 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.27 iEYEARECAAYFAlUcVp4ACgkQsF6jCi4glqPyUACeIKR6BXDrNsB/ABHGnIAPJFSE DaQAoO9wjRBIN3GKXgQBpo6jQXGxQlXb =MHl6 -----END PGP SIGNATURE----- --Apple-Mail=_205730C4-C09C-4491-A740-9A600AE75969-- From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 21:31:44 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3926712D; Wed, 1 Apr 2015 21:31:44 +0000 (UTC) Received: from mail-ie0-x236.google.com (mail-ie0-x236.google.com [IPv6:2607:f8b0:4001:c03::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id F1172D66; Wed, 1 Apr 2015 21:31:43 +0000 (UTC) Received: by ierf6 with SMTP id f6so54503843ier.2; Wed, 01 Apr 2015 14:31:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=t4usCs5hsiexxezQa31m61OaB2g0m41flOjs0aURsqk=; b=UnMVSi+aLZwguV30mRxLW/xusO9IRv87ga47P9nFQF4l8VvX6tMsBVVCfwhwrR5B8a Ny3miFpHSTdBuve6RSVMwOz3/+H3fCTWE4LgSav2vj1Dks/b19XiVuozt3YQedmBpiG6 6+PKypkg6cNTllGkxdkXKWRlSJTPihUnkk+8JPZXZ07sotFJybMpGRAzdIgDbIv3hjxx PnySQMKzQEH040GdolRUr1CjLzD+S+mH9WEDVS5LzBbCMTXBgTSnUm08RxpxB10aCHrx phewKKrN5mv6yAohzYqRzCC61JuB6vKoVvoq09CQHyyJl8/P1HjJFpPnqUrjbcwVOjNf dDZw== X-Received: by 10.50.36.104 with SMTP id p8mr15402624igj.16.1427923903338; Wed, 01 Apr 2015 14:31:43 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.158.19 with HTTP; Wed, 1 Apr 2015 14:31:23 -0700 (PDT) In-Reply-To: <9C59EF67-014F-4EA1-B4F5-8E69A5C3E0FD@FreeBSD.org> References: <9C59EF67-014F-4EA1-B4F5-8E69A5C3E0FD@FreeBSD.org> From: Ed Maste Date: Wed, 1 Apr 2015 17:31:23 -0400 X-Google-Sender-Auth: PDyNQSazeKcEbYms7aRcYRUJuMk Message-ID: Subject: Re: profile_rt from llvm folks? To: Dimitry Andric Content-Type: text/plain; charset=UTF-8 Cc: "freebsd-toolchain@freebsd.org" , Benno Rice , NGie Cooper X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 21:31:44 -0000 On 1 April 2015 at 16:35, Dimitry Andric wrote: > On 01 Apr 2015, at 02:03, NGie Cooper wrote: >> >> Hi all, >> We've recently integrated a version of profile_rt from the llvm >> folks internally to replace gcov for code coverage. I was wondering if >> there was a plan to replace the copy of gcov in FreeBSD with the same >> (either in the base system, ports, or both). > > I personally have no plans to do so, but the build of libprofile_rt.a > was added in r276857, at least. Yes, as of that change one can compile with --coverage, and .gcda and .gcno files will be produced via the functionality in libprofile_rt.a. gcov(1) is able to use them, but when I tried llvm-cov it didn't work correctly; in any case, llvm-cov is now on the roadmap for our toolchain. -Ed From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 21:44:50 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75340991 for ; Wed, 1 Apr 2015 21:44:50 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 1D151E9A for ; Wed, 1 Apr 2015 21:44:49 +0000 (UTC) Received: (qmail 22225 invoked from network); 1 Apr 2015 21:44:47 -0000 Received: from unknown (HELO mail-cs-02.app.dca.reflexion.local) (10.81.19.2) by 0 (rfx-qmail) with SMTP; 1 Apr 2015 21:44:47 -0000 Received: by mail-cs-02.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Wed, 01 Apr 2015 17:44:47 -0400 (EDT) Received: (qmail 9767 invoked from network); 1 Apr 2015 21:44:47 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Apr 2015 21:44:47 -0000 X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id B52DA1C43A2; Wed, 1 Apr 2015 14:44:42 -0700 (PDT) From: Mark Millard Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Subject: Shorter report: powerpc64-xtoolchain-gcc use fails from powerpc (non-64) Message-Id: Date: Wed, 1 Apr 2015 14:44:46 -0700 To: FreeBSD Toolchain , FreeBSD PowerPC ML Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) X-Mailer: Apple Mail (2.2070.6) X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 21:44:50 -0000 Attempting to use CROSS_TOOLCHAIN=3Dpowerpc64-gcc on powerpc (non-64) = 11.0-CURRENT with TARGET_ARCH=3Dpowerpc64 gets: > --- crti.o --- > gcc -O2 -pipe -I/usr/srcC/lib/csu/powerpc64/../common = -I/usr/srcC/lib/csu/powerpc64/../../libc/include -mlongcall -std=3Dgnu99 = -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter = -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type = -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter = -Wcast-align -Wchar-subscripts -Winline -Wnested-externs = -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c = /usr/srcC/lib/csu/powerpc64/crti.S > ... > /usr/srcC/lib/csu/powerpc64/crti.S: Assembler messages: > /usr/srcC/lib/csu/powerpc64/crti.S:35: Error: junk at end of line, = first unrecognized character is `@' > /usr/srcC/lib/csu/powerpc64/crti.S:51: Error: junk at end of line, = first unrecognized character is `@' > *** [crti.o] Error code 1 >=20 Read below only for analysis. First I'll deal with the error messages. Then I'll deal with the "gcc". The lines of crti.S in question are: > .quad .L._init,.TOC.@tocbase,0 > ... > .quad .L._fini,.TOC.@tocbase,0 The error messages are because __powerpc64__ is not defined when = machine/asm.h is included so the wrong definition is used for = _ENTRY(...): > #ifdef __powerpc64__ > ... > #define _ENTRY(name) \ > .section ".text"; \ > .p2align 2; \ > .globl name; \ > .section ".opd","aw"; \ > .p2align 3; \ > name: \ > .quad DOT_LABEL(name),.TOC.@tocbase,0; \ > .previous; \ > .p2align 4; \ > TYPE_ENTRY(name) \ > DOT_LABEL(name): > ... > #else /* !__powerpc64__ */ > #define _ENTRY(name) \ > .text; \ > .p2align 4; \ > .globl name; \ > .type name,@function; \ > name: > #define _END(name) > #endif /* __powerpc64__ */ The (powerpc64 specific) Makefile may need to force a 64-bit usage (-m64 = ?), presuming that such is supported from the 32 bit environment. But the below may also/instead be involved for = CROSS_TOOLCHAIN=3Dpowerpc64-gcc. As for why the "gcc" despite the CROSS_TOOLCHAIN=3Dpowerpc64-gcc = context... The head/lib/csu/powerpc64/Makefile always attempts to force the use of = "gcc": > # XXX: See the log for r232932 as to why the above -mlongcall is = needed. Since > # clang doesn't support -mlongcall, and testing shows a clang linked = with a > # clang-built csu segfaults, this must currently be compiled with gcc. = Once > # clang supports -mlongcall, or we get a fixed ld, this can be = revisited. > CC:=3D gcc > COMPILER_TYPE:=3D gcc So if gcc 4.2.1 is present then by default the old gcc's assembler is = used instead of the CROSS_TOOLCHAIN=3Dpowerpc64-gcc one. Otherwise gcc = may not be found. The gcc 4.2.1 behavior need not match the CROSS_TOOLCHAIN=3Dpowerpc64-gcc = behavior for an otherwise-the-same command line. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 21:49:57 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B665DBE6 for ; Wed, 1 Apr 2015 21:49:57 +0000 (UTC) Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 82121EEF for ; Wed, 1 Apr 2015 21:49:57 +0000 (UTC) Received: by pdbni2 with SMTP id ni2so67826504pdb.1 for ; Wed, 01 Apr 2015 14:49:56 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=EIkxfLvIsqptWCLtox+98TaJkfyrwkT0bz4O+oGX6QY=; b=CUkvmf8WoJPZYBe0h+J6BX8YTVNKE3PQ6sYkS/fwmObERLP6txXC6/nZt+8/WG6dyQ e9LknT4LaIpci8s1/8BhR3WZplui4Gt5RoFhaCuUSN3ZnznDqb3zJVliKPKuLbIypU7b pEYB/2b9NZe/Blnc7VtjlceFDhudsp91NoWhe66PnS1jbG2pvzV1wAN/nIVz+EB+B9nI PHQBEpfurARgDKKvTPGreChUP8fQDDkdktOCgOq9SYeTwhqzZcLEm9BZhuZzCII2zC4k cuyaSyrUAcz8XdgQfHtwyAsbpXQH6sTIbro9SPxqWyiIjRFciSlguAkVIzN9pZC7YRtp JLeQ== X-Gm-Message-State: ALoCoQmHqoAQrbwE9j/a/+m4/G5OgE6YDVROFoBl8fFqbdqowDkBKJjQCwPTeLbdjcqNVojgx4xa X-Received: by 10.70.92.132 with SMTP id cm4mr80401773pdb.18.1427924996576; Wed, 01 Apr 2015 14:49:56 -0700 (PDT) Received: from lgmac-panastasopoulos-6.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id ae7sm3100462pac.19.2015.04.01.14.49.54 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 14:49:55 -0700 (PDT) Sender: Warner Losh Subject: Re: Shorter report: powerpc64-xtoolchain-gcc use fails from powerpc (non-64) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_67A6748E-28CF-4E69-985A-ECCD2F004B8E"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: Date: Wed, 1 Apr 2015 14:49:51 -0700 Message-Id: References: To: Mark Millard X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD Toolchain , FreeBSD PowerPC ML X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 21:49:57 -0000 --Apple-Mail=_67A6748E-28CF-4E69-985A-ECCD2F004B8E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 1, 2015, at 2:44 PM, Mark Millard wrote: >=20 > Attempting to use CROSS_TOOLCHAIN=3Dpowerpc64-gcc on powerpc (non-64) = 11.0-CURRENT with TARGET_ARCH=3Dpowerpc64 gets: >=20 >> --- crti.o --- >> gcc -O2 -pipe -I/usr/srcC/lib/csu/powerpc64/../common = -I/usr/srcC/lib/csu/powerpc64/../../libc/include -mlongcall -std=3Dgnu99 = -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter = -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type = -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter = -Wcast-align -Wchar-subscripts -Winline -Wnested-externs = -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c = /usr/srcC/lib/csu/powerpc64/crti.S >> ... >> /usr/srcC/lib/csu/powerpc64/crti.S: Assembler messages: >> /usr/srcC/lib/csu/powerpc64/crti.S:35: Error: junk at end of line, = first unrecognized character is `@' >> /usr/srcC/lib/csu/powerpc64/crti.S:51: Error: junk at end of line, = first unrecognized character is `@' >> *** [crti.o] Error code 1 >>=20 >=20 >=20 >=20 > Read below only for analysis. >=20 >=20 >=20 > First I'll deal with the error messages. Then I'll deal with the = "gcc". >=20 > The lines of crti.S in question are: >=20 >> .quad .L._init,.TOC.@tocbase,0 >> ... >> .quad .L._fini,.TOC.@tocbase,0 >=20 > The error messages are because __powerpc64__ is not defined when = machine/asm.h is included so the wrong definition is used for = _ENTRY(=E2=80=A6): The gcc port needs to be fixed, with changes fed upstream. >> #ifdef __powerpc64__ >> ... >> #define _ENTRY(name) \ >> .section ".text"; \ >> .p2align 2; \ >> .globl name; \ >> .section ".opd","aw"; \ >> .p2align 3; \ >> name: \ >> .quad DOT_LABEL(name),.TOC.@tocbase,0; \ >> .previous; \ >> .p2align 4; \ >> TYPE_ENTRY(name) \ >> DOT_LABEL(name): >> ... >> #else /* !__powerpc64__ */ >> #define _ENTRY(name) \ >> .text; \ >> .p2align 4; \ >> .globl name; \ >> .type name,@function; \ >> name: >> #define _END(name) >> #endif /* __powerpc64__ */ >=20 > The (powerpc64 specific) Makefile may need to force a 64-bit usage = (-m64 ?), presuming that such is supported from the 32 bit environment. Generally, we=E2=80=99ve not added those kinds of flags to the command = line. There=E2=80=99s many subtle issues in the tree trying to do = that=E2=80=A6 Warner --Apple-Mail=_67A6748E-28CF-4E69-985A-ECCD2F004B8E Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVHGf/AAoJEGwc0Sh9sBEAIZoP/1m2jc320czmLmlohqDGG+m4 KD82iXxH4wnBSTm5AJ9ivtpbV8rkeOu/f1Aw9l0eHPQaj9aAslvaDxDMjpX5kXaa mZGDjzGm4FegktXIhIf8LZo4rRHNNc6fML/qeqL9QYKEQFJqXsGjrtIpRKlkX4Ah 5q3HJcA9By5rxNn/ws2Bktjpcd/2s4gG4Dd4jy9QyjBxGuVjlPU5PeIxV3e5vZ/T RbNsrsV/Hsfi8APnI1kjFe3bp4Muu+/ER9rUKY4V2F/SGtotvhA6iwnoSFNJHaHa 46PA4+ybEXaDYTt+wwGM4FaLGvIG4mZXtBwctUnXZrH+w5oMfgxDiTCPebKmQDmR c+o8aLpXgJr6FdfBwYeuQTM2KcZ9WpbiGSLRoeHA0DPQC/som/sFj/OIqbn08Fce W/Wiw7BYCI1f8aRDWLH8E3xbd6maEp3WuRKLIE5fV5o/Y0Iw2p4T2EJSVcB9xMU7 T/9wh7hWfUNfV63E2uY6Qq5a4CqPzx9AFi9SkhBEp5mPadIgdjKRDMjU+6KAn/x8 PScWRX+xPCkOsLnA6eBYHqMJEAiXo/TgjH6ogyFZw7eEMiMBQHaYWoABn9vhhQ/K EgI+zGrJk0ZlBLSbm2eGbQqXYk9Sa/djhx+vjmK5HVPKeYhN3TQodTgVs2EN5b39 PIw70mMGZkvc6Cf6wo/m =le1J -----END PGP SIGNATURE----- --Apple-Mail=_67A6748E-28CF-4E69-985A-ECCD2F004B8E-- From owner-freebsd-toolchain@FreeBSD.ORG Wed Apr 1 23:37:25 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8E56E261 for ; Wed, 1 Apr 2015 23:37:25 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 470B6D3F for ; Wed, 1 Apr 2015 23:37:24 +0000 (UTC) Received: (qmail 18609 invoked from network); 1 Apr 2015 23:37:23 -0000 Received: from unknown (HELO mail-cs-01.app.dca.reflexion.local) (10.81.19.1) by 0 (rfx-qmail) with SMTP; 1 Apr 2015 23:37:23 -0000 Received: by mail-cs-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Wed, 01 Apr 2015 19:37:23 -0400 (EDT) Received: (qmail 15022 invoked from network); 1 Apr 2015 23:37:22 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 1 Apr 2015 23:37:22 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id 31DE11C43AA; Wed, 1 Apr 2015 16:37:17 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Shorter report: powerpc64-xtoolchain-gcc use fails from powerpc (non-64) From: Mark Millard In-Reply-To: Date: Wed, 1 Apr 2015 16:37:21 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <7AF12D5F-F4A0-429E-AEAE-4AEF2D35FE31@dsl-only.net> References: To: Warner Losh X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD Toolchain , FreeBSD PowerPC ML X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Apr 2015 23:37:25 -0000 On 2015-Apr-1, at 02:49 PM, Warner Losh wrote: >> On Apr 1, 2015, at 2:44 PM, Mark Millard wrote: >>=20 >> Attempting to use CROSS_TOOLCHAIN=3Dpowerpc64-gcc on powerpc (non-64) = 11.0-CURRENT with TARGET_ARCH=3Dpowerpc64 gets: >>=20 >>> --- crti.o --- >>> gcc -O2 -pipe -I/usr/srcC/lib/csu/powerpc64/../common = -I/usr/srcC/lib/csu/powerpc64/../../libc/include -mlongcall -std=3Dgnu99 = -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter = -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type = -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter = -Wcast-align -Wchar-subscripts -Winline -Wnested-externs = -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c = /usr/srcC/lib/csu/powerpc64/crti.S >>> ... >>> /usr/srcC/lib/csu/powerpc64/crti.S: Assembler messages: >>> /usr/srcC/lib/csu/powerpc64/crti.S:35: Error: junk at end of line, = first unrecognized character is `@' >>> /usr/srcC/lib/csu/powerpc64/crti.S:51: Error: junk at end of line, = first unrecognized character is `@' >>> *** [crti.o] Error code 1 >>>=20 >>=20 >>=20 >>=20 >> Read below only for analysis. >>=20 >>=20 >>=20 >> First I'll deal with the error messages. Then I'll deal with the = "gcc". >>=20 >> The lines of crti.S in question are: >>=20 >>> .quad .L._init,.TOC.@tocbase,0 >>> ... >>> .quad .L._fini,.TOC.@tocbase,0 >>=20 >> The error messages are because __powerpc64__ is not defined when = machine/asm.h is included so the wrong definition is used for = _ENTRY(=E2=80=A6): >=20 > The gcc port needs to be fixed, with changes fed upstream. The head/lib/csu/powerpc64/Makefile generated "gcc" as the command (see = above). That in turn ended up as using: /usr/bin/gcc , which is the = FreeBSD 4.2.1 system gcc. So no port was involved. That may be the (or a) problem: ${XCC} was not = being used. >>> #ifdef __powerpc64__ >>> ... >>> #define _ENTRY(name) \ >>> .section ".text"; \ >>> .p2align 2; \ >>> .globl name; \ >>> .section ".opd","aw"; \ >>> .p2align 3; \ >>> name: \ >>> .quad DOT_LABEL(name),.TOC.@tocbase,0; \ >>> .previous; \ >>> .p2align 4; \ >>> TYPE_ENTRY(name) \ >>> DOT_LABEL(name): >>> ... >>> #else /* !__powerpc64__ */ >>> #define _ENTRY(name) \ >>> .text; \ >>> .p2align 4; \ >>> .globl name; \ >>> .type name,@function; \ >>> name: >>> #define _END(name) >>> #endif /* __powerpc64__ */ >>=20 >> The (powerpc64 specific) Makefile may need to force a 64-bit usage = (-m64 ?), presuming that such is supported from the 32 bit environment. >=20 > Generally, we=E2=80=99ve not added those kinds of flags to the command = line. There=E2=80=99s many subtle issues in the tree trying to do = that=E2=80=A6 >=20 > Warner =46rom a powerpc (non-64) 11.0-CURRENT boot is the following supposed to = work by producing a powerpc64 appropriate result (no CROSS_TOOLCHAIN for = this question)?=20 make buildworld buildkernel KERNCONF=3DGENERIC64 TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 The standard v4.2.1 /usr/bin/gcc in a powerpc context (non-64) for that = make command would produce files for TARGET_ARCH=3Dpowerpc unless the = command lines specified otherwise. Notably the build environment is picking powerpc64 specific paths when = appropriate, such as: lib/csu/powerpc64/Makefile so that specific Makefile is not likely to be used when powerpc64 = handling is inappropriate, even executed from from a powerpc (non-64) = context. A different path (and so a distinct Makefile) would be used for = KERNCONF=3DGENERIC TARGET_ARCH=3Dpowerpc . =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-toolchain@FreeBSD.ORG Thu Apr 2 00:05:00 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 297D568D for ; Thu, 2 Apr 2015 00:05:00 +0000 (UTC) Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id E78BBFE7 for ; Thu, 2 Apr 2015 00:04:59 +0000 (UTC) Received: by pacgg7 with SMTP id gg7so66826641pac.0 for ; Wed, 01 Apr 2015 17:04:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=3wKLXYV6h7ix4e5hBnkc4of8pmP0i3yBHLVcvABxzE8=; b=gMJqNF3ubjRxd8kVC8pmXYbx5bbTUpTRgDCeE0ziHKUbfyzhwlFNh3Xuw65e9ZWJCU NaJBP0jNE+D5cFGQt7K8uy7AHOKPy1YOvaBD2qxTVyG3UzF3kqf7vAwRZ6raDL7JMtnX 7dRreEwwAQOsSmKaEiKfA88FbPN2dhxekf7FTpW8LvmQ3KPIYuhGiCzAOitVSmUb9sFT ye3h/x6er/8Lv4O2dz+EAQLCdXceniJbrn2QmOkyH37o64Ni3kdto4VJPQtbEhoE/ECw 2wRktqFYH1+Q2CWZ6SPhSYO3XGDo6vhXOw/5gZZA6OcJV/aGAxVm/PFijCeYTLPJVHZA CjkQ== X-Gm-Message-State: ALoCoQlflQ7rXGbqtNh3QRzGVBFKH2jiRpa8RvSc/nU+7wY32eTIraxBhigSZiZQKlmXsJ6z7AH3 X-Received: by 10.68.227.41 with SMTP id rx9mr13581234pbc.76.1427933098927; Wed, 01 Apr 2015 17:04:58 -0700 (PDT) Received: from lgmac-panastasopoulos-6.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id pb2sm3261349pdb.33.2015.04.01.17.04.57 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Apr 2015 17:04:58 -0700 (PDT) Sender: Warner Losh Subject: Re: Shorter report: powerpc64-xtoolchain-gcc use fails from powerpc (non-64) Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_74D210E6-0D36-42FC-A42F-78A09CB89345"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: <7AF12D5F-F4A0-429E-AEAE-4AEF2D35FE31@dsl-only.net> Date: Wed, 1 Apr 2015 17:04:54 -0700 Message-Id: <83AB15DC-4B96-489D-A74B-84A552050785@bsdimp.com> References: <7AF12D5F-F4A0-429E-AEAE-4AEF2D35FE31@dsl-only.net> To: Mark Millard X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD Toolchain , FreeBSD PowerPC ML X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 00:05:00 -0000 --Apple-Mail=_74D210E6-0D36-42FC-A42F-78A09CB89345 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 1, 2015, at 4:37 PM, Mark Millard wrote: >=20 >=20 > On 2015-Apr-1, at 02:49 PM, Warner Losh wrote: >=20 >=20 >>> On Apr 1, 2015, at 2:44 PM, Mark Millard = wrote: >>>=20 >>> Attempting to use CROSS_TOOLCHAIN=3Dpowerpc64-gcc on powerpc = (non-64) 11.0-CURRENT with TARGET_ARCH=3Dpowerpc64 gets: >>>=20 >>>> --- crti.o --- >>>> gcc -O2 -pipe -I/usr/srcC/lib/csu/powerpc64/../common = -I/usr/srcC/lib/csu/powerpc64/../../libc/include -mlongcall -std=3Dgnu99 = -Wsystem-headers -Wall -Wno-format-y2k -W -Wno-unused-parameter = -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Wreturn-type = -Wcast-qual -Wwrite-strings -Wswitch -Wshadow -Wunused-parameter = -Wcast-align -Wchar-subscripts -Winline -Wnested-externs = -Wredundant-decls -Wold-style-definition -Wno-pointer-sign -c = /usr/srcC/lib/csu/powerpc64/crti.S >>>> ... >>>> /usr/srcC/lib/csu/powerpc64/crti.S: Assembler messages: >>>> /usr/srcC/lib/csu/powerpc64/crti.S:35: Error: junk at end of line, = first unrecognized character is `@' >>>> /usr/srcC/lib/csu/powerpc64/crti.S:51: Error: junk at end of line, = first unrecognized character is `@' >>>> *** [crti.o] Error code 1 >>>>=20 >>>=20 >>>=20 >>>=20 >>> Read below only for analysis. >>>=20 >>>=20 >>>=20 >>> First I'll deal with the error messages. Then I'll deal with the = "gcc". >>>=20 >>> The lines of crti.S in question are: >>>=20 >>>> .quad .L._init,.TOC.@tocbase,0 >>>> ... >>>> .quad .L._fini,.TOC.@tocbase,0 >>>=20 >>> The error messages are because __powerpc64__ is not defined when = machine/asm.h is included so the wrong definition is used for = _ENTRY(=E2=80=A6): >>=20 >> The gcc port needs to be fixed, with changes fed upstream. >=20 > The head/lib/csu/powerpc64/Makefile generated "gcc" as the command = (see above). That in turn ended up as using: /usr/bin/gcc , which is the = FreeBSD 4.2.1 system gcc. >=20 > So no port was involved. That may be the (or a) problem: ${XCC} was = not being used. That=E2=80=99s an interesting hole. It should be. >>>> #ifdef __powerpc64__ >>>> ... >>>> #define _ENTRY(name) \ >>>> .section ".text"; \ >>>> .p2align 2; \ >>>> .globl name; \ >>>> .section ".opd","aw"; \ >>>> .p2align 3; \ >>>> name: \ >>>> .quad DOT_LABEL(name),.TOC.@tocbase,0; \ >>>> .previous; \ >>>> .p2align 4; \ >>>> TYPE_ENTRY(name) \ >>>> DOT_LABEL(name): >>>> ... >>>> #else /* !__powerpc64__ */ >>>> #define _ENTRY(name) \ >>>> .text; \ >>>> .p2align 4; \ >>>> .globl name; \ >>>> .type name,@function; \ >>>> name: >>>> #define _END(name) >>>> #endif /* __powerpc64__ */ >>>=20 >>> The (powerpc64 specific) Makefile may need to force a 64-bit usage = (-m64 ?), presuming that such is supported from the 32 bit environment. >>=20 >> Generally, we=E2=80=99ve not added those kinds of flags to the = command line. There=E2=80=99s many subtle issues in the tree trying to = do that=E2=80=A6 >>=20 >> Warner >=20 > =46rom a powerpc (non-64) 11.0-CURRENT boot is the following supposed = to work by producing a powerpc64 appropriate result (no CROSS_TOOLCHAIN = for this question)? >=20 > make buildworld buildkernel KERNCONF=3DGENERIC64 TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 This should work, modulo broken compilers. > The standard v4.2.1 /usr/bin/gcc in a powerpc context (non-64) for = that make command would produce files for TARGET_ARCH=3Dpowerpc unless = the command lines specified otherwise. Ah, so it is a =E2=80=98cross build=E2=80=99 situation... > Notably the build environment is picking powerpc64 specific paths when = appropriate, such as: >=20 > lib/csu/powerpc64/Makefile >=20 > so that specific Makefile is not likely to be used when powerpc64 = handling is inappropriate, even executed from from a powerpc (non-64) = context. A different path (and so a distinct Makefile) would be used for = KERNCONF=3DGENERIC TARGET_ARCH=3Dpowerpc . The hack in that Makefile likely needs to be revisited. Warner --Apple-Mail=_74D210E6-0D36-42FC-A42F-78A09CB89345 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVHIemAAoJEGwc0Sh9sBEAQOQQAKbYddNkWIRGpykQiDAEl8eh atc2rzxu+SLUh+KVKpphXf4VJaCaE6/ssj+ddwTFpVHUPRVFaqHoxSgZ5A3GYWZD /Fs2H4/4Bf0h4ztS9s2hgx169NGdvyzvRVFXS+Fwb2AKjU6ybm9eD8iMHfGrPv0D xwJvBWb5glCV7GzW0oO/ScUhpN2nzBzHi0tEnfvyR4ZT5l5n8vv5pJiH8jSnpb9i TaWNTKOuGiYIgEKaTlZHnGhE3IQk/Jpl05LsFMQNBbyPOr5gESe95lqssWeZi7IF 693cTdtX64hhxUOzL/V6HTSQYr6NDIpxs69tpUB2Y/r7Ay9s5clFv0uNWt/AmWVw g7wRMql4sIrtmmElXKtjihyuo8IAvouJccmoszDK3Oz4T9YHeFDnyHTrrUuFDjzp bMD8dypsLJen1+mxlhIa2Pfhp/HxUCcjhFoeVi+azyM6vpC3TqLP8x0xn94ZcIO5 AMjH8xDbBTtWJSB9WXezAUQ/mIZckAO9VJMmx+7hxEDEY4PgSK9/I/iXDLRleOwo 9mtmQlLEjPE2Vvi241jLI/6+pPHSywNG0goXBcZ4ZeyPUXAe8cF7Jv+M/zpxmAP2 ZFrSJyZWhjiErRBBwyaaDD9B0Zkh2FBNFAJ9a5okymrXBXvXZQ1XqvyvF6cIaKni ItEuzwV5pYnM6aPvhIMA =bo5E -----END PGP SIGNATURE----- --Apple-Mail=_74D210E6-0D36-42FC-A42F-78A09CB89345-- From owner-freebsd-toolchain@FreeBSD.ORG Thu Apr 2 03:17:58 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46C44BEE for ; Thu, 2 Apr 2015 03:17:58 +0000 (UTC) Received: from asp.reflexion.net (outbound-242.asp.reflexion.net [69.84.129.242]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DDD6487A for ; Thu, 2 Apr 2015 03:17:57 +0000 (UTC) Received: (qmail 20536 invoked from network); 2 Apr 2015 03:17:50 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 2 Apr 2015 03:17:50 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v7.40.1) with SMTP; Wed, 01 Apr 2015 23:17:50 -0400 (EDT) Received: (qmail 5577 invoked from network); 2 Apr 2015 03:17:50 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (DHE-RSA-AES256-SHA encrypted) SMTP; 2 Apr 2015 03:17:50 -0000 X-No-Relay: not in my network X-No-Relay: not in my network X-No-Relay: not in my network Received: from [192.168.1.8] (c-67-189-19-145.hsd1.or.comcast.net [67.189.19.145]) by iron2.pdx.net (Postfix) with ESMTPSA id AEE2C1C4052; Wed, 1 Apr 2015 20:17:43 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: Shorter report: powerpc64-xtoolchain-gcc use fails from powerpc (non-64) From: Mark Millard In-Reply-To: <83AB15DC-4B96-489D-A74B-84A552050785@bsdimp.com> Date: Wed, 1 Apr 2015 20:17:48 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <7AF12D5F-F4A0-429E-AEAE-4AEF2D35FE31@dsl-only.net> <83AB15DC-4B96-489D-A74B-84A552050785@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.2070.6) Cc: FreeBSD Toolchain , FreeBSD PowerPC ML X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 03:17:58 -0000 [I've omitted history going in a different direction than this note.] On 2015-Apr-1, at 02:49 PM, Warner Losh wrote: >=20 > On Apr 1, 2015, at 4:37 PM, Mark Millard wrote: >=20 >> =46rom a powerpc (non-64) 11.0-CURRENT boot is the following supposed = to work by producing a powerpc64 appropriate result (no CROSS_TOOLCHAIN = for this question)? >>=20 >> make buildworld buildkernel KERNCONF=3DGENERIC64 TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 >=20 > This should work, modulo broken compilers. >=20 >> The standard v4.2.1 /usr/bin/gcc in a powerpc context (non-64) for = that make command would produce files for TARGET_ARCH=3Dpowerpc unless = the command lines specified otherwise. >=20 > Ah, so it is a =E2=80=98cross build=E2=80=99 situation... >=20 >> Notably the build environment is picking powerpc64 specific paths = when appropriate, such as: >>=20 >> lib/csu/powerpc64/Makefile >>=20 >> so that specific Makefile is not likely to be used when powerpc64 = handling is inappropriate, even executed from from a powerpc (non-64) = context. A different path (and so a distinct Makefile) would be used for = KERNCONF=3DGENERIC TARGET_ARCH=3Dpowerpc . After some experimentation I think that I've learned that I'd not = guessed the existence of a required step to enable "make buildkernel = KERNCONF=3DGENERIC64 TARGET=3Dpowerpc TARGET_ARCH=3Dpowerpc64" from = powerpc: one first must do a... make kernel-toolchain KERNCONF=3DGENERIC64 TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 before trying buildkernel. Similarly if buildworld is going to be done = then make toolchain KERNCONF=3DGENERIC64 TARGET=3Dpowerpc = TARGET_ARCH=3Dpowerpc64 should be done first. These put in place a tailored gcc 4.2.1 build into the appropriate part = of the /usr/obj/... tree and once it exists the path used during make = picks up the sub-tree-specific gcc 4.2.1. The defaults for this tree-specific gcc do not require command line = options to specify the default context for the special TARGET_ARCH. Similarly for building for powerpc from powerpc64. =3D=3D=3D Mark Millard markmi at dsl-only.net From owner-freebsd-toolchain@FreeBSD.ORG Thu Apr 2 06:59:27 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6536CD13 for ; Thu, 2 Apr 2015 06:59:27 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 41C2FF13 for ; Thu, 2 Apr 2015 06:59:27 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t326xRMM017508 for ; Thu, 2 Apr 2015 06:59:27 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t326xRuD017507; Thu, 2 Apr 2015 06:59:27 GMT (envelope-from root) Date: Thu, 2 Apr 2015 06:59:26 +0000 To: freebsd-toolchain@freebsd.org From: "dim (Dimitry Andric)" Subject: [Differential] [Closed] D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage Message-ID: <4b92f6d22456af287dda340626e51490@localhost.localdomain> X-Priority: 3 Thread-Topic: D2187: Ensure cross assembler, linker and objcopy are used for the build32 stage X-Herald-Rules: <28> X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ZDFjZDBmZDdjODFjNWQ3YTFiYzkzYzkyYjU5IFUc6M4= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: , , MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 06:59:27 -0000 dim closed this revision. dim updated this revision to Diff 4593. dim added a comment. Closed by commit rS280980 (authored by @dim). REVISION DETAIL https://reviews.freebsd.org/D2187 AFFECTED FILES head/Makefile.inc1 head/lib/csu/i386-elf/Makefile head/sys/boot/i386/boot2/Makefile head/sys/boot/i386/gptboot/Makefile head/sys/boot/i386/gptzfsboot/Makefile head/sys/boot/i386/zfsboot/Makefile head/sys/boot/mips/beri/boot2/Makefile head/sys/boot/pc98/boot0.5/Makefile head/sys/boot/pc98/boot0/Makefile head/sys/boot/pc98/boot2/Makefile To: dim, rodrigc, imp, bapt, emaste Cc: emaste, imp, freebsd-toolchain From owner-freebsd-toolchain@FreeBSD.ORG Thu Apr 2 15:27:06 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8F67B267; Thu, 2 Apr 2015 15:27:06 +0000 (UTC) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EB122373; Thu, 2 Apr 2015 15:27:05 +0000 (UTC) Received: by labe2 with SMTP id e2so62734425lab.3; Thu, 02 Apr 2015 08:27:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=T5R2MPswVNhx8zxwb1cQgPs7zuatB8hscH9pcs/vIE8=; b=ebE4dSbjgnD4PbVz6BLQ5Slu5tWVTyNFgE1FZh8zyxcz4Y7ka58mLad0AYMZexQqEI Dyk+3jBt/cWYK68MaOx2Fr/JHq1cZ4fA1O7i2ZLvU91Wg3THHwcz48hr0K8+reOhr2tX NnTmcZJ6ZexYt7MYrUPW89OHTuChK9s2pkoO9LfTxWfWfbeyiVzJ4wyGASLdeatd+pNk Y4RQD7hlw45qz7dXkl/0BE+VoI2B9YjOl9fHSuQx6mTDjktD7UdPhvwszdO/XqlgIY40 vxHTdkHkjkmJunbF3LBRPKQTGFV66v2YQjlAWqHKaiJid3AHc12LiIaDdCeX8sA0rJV3 VKTg== MIME-Version: 1.0 X-Received: by 10.152.36.169 with SMTP id r9mr18079878laj.29.1427988424045; Thu, 02 Apr 2015 08:27:04 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Thu, 2 Apr 2015 08:27:03 -0700 (PDT) In-Reply-To: References: Date: Thu, 2 Apr 2015 08:27:03 -0700 X-Google-Sender-Auth: DuSntYqIfX7HjYk1qtkgIJHHKZM Message-ID: Subject: Re: Failed to build rescue with gcc 4.9 From: Craig Rodrigues To: FreeBSD Toolchain , "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 15:27:06 -0000 On Sat, Mar 28, 2015 at 2:34 PM, Craig Rodrigues wrote: > Hi, > > The build host VM that I used was FreeBSD 10.1-RELEASE, amd64. > > I took this patch for libc++ and applied it to my tree: > > http://reviews.llvm.org/D8461 > > I used this script to build with gcc 4.9: > > > https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-build.sh > > Building rescue failed. You can see the full build log here: > > > https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/26/console > > The relevant section seems to be this: > > --- rescue --- > /usr/local/bin/x86_64-portbld-freebsd10.0-gcc -isystem > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/include > > -L/builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp/usr/lib > > --sysroot=/builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/tmp > -B/usr/local/x86_64-freebsd/bin/ -static -o rescue rescue.o cat.lo > chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo > expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo > mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo > sh.lo sleep.lo stty.lo sync.lo test.lo rcp.lo csh.lo badsect.lo > camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo dumpfs.lo > dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo > gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo kldstat.lo > kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo > mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo mount_nullfs.lo > mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo > ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo > rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo > umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo bsdlabel.lo > fdisk.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo > gzip.lo bzip2.lo less.lo xz.lo tar.lo vi.lo id.lo zdb.lo chroot.lo > chown.lo > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue/../librescue/exec.o > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue/../librescue/getusershell.o > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue/../librescue/login_class.o > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue/../librescue/popen.o > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue/../librescue/rcmdsh.o > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue/../librescue/sysctl.o > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue/../librescue/system.o > -lcrypt -ledit -ljail -lkvm -ll -ltermcapw -lutil -lxo -lalias -lcam > -lncursesw -ldevstat -lipsec -llzma -lavl -lzpool -lzfs_core -lzfs > -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmt > -lsbuf -lufs -lz -lbz2 -larchive -lcrypto -lmd -lm cat.lo: file not > recognized: File truncated collect2: error: ld returned 1 exit > status *** [rescue] Error code 1 > > make[5]: stopped in > > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue > 1 error > > > I double checked. cat.lo is not a truncated file. > # ls -l cat.lo ; file cat.lo > -rw-r--r-- 1 jenkins wheel 13112 Mar 28 21:17 cat.lo > cat.lo: ELF 64-bit LSB relocatable, x86-64, version 1 (FreeBSD), stripped > > Any ideas? > -- > Craig > > On Tue, Mar 31, 2015 at 1:41 PM, Dimitry Andric wrote: > > I'm suspecting this might have something to do with crunchide, or least, > the copy of crunchide that is run for this: > > --- cat.lo --- > /usr/local/x86_64-freebsd/bin/ld -dc -r -o cat.lo cat_stub.o > /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_external_toolchain_gcc/rescue/rescue//builds/FreeBSD_HEAD_external_toolchain_gcc/bin/cat/cat.o > crunchide -k _crunched_cat_stub cat.lo > > If I look at my own build logs, it seems to pick the crunchide > executable in /usr/bin, and Makefile.inc1 does *not* build it during the > cross-tools stage if ${TARGET_ARCH} is the same as ${MACHINE_ARCH}: > > .if ${TARGET_ARCH} != ${MACHINE_ARCH} > .if ${MK_RESCUE} != "no" || defined(RELEASEDIR) > _crunchide= usr.sbin/crunch/crunchide > .endif > > However, this does not explain why my /usr/bin/crunchide seems to not > screw up cat.lo, while yours does. As far as I can see, we're both > building this on a stable/10 amd64 box... > > Maybe, as a hack, you can force cross-tools to build crunchide, by > patching Makefile.inc1 to ignore the arch check, and see what that > results in? > > Actually, I am building on a 10.1-RELEASE box. I was able to get this successful build: https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/38/console by applying this patch (the ${TARGET_ARCH} != ${MACHINE_ARCH} checks seemed wrong to me): Index: Makefile.inc1 =================================================================== --- Makefile.inc1 (revision 280979) +++ Makefile.inc1 (working copy) @@ -1457,12 +1457,9 @@ # we get done with the earlier stages. It is the last set of tools needed # to begin building the target binaries. # -.if ${TARGET_ARCH} != ${MACHINE_ARCH} .if ${TARGET_ARCH} == "amd64" || ${TARGET_ARCH} == "i386" _btxld= usr.sbin/btxld .endif -.endif -.if ${TARGET_ARCH} != ${MACHINE_ARCH} .if ${MK_RESCUE} != "no" || defined(RELEASEDIR) _crunchide= usr.sbin/crunch/crunchide .endif @@ -1469,7 +1466,6 @@ .if ${TARGET_ARCH} == "i386" && defined(RELEASEDIR) _kgzip= usr.sbin/kgzip .endif -.endif # If we're given an XAS, don't build binutils. .if ${XAS:M/*} == "" -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Thu Apr 2 15:42:00 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E7D08BE for ; Thu, 2 Apr 2015 15:42:00 +0000 (UTC) Received: from mail-pa0-f50.google.com (mail-pa0-f50.google.com [209.85.220.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 26B787E3 for ; Thu, 2 Apr 2015 15:41:59 +0000 (UTC) Received: by pactp5 with SMTP id tp5so87617679pac.1 for ; Thu, 02 Apr 2015 08:41:53 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=o37khhpnpPMRlzPPXzFxDeRUJi5x0HQiYQjOVrMUgE8=; b=gzMBAU652KnG6Lp2E9bFtYUGPAvm5gCzf2RqAvfHFTpsrg03Sx7kFd0409cPLX+VE5 rzvj2hxK1QN0MXk54PTcTXoMoEPsn7CaseJlU02LFpN1vTJDUOqWoai88YzJQVlGkp+a 2p3wy6sCIsIWz4pwd4S4UJaIrwuaBn3GLzN7AIL2C3kQae2jqLcXhzOnArZGmRBGgBEE 8QGIOr+b6MNskK4IF5rtWvSSfDdAmSleod4S0KfUQQU6y2/EU8U0dXzd/4lFVNNXjt+A NVkafsW5ITr8o4stZzG+3+6K8eVMW4wKEFrREDsl9n8vxLkRwP9Ut5tvue7j2GuPxHoR 9uEA== X-Gm-Message-State: ALoCoQlw2SurRR+IKwUo1GDo/gCIP+1fdRmrJYql8YltmmB2Y7/s25VdJSWKwvvFojXIZVtnW3CC X-Received: by 10.70.129.72 with SMTP id nu8mr88071396pdb.72.1427989312956; Thu, 02 Apr 2015 08:41:52 -0700 (PDT) Received: from [198.18.104.37] ([12.27.65.194]) by mx.google.com with ESMTPSA id ob7sm5608122pdb.13.2015.04.02.08.41.51 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 02 Apr 2015 08:41:52 -0700 (PDT) Sender: Warner Losh Subject: Re: Failed to build rescue with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_121E348A-F3E2-4DB3-ADB8-0B3ABFD4A1B9"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: Date: Thu, 2 Apr 2015 08:41:50 -0700 Message-Id: References: To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Apr 2015 15:42:00 -0000 --Apple-Mail=_121E348A-F3E2-4DB3-ADB8-0B3ABFD4A1B9 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 2, 2015, at 8:27 AM, Craig Rodrigues = wrote: >=20 > On Sat, Mar 28, 2015 at 2:34 PM, Craig Rodrigues > wrote: >=20 >> Hi, >>=20 >> The build host VM that I used was FreeBSD 10.1-RELEASE, amd64. >>=20 >> I took this patch for libc++ and applied it to my tree: >>=20 >> http://reviews.llvm.org/D8461 >>=20 >> I used this script to build with gcc 4.9: >>=20 >>=20 >> = https://github.com/freebsd/freebsd-ci/blob/master/scripts/build/cross-buil= d.sh >>=20 >> Building rescue failed. You can see the full build log here: >>=20 >>=20 >> = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/26/con= sole >>=20 >> The relevant section seems to be this: >>=20 >> --- rescue --- >> /usr/local/bin/x86_64-portbld-freebsd10.0-gcc -isystem >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/tmp/usr/include >>=20 >> = -L/builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_exte= rnal_toolchain_gcc/tmp/usr/lib >>=20 >> = --sysroot=3D/builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD= _HEAD_external_toolchain_gcc/tmp >> -B/usr/local/x86_64-freebsd/bin/ -static -o rescue rescue.o cat.lo >> chflags.lo chio.lo chmod.lo cp.lo date.lo dd.lo df.lo echo.lo ed.lo >> expr.lo getfacl.lo hostname.lo kenv.lo kill.lo ln.lo ls.lo mkdir.lo >> mv.lo pkill.lo ps.lo pwd.lo realpath.lo rm.lo rmdir.lo setfacl.lo >> sh.lo sleep.lo stty.lo sync.lo test.lo rcp.lo csh.lo badsect.lo >> camcontrol.lo ccdconfig.lo clri.lo devfs.lo dmesg.lo dump.lo = dumpfs.lo >> dumpon.lo fsck.lo fsck_ffs.lo fsck_msdosfs.lo fsdb.lo fsirand.lo >> gbde.lo geom.lo ifconfig.lo init.lo kldconfig.lo kldload.lo = kldstat.lo >> kldunload.lo ldconfig.lo md5.lo mdconfig.lo mdmfs.lo mknod.lo >> mount.lo mount_cd9660.lo mount_msdosfs.lo mount_nfs.lo = mount_nullfs.lo >> mount_udf.lo mount_unionfs.lo newfs.lo newfs_msdos.lo nos-tun.lo >> ping.lo reboot.lo restore.lo rcorder.lo route.lo routed.lo rtquery.lo >> rtsol.lo savecore.lo spppcontrol.lo swapon.lo sysctl.lo tunefs.lo >> umount.lo atmconfig.lo ping6.lo ipf.lo zfs.lo zpool.lo bsdlabel.lo >> fdisk.lo dhclient.lo head.lo mt.lo nc.lo sed.lo tail.lo tee.lo >> gzip.lo bzip2.lo less.lo xz.lo tar.lo vi.lo id.lo zdb.lo chroot.lo >> chown.lo >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue/../librescue/exec.o >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue/../librescue/getusershell.o >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue/../librescue/login_class.o >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue/../librescue/popen.o >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue/../librescue/rcmdsh.o >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue/../librescue/sysctl.o >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue/../librescue/system.o >> -lcrypt -ledit -ljail -lkvm -ll -ltermcapw -lutil -lxo -lalias -lcam >> -lncursesw -ldevstat -lipsec -llzma -lavl -lzpool -lzfs_core -lzfs >> -lnvpair -lpthread -luutil -lumem -lgeom -lbsdxml -lkiconv -lmt >> -lsbuf -lufs -lz -lbz2 -larchive -lcrypto -lmd -lm cat.lo: file not >> recognized: File truncated collect2: error: ld returned 1 exit >> status *** [rescue] Error code 1 >>=20 >> make[5]: stopped in >>=20 >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue >> 1 error >>=20 >>=20 >> I double checked. cat.lo is not a truncated file. >> # ls -l cat.lo ; file cat.lo >> -rw-r--r-- 1 jenkins wheel 13112 Mar 28 21:17 cat.lo >> cat.lo: ELF 64-bit LSB relocatable, x86-64, version 1 (FreeBSD), = stripped >>=20 >> Any ideas? >> -- >> Craig >>=20 >>=20 >=20 > On Tue, Mar 31, 2015 at 1:41 PM, Dimitry Andric = wrote: >=20 >>=20 >> I'm suspecting this might have something to do with crunchide, or = least, >> the copy of crunchide that is run for this: >>=20 >> --- cat.lo --- >> /usr/local/x86_64-freebsd/bin/ld -dc -r -o cat.lo cat_stub.o >> = /builds/FreeBSD_HEAD_external_toolchain_gcc/obj/builds/FreeBSD_HEAD_extern= al_toolchain_gcc/rescue/rescue//builds/FreeBSD_HEAD_external_toolchain_gcc= /bin/cat/cat.o >> crunchide -k _crunched_cat_stub cat.lo >>=20 >> If I look at my own build logs, it seems to pick the crunchide >> executable in /usr/bin, and Makefile.inc1 does *not* build it during = the >> cross-tools stage if ${TARGET_ARCH} is the same as ${MACHINE_ARCH}: >>=20 >> .if ${TARGET_ARCH} !=3D ${MACHINE_ARCH} >> .if ${MK_RESCUE} !=3D "no" || defined(RELEASEDIR) >> _crunchide=3D usr.sbin/crunch/crunchide >> .endif >>=20 >> However, this does not explain why my /usr/bin/crunchide seems to not >> screw up cat.lo, while yours does. As far as I can see, we're both >> building this on a stable/10 amd64 box... >>=20 >> Maybe, as a hack, you can force cross-tools to build crunchide, by >> patching Makefile.inc1 to ignore the arch check, and see what that >> results in? >>=20 >>=20 > Actually, I am building on a 10.1-RELEASE box. >=20 > I was able to get this successful build: > = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/38/con= sole >=20 > by applying this patch (the ${TARGET_ARCH} !=3D ${MACHINE_ARCH} = checks > seemed wrong to me): Why do they seem wrong. The intent is that you=E2=80=99d only build = these tools when you are cross building. A long time ago, they were in the bootstrap = path, but every FreeBSD system for a long time now has adequate versions of them. If that=E2=80=99s not the case, then we perhaps need to revisit the = logic here. If we=E2=80=99ve suddenly started needing newer versions, that should be expressed in the logic as well. Warner > Index: Makefile.inc1 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- Makefile.inc1 (revision 280979) > +++ Makefile.inc1 (working copy) > @@ -1457,12 +1457,9 @@ > # we get done with the earlier stages. It is the last set of tools = needed > # to begin building the target binaries. > # > -.if ${TARGET_ARCH} !=3D ${MACHINE_ARCH} > .if ${TARGET_ARCH} =3D=3D "amd64" || ${TARGET_ARCH} =3D=3D "i386" > _btxld=3D usr.sbin/btxld > .endif > -.endif > -.if ${TARGET_ARCH} !=3D ${MACHINE_ARCH} > .if ${MK_RESCUE} !=3D "no" || defined(RELEASEDIR) > _crunchide=3D usr.sbin/crunch/crunchide > .endif > @@ -1469,7 +1466,6 @@ > .if ${TARGET_ARCH} =3D=3D "i386" && defined(RELEASEDIR) > _kgzip=3D usr.sbin/kgzip > .endif > -.endif >=20 > # If we're given an XAS, don't build binutils. > .if ${XAS:M/*} =3D=3D "" >=20 >=20 > -- > Craig > _______________________________________________ > freebsd-toolchain@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-toolchain > To unsubscribe, send any mail to = "freebsd-toolchain-unsubscribe@freebsd.org" --Apple-Mail=_121E348A-F3E2-4DB3-ADB8-0B3ABFD4A1B9 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVHWM+AAoJEGwc0Sh9sBEAP/YP/RYs/abLU74nd3LgbTSexke/ sUIB83gfr1PHOqaYVRmXfwm8H3a64BUpWzsgQ67z98a3T+GRC8Be7WGm59rwOBAF 9otI2SCL9E6Tmi13HldcEzSMJL79mmx2wWQr60vHt3XlMXf8gFljIQ5c117pZnXg r0+mkTPp7ZM5ibjxn/Q/0wadx9ONLdZXC3mEbmfitz+eHyU6vn3TJGfxyeT+my5C yjEEwT0B1hV1BzzyAlAMU3uohV/eZjsWWancnp4U8CA29+SfYDhOSjnv7tdbqkWQ yXK4IBYYEXTYDOipSbThOtNj/EBCINiTxG9v6aiua6vuxPQ92q0AxCq9rpAlkm8x vz8WScrAxO8OL3EU3PRHVY8WHW71BnhFCNXW0UQmL2jmtU3V8PmbJ/fyzLzKNQmf 7mgmf+hNaR5gbHpdipGlb07S1Ig7fgyNLZjTchA46Bqpmq75wwNi1/HvRmVrdh2Z f6M61PVfpTSv35qfOcKrZZZlSL/Oc/vgxrUKrKQq5LkMgYsJyqr4x3q/b0+qQ6mE L/xYKmnSq2VsYSMc4mGyawOfTXPVZniATyQyqb/7XsF12BNGQdrmqY7X4WreB7P9 RMQmZHWyJxYTpzOnl8ssd1Xy20MxBdX6XubK4baL8Z8GGjayT0jaOtzxMS3+y8DK ovssSbmQKO9opSSPa1XN =uhe9 -----END PGP SIGNATURE----- --Apple-Mail=_121E348A-F3E2-4DB3-ADB8-0B3ABFD4A1B9-- From owner-freebsd-toolchain@FreeBSD.ORG Fri Apr 3 16:58:40 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BBEA0DB6; Fri, 3 Apr 2015 16:58:40 +0000 (UTC) Received: from mail-lb0-x236.google.com (mail-lb0-x236.google.com [IPv6:2a00:1450:4010:c04::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3A64033C; Fri, 3 Apr 2015 16:58:40 +0000 (UTC) Received: by lboc7 with SMTP id c7so82076928lbo.1; Fri, 03 Apr 2015 09:58:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=K9FW+eOTK5bPmaVluo+cEY/qddwadwitUUDWZ1qi1Aw=; b=Mgv7LqUM6HiEltPtZ9+/cUDF63bkQzQEGwhnjc/SKYfMZSayP0z9klmueDfupp/tYl E3iR123Rl7YwLsG+jz1hmC6WIX9WjoIPkZfDTxXYF7tBoL++5aSaby1o6vk75pq3QEi4 TFk4a1wYSw1vLW3XnxnDRU3VSkq2mBOAeb5ZndC4tVXj151MHArhSZe3M3Cj0+jlKJYR AzVwh59ZU5+lPH1KzXvOvCLlhyhOkx1TbuFE5EDisbQiaFFN/LDg45pDHhWS3ib6+fcr GGXEDfoVPBRUA5ASGCkuE4uVFuDTu4VhAzNLRQ1nPIyD0mDgV0P2n5k7ShRqw021Hdbr aOFA== MIME-Version: 1.0 X-Received: by 10.112.8.76 with SMTP id p12mr2865460lba.29.1428080318171; Fri, 03 Apr 2015 09:58:38 -0700 (PDT) Sender: crodr001@gmail.com Received: by 10.112.108.168 with HTTP; Fri, 3 Apr 2015 09:58:38 -0700 (PDT) In-Reply-To: References: Date: Fri, 3 Apr 2015 09:58:38 -0700 X-Google-Sender-Auth: Ep014CyPsE3IiFmJkGKXIgGCYOc Message-ID: Subject: Re: Failed to build rescue with gcc 4.9 From: Craig Rodrigues To: FreeBSD Toolchain , "freebsd-testing@freebsd.org" Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 16:58:40 -0000 On Thu, Apr 2, 2015 at 8:27 AM, Craig Rodrigues wrote: > > Actually, I am building on a 10.1-RELEASE box. > > I was able to get this successful build: > > https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/38/console > > by applying this patch (the ${TARGET_ARCH} != ${MACHINE_ARCH} checks > seemed wrong to me): > > Index: Makefile.inc1 > =================================================================== > --- Makefile.inc1 (revision 280979) > +++ Makefile.inc1 (working copy) > @@ -1457,12 +1457,9 @@ > # we get done with the earlier stages. It is the last set of tools needed > # to begin building the target binaries. > # > -.if ${TARGET_ARCH} != ${MACHINE_ARCH} > .if ${TARGET_ARCH} == "amd64" || ${TARGET_ARCH} == "i386" > _btxld= usr.sbin/btxld > .endif > -.endif > -.if ${TARGET_ARCH} != ${MACHINE_ARCH} > .if ${MK_RESCUE} != "no" || defined(RELEASEDIR) > _crunchide= usr.sbin/crunch/crunchide > .endif > @@ -1469,7 +1466,6 @@ > .if ${TARGET_ARCH} == "i386" && defined(RELEASEDIR) > _kgzip= usr.sbin/kgzip > .endif > -.endif > > # If we're given an XAS, don't build binutils. > .if ${XAS:M/*} == "" > > I backed out this patch from my tree, and rebuilt everything in my 10.1-RELEASE VM from the latest CURRENT sources. At this point, I ran into the same problem building rescue which I reported in https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.html I put the patch back in my tree, and recompiled everything, and the problem went away. To reliably build the tree, I think this patch should go in, so that these tools are properly bootstrapped during the build. -- Craig From owner-freebsd-toolchain@FreeBSD.ORG Fri Apr 3 17:02:55 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2FF8E162 for ; Fri, 3 Apr 2015 17:02:55 +0000 (UTC) Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id DBEBF5F1 for ; Fri, 3 Apr 2015 17:02:54 +0000 (UTC) Received: by ignm3 with SMTP id m3so67971493ign.0 for ; Fri, 03 Apr 2015 10:02:47 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=f/Ai4bcGwPCJJNWPAKCJxvAZZaLRRLdThpatUPNlsjA=; b=HKi9H+URGq/DrI1cC6ZEwil6W6/gt9Qy+F5bBQHa+E1IYczirwz9zwXawHimIUX6mH a1uwDb0Ez6ZJ+s0fW0S0wtlPZPKQjfG7AcpiqMFEFLsM1LJ9bEO9iFBiiJeYBcHWhEck JpxLZH9/uA4QMQJ0ye1PXCDSM1OZTBiVU+hgao9yC0tNBalfEirnOrKHbpq+kLOP1wog a+fD0RbwBFbu3qYGFgLjiPtd1vnfE8E//tmkiYfadmSW5l0e2Ww0zVtvBFQEvjbvGoGj NhhggxQXustEMSZs7luvL7oXdwqBX8Yc3+0fYem56zcLIK04B9u2tTtV0fxVdDRJwZ1q 4f1g== X-Gm-Message-State: ALoCoQmuREIlPGHzh0qSt4mDF3SEvfCzHOU+rBVXQ63EdoQ3rfcK8Bbf3iHoD9WisY6+hNNH11k+ X-Received: by 10.42.121.73 with SMTP id i9mr5004878icr.91.1428080567832; Fri, 03 Apr 2015 10:02:47 -0700 (PDT) Received: from netflix-mac-wired.bsdimp.com ([50.253.99.174]) by mx.google.com with ESMTPSA id m136sm5815956iom.21.2015.04.03.10.02.46 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Apr 2015 10:02:46 -0700 (PDT) Sender: Warner Losh Subject: Re: Failed to build rescue with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_2BDF8736-4C30-446F-AD28-5CF3A9FFAD91"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: Date: Fri, 3 Apr 2015 11:02:45 -0600 Message-Id: <2D2191D4-DB6F-4889-9CA9-DFEE495D8302@bsdimp.com> References: To: Craig Rodrigues X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 17:02:55 -0000 --Apple-Mail=_2BDF8736-4C30-446F-AD28-5CF3A9FFAD91 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 3, 2015, at 10:58 AM, Craig Rodrigues = wrote: >=20 > On Thu, Apr 2, 2015 at 8:27 AM, Craig Rodrigues = wrote: >=20 >>=20 >> Actually, I am building on a 10.1-RELEASE box. >>=20 >> I was able to get this successful build: >>=20 >> = https://jenkins.freebsd.org/job/FreeBSD_HEAD_external_toolchain_gcc/38/con= sole >>=20 >> by applying this patch (the ${TARGET_ARCH} !=3D ${MACHINE_ARCH} = checks >> seemed wrong to me): >>=20 >> Index: Makefile.inc1 >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> --- Makefile.inc1 (revision 280979) >> +++ Makefile.inc1 (working copy) >> @@ -1457,12 +1457,9 @@ >> # we get done with the earlier stages. It is the last set of tools = needed >> # to begin building the target binaries. >> # >> -.if ${TARGET_ARCH} !=3D ${MACHINE_ARCH} >> .if ${TARGET_ARCH} =3D=3D "amd64" || ${TARGET_ARCH} =3D=3D "i386" >> _btxld=3D usr.sbin/btxld >> .endif >> -.endif >> -.if ${TARGET_ARCH} !=3D ${MACHINE_ARCH} >> .if ${MK_RESCUE} !=3D "no" || defined(RELEASEDIR) >> _crunchide=3D usr.sbin/crunch/crunchide >> .endif >> @@ -1469,7 +1466,6 @@ >> .if ${TARGET_ARCH} =3D=3D "i386" && defined(RELEASEDIR) >> _kgzip=3D usr.sbin/kgzip >> .endif >> -.endif >>=20 >> # If we're given an XAS, don't build binutils. >> .if ${XAS:M/*} =3D=3D "" >>=20 >>=20 >=20 > I backed out this patch from my tree, and rebuilt everything > in my 10.1-RELEASE VM from the latest CURRENT sources. At this > point, I ran into the same problem building rescue which I reported in > = https://lists.freebsd.org/pipermail/freebsd-toolchain/2015-March/001545.ht= ml >=20 > I put the patch back in my tree, and recompiled everything, and the > problem went away. >=20 > To reliably build the tree, I think this patch should go in, so that = these > tools are properly bootstrapped during the build. That shows that something in the list is needed. Likely only crunchhide. It doesn=E2=80=99t tell us why we need it, or when we started needing = it, or what other conditions we might need it. This information is critical to = document so we know when we can stop doing it in the future. I=E2=80=99m = extremely reluctant to commit this until we know these details. Sorry for being a bit of a pain about this, but these lists are = something that I=E2=80=99ll be maintaining long into the future and we=E2=80=99ve had = issues in the past where people would just hack something in and not document, then = lovingly copy it over and over w/o understanding :( Warner --Apple-Mail=_2BDF8736-4C30-446F-AD28-5CF3A9FFAD91 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVHse1AAoJEGwc0Sh9sBEADggP/iCbB09Q7erlfSLE+9AWKGyC Q1bsWfq8H4srlKML8srlMidogSXpn5m9CBRIPKlOhOmhF9bdeJHO3uM4WYoU1WF8 I7AMl7b2x6PRicxpJJL0eSGw3AL8iuXFwRv/beCAqoe4FTh96fq633klATmwxHV2 MGt0WFhS7gQ0GyhBI2AyDUsb5k5dmSgF7HIbADcXlju/v5q0WU0EK+UkpRNAGXME EcvW+XRa9OJFkl+ZqWvZab69AzAd7xLtAagwMWBzYT2sc2fyOUQaVHW4nYGgf1Wq GOu4Yb+pYmsQiVNfqDS9eLMIQvB4MXtRXUnMAyrmtLkvp6p72sW4oI7g49GNkVGd n8/cv9jd1Qqx9hhlLUe/8vuhKh/hStyG0A6OnfFP3gr3Caoz9Jeb5NMtOZyRfnvg 3fGA7PRir/NgA8Xo0Gh6BSuDSo+ybELQQNn8YWL5iBcZ8bSFRJww6DM7anaJux+M PSLhC4FvJs65SwLUNLEpi2M2nN7w5aN3WiwV+Y+TxQaDN592om4U7X/RKfS2oltn x3P5W6EQWIVlm4woIQrYQNdMMHh6h0YciY33UwdDVXaXhmmvDiN8gu5PXa+X2gvr RwWZZHmXQcR81K26IZd/Yu2StzX8QZiuJjpsVgmR0pCHLsSnsbF6Uj9Of4p+KT+E jECHoywxjgMMIKTCl1Re =tNOu -----END PGP SIGNATURE----- --Apple-Mail=_2BDF8736-4C30-446F-AD28-5CF3A9FFAD91-- From owner-freebsd-toolchain@FreeBSD.ORG Fri Apr 3 20:39:54 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 35FCE9FE; Fri, 3 Apr 2015 20:39:54 +0000 (UTC) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EBBB8F5F; Fri, 3 Apr 2015 20:39:53 +0000 (UTC) Received: by ierf6 with SMTP id f6so97695372ier.2; Fri, 03 Apr 2015 13:39:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type:content-transfer-encoding; bh=6oDlLOuxwNN1+gyd/RyR+c8tdOuvmY3OJZi46ZBLfN0=; b=MddINJgHPp9WFRsYR0w6UK4+GYlrvPfZAKqIEe0SQ+2y4JTaE97CYlNf2REqBpVR7f tXveuQTIA+4N4JMThJpkC6P6kiij8GMFsUh2W0cJgWEjMEguQlL2t3ixLpB+7zky0iAw kpf3KiwMIplEhzyKpkZAyG3P+t7v4act2eA1ApHhkxxNCzgdIsDdW7W87mrTL2adQ1bq 5bp/C14w9PH8nmJrmqd+BooXdgt1+6VdWD8uQ4PMN3LHqCWpVciu9LhumdVp6nk1ze9k Ga3g2nwt8MXO1SbO4NJXkTLFthf1FQrk3CUEfVxxlwU0x38ficGGU4inzaB4XZmYRxsm 3kGQ== X-Received: by 10.50.28.8 with SMTP id x8mr7233023igg.19.1428093593459; Fri, 03 Apr 2015 13:39:53 -0700 (PDT) MIME-Version: 1.0 Sender: carpeddiem@gmail.com Received: by 10.107.158.19 with HTTP; Fri, 3 Apr 2015 13:39:32 -0700 (PDT) In-Reply-To: <2D2191D4-DB6F-4889-9CA9-DFEE495D8302@bsdimp.com> References: <2D2191D4-DB6F-4889-9CA9-DFEE495D8302@bsdimp.com> From: Ed Maste Date: Fri, 3 Apr 2015 16:39:32 -0400 X-Google-Sender-Auth: 0evGjqvq7s1u4OUwsVBsdGD3qiU Message-ID: Subject: Re: Failed to build rescue with gcc 4.9 To: Warner Losh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 20:39:54 -0000 On 3 April 2015 at 13:02, Warner Losh wrote: > That shows that something in the list is needed. Likely only crunchhide. > > It doesn=E2=80=99t tell us why we need it, or when we started needing it,= or what > other conditions we might need it. This information is critical to docume= nt > so we know when we can stop doing it in the future. I=E2=80=99m extremely= reluctant > to commit this until we know these details. Yes, it's crunchide. It was broken prior to r277259: | crunchide: Correct 64-bit section header offset | | For 64-bit binaries the Elf_Ehdr e_shoff is at offset 40, not 44. | Instead of using an incorrect hardcoded offset, let the compiler | figure it out for us with offsetof(). | | Differential Revision: https://reviews.freebsd.org/D1543 It's not completely clear to me why we did not encounter this before; a comment before the erroneous write states: /* * update the offset of section header table in elf * header if needed. */ so I presume something about the object file created by gcc 4.9 causes this code to be executed, while builds using the in-tree compiler did not. From owner-freebsd-toolchain@FreeBSD.ORG Fri Apr 3 21:10:13 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F0613EB3 for ; Fri, 3 Apr 2015 21:10:13 +0000 (UTC) Received: from mail-pa0-f41.google.com (mail-pa0-f41.google.com [209.85.220.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B840925F for ; Fri, 3 Apr 2015 21:10:13 +0000 (UTC) Received: by pabsx10 with SMTP id sx10so35387931pab.3 for ; Fri, 03 Apr 2015 14:10:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:message-id:references:to; bh=/kVKAgz9LqMeMUjx1y3pkQjuDdS9LggPoX5wPXt1+MM=; b=jwkzUFVxN4+Sm1Yb1nhAPk0dVnKiFQEKcvG0MPzK1roD0zGQD+GSTh4LAeA8rD+VFs Ud46QN+m63T8uul9+/yLaSZYdogAEgHjKR5oHEDDmU0dmqfKboJza4XhEHFKN5VtGmN9 7er6nZGi3i9RuAp4j7RgNPfsZmLZyMk+3fKTQnn2jUG5rqw2l35u+NrUTdA0cLOn3DyQ z5aJ83lP648EcxUxOaAsmiSBUhbrd0Fswer6ZJTZVGsaCjbJsl9zvwu54lGrDdvZ6y8X w6K8R4wgDnILRTBvJ3LQVzUltEomVSZgfHo18vzAFo2g8vyj6xoMM/yy0wj9POmnYoV0 qnqQ== X-Gm-Message-State: ALoCoQnbA301cE0kk/2+oMm4AcNdBiT+2KtaABzCYNVq0Zjfi2U//8f8sTq9hI0r1Agx80DkkqMq X-Received: by 10.70.98.139 with SMTP id ei11mr7191740pdb.3.1428095412796; Fri, 03 Apr 2015 14:10:12 -0700 (PDT) Received: from lgwl-doulam.corp.netflix.com ([69.53.236.236]) by mx.google.com with ESMTPSA id fm3sm9008105pab.29.2015.04.03.14.10.11 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Apr 2015 14:10:12 -0700 (PDT) Sender: Warner Losh Subject: Re: Failed to build rescue with gcc 4.9 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Content-Type: multipart/signed; boundary="Apple-Mail=_EDE77C46-E36F-4072-8E7E-46327059403A"; protocol="application/pgp-signature"; micalg=pgp-sha512 X-Pgp-Agent: GPGMail 2.5b6 From: Warner Losh In-Reply-To: Date: Fri, 3 Apr 2015 15:10:09 -0600 Message-Id: <04452C2A-FB67-465B-AE33-44ED2109672E@bsdimp.com> References: <2D2191D4-DB6F-4889-9CA9-DFEE495D8302@bsdimp.com> To: Ed Maste X-Mailer: Apple Mail (2.2070.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 21:10:14 -0000 --Apple-Mail=_EDE77C46-E36F-4072-8E7E-46327059403A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Apr 3, 2015, at 2:39 PM, Ed Maste wrote: >=20 > On 3 April 2015 at 13:02, Warner Losh wrote: >> That shows that something in the list is needed. Likely only = crunchhide. >>=20 >> It doesn=E2=80=99t tell us why we need it, or when we started needing = it, or what >> other conditions we might need it. This information is critical to = document >> so we know when we can stop doing it in the future. I=E2=80=99m = extremely reluctant >> to commit this until we know these details. >=20 > Yes, it's crunchide. It was broken prior to r277259: >=20 > | crunchide: Correct 64-bit section header offset > | > | For 64-bit binaries the Elf_Ehdr e_shoff is at offset 40, not 44. > | Instead of using an incorrect hardcoded offset, let the compiler > | figure it out for us with offsetof(). > | > | Differential Revision: https://reviews.freebsd.org/D1543 >=20 > It's not completely clear to me why we did not encounter this before; > a comment before the erroneous write states: >=20 > /* > * update the offset of section header table in elf > * header if needed. > */ >=20 > so I presume something about the object file created by gcc 4.9 causes > this code to be executed, while builds using the in-tree compiler did > not. Ah Yes! I remember now! We should find the FreeBSD version at that date and either build it when we=E2=80=99re cross compiling, or rebuild it = when we=E2=80=99re bootstrapping. Thanks for finding this Ed. Warner --Apple-Mail=_EDE77C46-E36F-4072-8E7E-46327059403A Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJVHwGyAAoJEGwc0Sh9sBEAwQ4QALaZUoOfWFW9art2QZ5rDyfz qsI2bgoxrUanYky+17w4D1jLr5EAlagRyHfQcvwd1un1FejzpfsJXmluk7RUzjGv 678BI1jV2GN6jGrfEbAvvABG5B1Wn7qgduYTziIWFfT7DaJuOf1dNhVu3Pc3t7Qn 1Izerokpxqo3B1PQAsl6clrFW8GsBsgClpwgqQ97YhQZivJ/0B5fEA11YQPwqet7 cdKavwpBNMlcFmVwodfnEd+PxX0HZs4dDgPoM+n9uEGonHg9/tYrCYnFevf2x2RT u2FPDNSr7PO2RyFqAw6QwO6JQsHiJ1n6DajwX3v6X1GGCxwUYwDyDkdp+kYA3aG8 hI7ffoC3QWvwsnPKPtdaO3rdxxmkAQaRt72EzjOYbo1WYnqCjLSEEFmmZpjwJuus o3tyfQiBVVM6rFHG+tdJ6QiFqlzrklgnWbQXIbjpK2/CM8IeizBvwNlpZALVy8yi zT9KIt6SvWrZwu7W8KzKu2vdrxyPsUDXeFybhl09ofdAUnCS3UvSBlnzDPjZkKdh JfnC3JIyhx/XJTbTH5ZieBLq9wd+XdFmZhUDYli8ni+Hv7wD3UuHYo4ae+rOqTlu 7R/VVsn2V9Dh2BIqExcA0BvmISPS2QcEWTXcgrK1M69+YNVBtR7B2qkitJUHuDt6 2o6DIfeQ1tiIqQhrnjN/ =lgJJ -----END PGP SIGNATURE----- --Apple-Mail=_EDE77C46-E36F-4072-8E7E-46327059403A-- From owner-freebsd-toolchain@FreeBSD.ORG Fri Apr 3 21:15:54 2015 Return-Path: Delivered-To: freebsd-toolchain@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BCC02F6D; Fri, 3 Apr 2015 21:15:54 +0000 (UTC) Received: from mail-pa0-x229.google.com (mail-pa0-x229.google.com [IPv6:2607:f8b0:400e:c03::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8A02F34C; Fri, 3 Apr 2015 21:15:54 +0000 (UTC) Received: by paboj16 with SMTP id oj16so46081373pab.0; Fri, 03 Apr 2015 14:15:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=eU9JKpqjPlPw8Rhvo8CLy8mfCN5+WpatSehfspsNDKw=; b=jdsBgEYAc04YbI+O4RNkbeRCOwjUoOmWA76uiFx3rDaqvDS68ZARf4RdmWLMqE94W0 eKI9RTzXgjc/Z4bSuHB37wjTzkg43XLS/qnWffCzqUmTiHX3L9JczKlND1B8+3YaHoop 00MYpfmyda99PG/9PxyutXh5HRfYY/nhEfSNc1fRvy1ZQMJra4LC9LIh1WssfgQe+SWU 090npIydJtF1dlF8whVo2FpMAoyQDZ0B1NQuqchc5p3UJKpnZ9HFKnZlyjH19ttJmjTS TI0CRx8l5I6U2Sja0eJKapjyXy6tsINO1LDxmIlu2ehS1hDqIfB8MzXGObOvOSnOd8WA vqEA== X-Received: by 10.67.22.72 with SMTP id hq8mr7426901pad.154.1428095754023; Fri, 03 Apr 2015 14:15:54 -0700 (PDT) Received: from ?IPv6:2601:8:ab80:7d6:c0f7:599f:1bc7:96bd? ([2601:8:ab80:7d6:c0f7:599f:1bc7:96bd]) by mx.google.com with ESMTPSA id nn6sm8723141pdb.79.2015.04.03.14.15.52 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Apr 2015 14:15:53 -0700 (PDT) Content-Type: multipart/signed; boundary="Apple-Mail=_2A31875E-D891-44B3-AC52-7782582485AE"; protocol="application/pgp-signature"; micalg=pgp-sha512 Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Failed to build rescue with gcc 4.9 From: Garrett Cooper In-Reply-To: <04452C2A-FB67-465B-AE33-44ED2109672E@bsdimp.com> Date: Fri, 3 Apr 2015 14:15:50 -0700 Message-Id: <73C7F494-54BD-4E83-B2AD-882D8C3FF11A@gmail.com> References: <2D2191D4-DB6F-4889-9CA9-DFEE495D8302@bsdimp.com> <04452C2A-FB67-465B-AE33-44ED2109672E@bsdimp.com> To: Warner Losh X-Mailer: Apple Mail (2.1878.6) Cc: "freebsd-testing@freebsd.org" , FreeBSD Toolchain X-BeenThere: freebsd-toolchain@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Maintenance of FreeBSD's integrated toolchain List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Apr 2015 21:15:54 -0000 --Apple-Mail=_2A31875E-D891-44B3-AC52-7782582485AE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Apr 3, 2015, at 14:10, Warner Losh wrote: >>=20 >> On Apr 3, 2015, at 2:39 PM, Ed Maste wrote: >>=20 >> On 3 April 2015 at 13:02, Warner Losh wrote: >>> That shows that something in the list is needed. Likely only = crunchhide. >>>=20 >>> It doesn=92t tell us why we need it, or when we started needing it, = or what >>> other conditions we might need it. This information is critical to = document >>> so we know when we can stop doing it in the future. I=92m extremely = reluctant >>> to commit this until we know these details. >>=20 >> Yes, it's crunchide. It was broken prior to r277259: >>=20 >> | crunchide: Correct 64-bit section header offset >> | >> | For 64-bit binaries the Elf_Ehdr e_shoff is at offset 40, not = 44. >> | Instead of using an incorrect hardcoded offset, let the compiler >> | figure it out for us with offsetof(). >> | >> | Differential Revision: https://reviews.freebsd.org/D1543 >>=20 >> It's not completely clear to me why we did not encounter this before; >> a comment before the erroneous write states: >>=20 >> /* >> * update the offset of section header table in elf >> * header if needed. >> */ >>=20 >> so I presume something about the object file created by gcc 4.9 = causes >> this code to be executed, while builds using the in-tree compiler did >> not. >=20 > Ah Yes! I remember now! We should find the FreeBSD version at that = date > and either build it when we=92re cross compiling, or rebuild it when = we=92re > bootstrapping. >=20 > Thanks for finding this Ed. These numbers need to be bumped by 1, but here they are (this also = wasn=92t backported to stable/8 or stable/9 AFAICT). Cheers! head: $ svn cat -r r277259 ^/head/sys/sys/param.h | grep = '#define.*__FreeBSD_version' | awk '{ print $3 }=92 1100054 stable/10: $ svn cat -r 277557 ^/stable/10/sys/sys/param.h | grep = '#define.*__FreeBSD_version' | awk '{ print $3 }' 1001506 --Apple-Mail=_2A31875E-D891-44B3-AC52-7782582485AE Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJVHwMGAAoJEMZr5QU6S73eWZgH/1Jq6wWZ0fS60AmdWgsU9vc7 woAGbiKKWOX7jm/A1Yo8fIg3C00szKBrdOIMN4G9ZGFZg85jfnQwDZHTMPupyRRd lt4XPMNhC2+FW1t+SCe7zTvlFTN1LBnvc20oxEON9MVGHefYMEdMh+gC7DY2fjJs xpCssUGKRKB2JPVs1UzfV+V31QxnKSjAggqd43lr/D82bzrJ7QUKzg3R4252U8IL YW8XE0w/ig5g6twjosrQPon88yPLDnUo6YFHCcDAhjwvCTRAD9Lu0sT9JTAdAYzN dJ9yNQw+CnDwC8faBzLYG6W86jwP9kfSJTnI23iM+xCFSBX/r4ipB0k+Mm5Xwlo= =xRe1 -----END PGP SIGNATURE----- --Apple-Mail=_2A31875E-D891-44B3-AC52-7782582485AE--