Authentication-Results: mail-b.sr.ht; dkim=pass header.d=c9x.me header.i=@c9x.me; dkim=pass header.d=messagingengine.com header.i=@messagingengine.com Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by mail-b.sr.ht (Postfix) with ESMTPS id 78B7111EF5E for <~mpu/qbe@lists.sr.ht>; Tue, 4 Oct 2022 21:04:51 +0000 (UTC) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 576CD5C011A for <~mpu/qbe@lists.sr.ht>; Tue, 4 Oct 2022 17:04:51 -0400 (EDT) Received: from imap46 ([10.202.2.96]) by compute4.internal (MEProxy); Tue, 04 Oct 2022 17:04:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=c9x.me; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; t=1664917491; x=1665003891; bh=DDgc2JUBng /APQgTOJvnbRnW+Y4avzpyKUP8Px9qhOE=; b=HeUsBNaBhvqbfV/AIfy10/+o3o rexZ0o/0/LmOvCbw5duvK49rXR+LkOrWSS1+i1m82pueSn2E+bM7yylgQehlCTT0 94Agm6qJp4jGKuKHOpjZm4JalzbcgMpiABEsY8Sf7w9Ia9MiGRA7OWA5mrK3L69U ApLVrA9Qi/QEw3CjdP7uOgFv6vc8XVR59w6vTdQutwAQr08CQ1biOHMXNc1FLi0L Pl/5jeCW8xh9lPEN7btPhSG9zW4DlR4jG3crZR+5Xyv4E5LQglI1BiHe0Z3P6pEI fj/HxNWs++HB6OHBV4zac0KXriCcCDI77iZG2+wcyPDG87yHFclePiV+wTvQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; t=1664917491; x=1665003891; bh=DDgc2JUBng/APQgTOJvnbRnW+Y4a vzpyKUP8Px9qhOE=; b=hZvJJiPDameaLT5vG0U5SEXofcRs4qmpp50v9gKE/REv YsD1KBUuaFt7eGFfVzkIg5oo8frqvyn+VUF9NHpmnZZybRJsdaVe5RphWIJ90tLt hWTZT60+06n1saqwb1/xVeDDRmeDL5Phbg0Ba8IjfUJYNX7J969aRUuWqTz388Kx SobCESCLHkoTV6KN4Gek5cuzt2VYZ0+5KiAW+DSIHuwtWwyGSO7mP3fZ0bXx6xy0 u3Sci+OIG3YV50nsdgohUSkN8rvhiZbrORwzKwg0VVOadga/lgPGJXPVg/LKKj5c l4IiMxzqSmt2x0lwAbGOv8+dMiRlxaDl+C5ivR3Edg== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrfeeiuddgudehiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdfsuhgvnhhtihhnucevrghrsghonhhnvggruhigfdcu oehquhgvnhhtihhnsegtleigrdhmvgeqnecuggftrfgrthhtvghrnhepgeeludettdetud eiueejfffgkeffvdfffeeiveeuvdevieettefgfedtgffgleehnecuvehluhhsthgvrhfu ihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepqhhuvghnthhinhestgelgidrmh gv X-ME-Proxy: Feedback-ID: i52e14683:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 206F92A20080; Tue, 4 Oct 2022 17:04:51 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.7.0-alpha0-1015-gaf7d526680-fm-20220929.001-gaf7d5266 Mime-Version: 1.0 Message-Id: In-Reply-To: References: Date: Tue, 04 Oct 2022 23:04:29 +0200 From: "Quentin Carbonneaux" To: ~mpu/qbe@lists.sr.ht Subject: Re: Any interest in SIMD types? Content-Type: text/plain On Tue, Oct 4, 2022, at 22:11, Harris Snyder wrote: > Would there be any interest in adding SIMD types? Hi Harris, Thanks for your message to the list. The general trend lately in qbe has been to "broaden" the surface, with new archs supported (apple hardware) and new IL capabilities (thread local variables). I would now like us to revert to improving the core compilation algorithms. Adding SIMD types is not really aligned with that and may well complicate things. Additionally, I am under the impression that SIMD types are not uniform enough across platforms to warrant a place in the IL. I may be proved wrong here, though. For the above reasons, I am not presently interested in supoorting SIMD types.