From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) by sourceware.org (Postfix) with ESMTPS id A3B2F3858C27 for ; Tue, 26 Oct 2021 11:48:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A3B2F3858C27 Received: by mail-wm1-x32f.google.com with SMTP id 82-20020a1c0055000000b0032ccc3ad5c1so859912wma.2 for ; Tue, 26 Oct 2021 04:48:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:in-reply-to:references :message-id:mime-version:content-transfer-encoding; bh=EaXE3DEInaufVvD79sGVK4XzTVa8rTJWa5q0fHlgHmk=; b=4VTiSurfUe1QFgmcYdoPhrdcE2wMJpb0BfA6ruwiE3ykmjce+Y0aO4ecQQ6YXGOlzH RAXHiJVdX4Iue6rQ7ftQto4qWKAIX6+OvjDtnons/uoerh8ESalxsOFJo3TraNRf/IKa DK6QBXj0p2hHG54/pX1WE+EE4HQX3lMyKHnwpe2N1iE6BkxUcPLUCqEinfHmOa78BiAZ 76XthDrLM92A/NlDXwNrNCH01Sl77DuVvCyX9PUQfvwhO8kRglnAcJhf1Ydns+USChcv n5Yn74xCDw3KgCmQeeEiz19J+TfZR5TnwE8oahiPeVboypQJNbeLG+Xf1dnpMmOsUsEW +zow== X-Gm-Message-State: AOAM532OI2s06fm3sTkvErZTVJ0sI2iO0CQcngMmK9ah6hfJCyWhL44m tMcDqVv56JOf+Txh+CK2Ng4= X-Google-Smtp-Source: ABdhPJwj70eMxV2mhcPFQK1WeMbLXHyka9qeJfEIPB3rkuRZzSK+meEcaiwaFVlon6U5TB/hDthRSg== X-Received: by 2002:a05:600c:4894:: with SMTP id j20mr23422831wmp.60.1635248922667; Tue, 26 Oct 2021 04:48:42 -0700 (PDT) Received: from [127.0.0.1] (62-46-115-185.adsl.highway.telekom.at. [62.46.115.185]) by smtp.gmail.com with ESMTPSA id m12sm5984687wrq.69.2021.10.26.04.48.41 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Oct 2021 04:48:42 -0700 (PDT) Date: Tue, 26 Oct 2021 13:48:39 +0200 From: Bernhard Reutner-Fischer To: Richard Biener , Richard Biener via Gcc-patches , gcc-patches@gcc.gnu.org Subject: Re: [PATCH] Move negative stride bias out of dr_misalignment In-Reply-To: <24qs317-4090-n6n6-1o2n-40r52no5313n@fhfr.qr> References: <24qs317-4090-n6n6-1o2n-40r52no5313n@fhfr.qr> Message-ID: <5916DAE9-2B77-4AA7-9676-BA2A8538A219@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Oct 2021 11:48:45 -0000 On 26 October 2021 11:19:44 CEST, Richard Biener via Gcc-patches wrote: =20 >@@ -2010,6 +2010,7 @@ get_negative_load_store_type (vec_info *vinfo, > if (dump_enabled_p ()) > dump_printf_loc (MSG_MISSED_OPTIMIZATION, vect_location, > "negative step but alignment required=2E\n"); >+ *poffset =3D 0; > return VMAT_ELEMENTWISE; > *poffset =3D 0; > } I think you cannot really diagnose these, they would trigger a lot, in eac= h early return, no? Or would we see that there are unreachable, non artificial stmts in the sa= me block after a return? Somebody could experiment with diagnosing each and every DCEd stmt (!artif= icial, nondebug) but I would expect that hell breaks loose=2E=2E cheers,