From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BDD893858D3C; Tue, 21 Feb 2023 13:36:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BDD893858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1676986585; bh=ae3b4DUj7PDEMxkyk5hHs8Ou1HktZ+neWmFO5fK+EqM=; h=From:To:Subject:Date:In-Reply-To:References:From; b=Y5IH1balfmtomMk20GfWL6y+Oa0J4lZu8Yb74YyBdtUaCOrLiNZ52x0RNhW07Y93S z3AOZTxgphmc1RYZPor9a/03t9yBaDi+k8JyjwqDJZa7hBAFiAJgJBfTa9fGjgU/vx Wr0hRUy0GRR1VVgAPuICeW1LAU8Yh1BWykiDbt7g= From: "muecker at gwdg dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/108375] [10/11/12 Regression] Some variably modified types not detected as such Date: Tue, 21 Feb 2023 13:36:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: accepts-invalid X-Bugzilla-Severity: normal X-Bugzilla-Who: muecker at gwdg dot de X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.5 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108375 --- Comment #11 from Martin Uecker --- Yes, for C this is fixed on trunk. This change seems to also fix PR102939. There is only one place in c-common/ left where middle-end function is used= , so we could easily separate the C FE understanding of VM-types from the one of= the middle-end. I think for C++ it would also be no problem (it even more restrictive). Ada I have no idea. But I suspect that different languages might also have a different idea abo= ut this, and it would therefor make sense to decouple this. So the question is: What is the middle-end's idea of a variably modified ty= pe? Why does it even have to know? In contrast to types with variable size I th= ink a variably modified type is something which could be a FE only thing. If LTO does not work with lang hooks (what happens? are they just removed?), should we just remove the call to it? (which might require the change in c-/common).=