From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx2.suse.de (mx2.suse.de [195.135.220.15]) by sourceware.org (Postfix) with ESMTPS id 317B3385BF81 for ; Sat, 6 Jun 2020 06:04:32 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 317B3385BF81 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=suse.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=rguenther@suse.de X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 94EC4B0C6; Sat, 6 Jun 2020 06:04:34 +0000 (UTC) Date: Sat, 06 Jun 2020 08:04:28 +0200 User-Agent: K-9 Mail for Android In-Reply-To: <79572583.bFItsc2c9M@polaris> References: <2785895.FhdWIMSt8s@polaris> <79572583.bFItsc2c9M@polaris> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PATCH] middle-end/95493 - bogus MEM_ATTRS for variable array access To: Eric Botcazou CC: gcc-patches@gcc.gnu.org From: Richard Biener Message-ID: <84E3E49A-CDBC-4883-91F3-3E6B973BBFD4@suse.de> X-Spam-Status: No, score=-10.2 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) 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: Sat, 06 Jun 2020 06:04:33 -0000 On June 5, 2020 6:38:10 PM GMT+02:00, Eric Botcazou wrote: >> I've installed it on trunk but will give it quite a while there >before >> backporting=2E I'm still somewhat worried about the >>=20 >> /* ??? If we end up with a constant or a descriptor do not >> record a MEM_EXPR=2E */ >> else if (CONSTANT_CLASS_P (t) >>=20 >> || TREE_CODE (t) =3D=3D CONSTRUCTOR) >>=20 >> ; >>=20 >> case, maybe we should assert that bitpos =3D=3D 0 here since we're >> dropping it on the floor but eventually inherit offset_known_p =3D=3D >true >> from the already present MEM_ATTRs=2E > >It's hard to imagine without a testcase how you can end up inheriting >anything=20 >for CONSTANT_CLASS_P or CONSTRUCTOR though: where do the MEM_ATTRs come >from?=20 For constructor it was constant descriptors seen during ada bootstrap=2E I= can imagine constants are similar for constant pool entries=2E=20 Richard=2E=20