From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from eggs.gnu.org (eggs.gnu.org [IPv6:2001:470:142:3::10]) by sourceware.org (Postfix) with ESMTPS id 0FD683857009 for ; Fri, 26 May 2023 15:53:44 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 0FD683857009 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=nexgo.de Authentication-Results: sourceware.org; spf=fail smtp.mailfrom=nexgo.de Received: from mr3.vodafonemail.de ([145.253.228.163]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q2Zl8-0007hz-CY for gcc@gnu.org; Fri, 26 May 2023 11:53:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nexgo.de; s=vfde-smtpout-mb-15sep; t=1685116421; bh=f7nBRlA+Is6K1+W5uKHlinvNQWOd5DF4cNPOzqoiixs=; h=Message-ID:From:To:References:In-Reply-To:Subject:Date: Content-Type:X-Mailer:From; b=JxFPQMMU3m7pxqTgK4mtmYXLCP4T4zhUVKs1aiamIam4eZHt46wSNQ/7KPZOcX1I6 OFlFPD5VYY4a7rSNsAjW5ZEOLyKUsk8uoV1+wMIrrQNComsThXV5FqjNAUmiWQlvqm ZGCxS68mbFiaw9w8lvp8tbmcV20l+oflbqnq/a+g= Received: from smtp.vodafone.de (unknown [10.0.0.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by mr3.vodafonemail.de (Postfix) with ESMTPS id 4QSTx11v55z20xW; Fri, 26 May 2023 15:53:41 +0000 (UTC) Received: from H270 (p5b38f631.dip0.t-ipconnect.de [91.56.246.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtp.vodafone.de (Postfix) with ESMTPSA id 4QSTwl6SMxzKn80; Fri, 26 May 2023 15:53:24 +0000 (UTC) Message-ID: <24C17D6B62D041D39D3962704D1B4B67@H270> From: "Stefan Kanthak" To: "Jonathan Wakely" Cc: "Jakub Jelinek" , , "Andrew Pinski" References: <51071A92918346ABBC6B5703179F5174@H270> <896EB515110646CEBAA84E98E273E4B8@H270> <4BD5D8BA8E0F45098CC3E2B188A216E6@H270> In-Reply-To: Subject: Re: Will GCC eventually support SSE2 or SSE4.1? Date: Fri, 26 May 2023 17:49:23 +0200 Organization: Me, myself & IT MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Windows Mail 6.0.6002.18197 X-MimeOLE: Produced By Microsoft MimeOLE V6.1.7601.24158 X-purgate-type: clean X-purgate: clean X-purgate-size: 1596 X-purgate-ID: 155817::1685116417-117F94F8-213FFEF2/0/0 Received-SPF: pass client-ip=145.253.228.163; envelope-from=stefan.kanthak@nexgo.de; helo=mr3.vodafonemail.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9,DKIM_SIGNED=0.1,DKIM_VALID=-0.1,DKIM_VALID_AU=-0.1,DKIM_VALID_EF=-0.1,RCVD_IN_DNSWL_LOW=-0.7,SPF_HELO_NONE=0.001,SPF_PASS=-0.001,T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_FAIL,SPF_HELO_PASS,TXREP,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: "Jonathan Wakely" wrote: > On Fri, 26 May 2023 at 15:34, Stefan Kanthak wrote: >> >> "Jonathan Wakely" wrote: >> >> > On Fri, 26 May 2023 at 14:55, Stefan Kanthak wrote: >> >> [...] >> >> >> NOT obvious is but that -m -march= does not clear any >> >> not supported in , i.e the last one does NOT win here. >> > >> > The last -march option selects the base set of instructions. The -mISA >> > options modify that base. >> >> You but missed the point, AGAIN: the modifications per -mISA and -mno-ISA >> persist, i.e. they are NOT reset by the last -march= option. > > Nobody said they are reset, and the docs don't say that, so assume they are not. For the supported -march= the documentation EXPLICITLY enumerates (all?) options! Why should I assume that these options are "sticky" and override the DOCUMENTED set? Unless you document the behaviour in either way it is UB, so every user of GCC can assume anything he wants! > The last -march option selects a base and the -mISA options modify the > base. Note *the* base. The one that was selected. By the last -march > option. The base. > >> Is this SOOOO hard to grok? > > I understand your question. It's based on failing to read or > understand what has been said. Yes, silly! [...] >> Is this soooo hard to document? > > I prefer arguing with trolls, it's even easier. I don't like to argue with idiots: they beat me with experience! Stefan