From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BB7FD382B3FD; Wed, 7 Dec 2022 04:21:07 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BB7FD382B3FD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1670386867; bh=e61GiMGKDVyZ8u8FtJ4npyXqvW+9Z36dnON4Vwa9ZPs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=w63UWYPGja/mR0QYSuRsczX6O6bMCMvTLVTSfuIEk6QrxggrsZl2+050QL+VG45PP 1VswV3/6UkXQSTymqEqJY91vg/+wUMU3bJH2nnY5Y+T83vkQOAQjvVxz+tbbKE24+s dYUhBDsUVCb/FjVT02ZZS4VyP4yhw3rJMPf7z8sM= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105043] Documentation for __builtin_object_size and other Object Size checking builtin functions should mention - D_FORTIFY_SOURCE Date: Wed, 07 Dec 2022 04:21:06 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: documentation X-Bugzilla-Severity: enhancement X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: NEW 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: resolution short_desc bug_severity bug_status 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=3D105043 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|MOVED |--- Summary|Please document |Documentation for |-D_FORTIFY_SOURCE |__builtin_object_size and | |other Object Size checking | |builtin functions should | |mention - D_FORTIFY_SOURCE Severity|normal |enhancement Status|RESOLVED |NEW --- Comment #7 from Andrew Pinski --- I do think we should mention in the section about __builtin_object_size that this used in connection with the -D_FORTIFY_SOURCE feature of some libc's. That is on this page: https://gcc.gnu.org/onlinedocs/gcc/Object-Size-Checking.html#Object-Size-Ch= ecking Mention that the libc feature -D_FORTIFY_SOURCE uses these builtins. I am not 100% sure on the exact wording but that should give a hint to the = user of GCC to look into glibc/libc documentation for -D_FORTIFY_SOURCE.=