From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.0 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: from second.openwall.net (second.openwall.net [193.110.157.125]) by inbox.vuxu.org (Postfix) with SMTP id 8D24020CC3 for ; Thu, 24 Oct 2024 15:36:33 +0200 (CEST) Received: (qmail 13821 invoked by uid 550); 24 Oct 2024 13:36:29 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com x-ms-reactions: disallow Received: (qmail 13775 invoked from network); 24 Oct 2024 13:36:29 -0000 Date: Thu, 24 Oct 2024 09:36:20 -0400 From: Rich Felker To: =?utf-8?Q?J=2E_Neusch=C3=A4fer?= Cc: musl@lists.openwall.com Message-ID: <20241024133619.GX10433@brightrain.aerifal.cx> References: <20241002-gcc-bump-v1-0-8f910fd54b1c@gmx.net> <20241022215221.GS10433@brightrain.aerifal.cx> <20241024131141.GW10433@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20241024131141.GW10433@brightrain.aerifal.cx> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [musl] [PATCH MCM 0/3] musl-cross-make: add newer GCC versions On Thu, Oct 24, 2024 at 09:11:42AM -0400, Rich Felker wrote: > On Wed, Oct 23, 2024 at 02:29:13PM +0200, J. Neuschäfer wrote: > > On Tue, Oct 22, 2024 at 05:52:22PM -0400, Rich Felker wrote: > > > On Wed, Oct 02, 2024 at 05:40:03PM +0200, J. Neuschäfer wrote: > > > > This patchset adds newer GCC versions to MCM. Patches are copied from > > > > GCC 11 and only very lightly modifed (which can be verified by diffing > > > > the patch directories). > > > > > > > > I haven't tested the resulting toolchains, so there might be some bugs > > > > lurking. > > > > > > Could you resend these as attachments instead of lkml-thread-style? > > > Something got messed up with the whitespace and git am is applying > > > them but giving results that have gratuitous whitespace diffs, and I'd > > > rather not track down whether any of that is breaking. > > > > > > Rich > > > > Here they are. > > Weird, I'm still getting problems. git-am gives me: > > ..git/rebase-apply/patch:40: space before tab in indent. > "|fstack-protector-strong|fstack-protector-explicit" \ > ..git/rebase-apply/patch:88: space before tab in indent. > extra_headers="s390intrin.h htmintrin.h htmxlintrin.h vecintrin.h" > ..git/rebase-apply/patch:89: space before tab in indent. > ;; > ..git/rebase-apply/patch:93: space before tab in indent. > cpu_type=sh > ..git/rebase-apply/patch:94: space before tab in indent. > extra_options="${extra_options} fused-madd.opt" > warning: squelched 79 whitespace errors > warning: 84 lines add whitespace errors. > > and the applied patches have context lines that should be an empty > line with the one-space diff prefix replaced to empty lines (no > leading diff space). > > Can you verify whether this is expected or if something is getting > munged in the mail? It looks like your mailer munged them sending the attachments as message/rfc822 mime, which is lossy with respect to whitespace, rather than text/plain or something that would be safely preserved. The "trailing whitespace" on the context lines is missing in the actual message I received. Rich