From owner-freebsd-bugs@FreeBSD.ORG Tue Jan 14 21:40:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7FCB5B7A for ; Tue, 14 Jan 2014 21:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6C44C1CB8 for ; Tue, 14 Jan 2014 21:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s0ELe1bA002905 for ; Tue, 14 Jan 2014 21:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s0ELe1rT002904; Tue, 14 Jan 2014 21:40:01 GMT (envelope-from gnats) Date: Tue, 14 Jan 2014 21:40:01 GMT Message-Id: <201401142140.s0ELe1rT002904@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Pedro Giffuni Subject: Re: gnu/155309: [PATCH] gcc: backport bswap32() and bswap64() X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Pedro Giffuni List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jan 2014 21:40:01 -0000 The following reply was made to PR gnu/155309; it has been noted by GNATS. From: Pedro Giffuni To: bug-followup@FreeBSD.org, mm@FreeBSD.org Cc: Subject: Re: gnu/155309: [PATCH] gcc: backport bswap32() and bswap64() Date: Tue, 14 Jan 2014 16:37:30 -0500 Hello; In an effort to reduce differences against Apple's GCC, I committed the bswap34/64 builtins as part of r258428. The change was not MFCd to FreeBSD 9.x because I noticed something in the bigger patch causes issues when building OpenOffice. It is probable that just rebuilding all the dependencies fixes the issue but I obviously wanted to avoid some pain to existing users. Further investigation is welcome or we can just close this PR.