From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id A15DD3858C35; Fri, 6 Oct 2023 02:59:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A15DD3858C35 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1696561143; bh=xMNnSdXL0Jv+mg2OPW01mby7pR30YxtgPwlSDNc7f1s=; h=From:To:Subject:Date:In-Reply-To:References:From; b=JtEWqKMAL2W2rdHGM8WYouxds3/Av2js5C6WtjZ1kA3QuI1Ln1BxyzTaZ90K6VwqE JHoOxq+DB7kHh3lB1SAz1MR7xGHyqlfkGqWCR7oHpDsJeVbwqHtFkcGFuF5We3jWYx 6D5Q0aYUAbk8+H2hi/ZA0yHVPbkwPqq6Z9EZLMuY= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/111672] Inappropriate function splitting during pass_split_functions Date: Fri, 06 Oct 2023 02:59:03 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 12.3.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D111672 --- Comment #12 from Andrew Pinski --- (In reply to Hanke Zhang from comment #11) > But I have never seen this '_FORTIFY_SOURCE' before. So I'm a confused as > well. And when I try gcc@11.4 built in the default ubuntu 22.04, it's the > same. So I don't know how to describe now. Thanks for your help anyway. Well Ubuntu's compiler defaults to defining _FORTIFY_SOURCE while the upstr= eam GCC does not. Ubuntu's compiler also defaults to building PIE applications = too.=