From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D841B3858C41; Wed, 10 Jan 2024 19:02:48 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D841B3858C41 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1704913368; bh=XR1WjpnQlM3pvt1DVxD7odCR/Xv4zomfcJ8a4BJwgRQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=eppO0Bj7fD/VBaV44ehgFFsudiDfzklxTJYLzyNVYSi7RyOAlJbUPAjXC6aIWxEkV M70FOM6gcTAq8QBCXNRRsxVfInvqx9FvPOic8TiizFmT/xMndLkxqDEqVyHBZm36jy tG5zQGJiY0bb86Q6+LmJw/fqaEUAKgfCVk2nGEIg= From: "hubicka at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109753] [13/14 Regression] pragma GCC target causes std::vector not to compile (always_inline on constructor) Date: Wed, 10 Jan 2024 19:02:48 +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.1.1 X-Bugzilla-Keywords: rejects-valid X-Bugzilla-Severity: normal X-Bugzilla-Who: hubicka at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 13.3 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=3D109753 --- Comment #12 from Jan Hubicka --- I think this is a problem with two meanings of always_inline. One is "it mu= st be inlined or otherwise we will not be able to generate code" other is "disregard inline limits". I guess practical solution here would be to ingore always inline for functi= ons called from static construction wrappers (since they only optimize around a= rray of function pointers). Question is how to communicate this down from FE to ipa-inline...=