From: Xi Ruoyao <xry111@xry111.site>
To: Reid Wahl <nwahl@redhat.com>, gcc-help@gcc.gnu.org
Subject: Re: -fno-builtin not preventing __builtin___snprintf_chk in gcc 11.2.0-19ubuntu1
Date: Mon, 22 Aug 2022 11:03:10 +0800 [thread overview]
Message-ID: <2351f99b1bc5bb8f120e132354b2580b5163916a.camel@xry111.site> (raw)
In-Reply-To: <CAPiuu9_=ZtFZUD+3+vzKUuvShxWezf1ngjnm0=dUmDNBQwiShg@mail.gmail.com>
On Sun, 2022-08-21 at 19:39 -0700, Reid Wahl via Gcc-help wrote:
For the title: -fno-builtin only prevents gcc to convert foo() to
__builtin_foo(). If you write __builtin_foo() directly built-in will be
used with or without -fno-builtin.
The remaining discussion is not related to GCC anyway. _FORTIFY_SOURCE
is a Glibc (not GCC) feature, and it's just enabled by default because
the distro is *too* smart... I completely agree to add -
D_FORTIFY_SOURCE when they build their .deb packages, but hard wiring
this into GCC is just puzzling new users and causing them to wrongly
believe this was a "feature" of vanilla GCC. To make things worse, many
people use Ubuntu as their first Linux distro...
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2022-08-22 3:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 0:53 Reid Wahl
2022-08-22 2:39 ` Reid Wahl
2022-08-22 3:03 ` Xi Ruoyao [this message]
2022-08-22 4:07 ` Reid Wahl
2022-08-22 8:41 ` Florian Weimer
2022-08-22 8:54 ` Reid Wahl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2351f99b1bc5bb8f120e132354b2580b5163916a.camel@xry111.site \
--to=xry111@xry111.site \
--cc=gcc-help@gcc.gnu.org \
--cc=nwahl@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).