public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hkzhang455 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/111672] Inappropriate function splitting during pass_split_functions
Date: Fri, 06 Oct 2023 16:16:32 +0000 [thread overview]
Message-ID: <bug-111672-4-G6GnB0dUFu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111672-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111672
--- Comment #13 from Hanke Zhang <hkzhang455 at gmail dot com> ---
(In reply to Andrew Pinski from comment #12)
> (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
> upstream GCC does not. Ubuntu's compiler also defaults to building PIE
> applications too.
Thanks a lot. The _FORTIFY_SOURCE maybe the problem then.
prev parent reply other threads:[~2023-10-06 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 9:41 [Bug c/111672] New: " hkzhang455 at gmail dot com
2023-10-03 16:37 ` [Bug ipa/111672] " pinskia at gcc dot gnu.org
2023-10-04 2:00 ` hkzhang455 at gmail dot com
2023-10-04 2:04 ` pinskia at gcc dot gnu.org
2023-10-04 2:08 ` hkzhang455 at gmail dot com
2023-10-04 5:24 ` pinskia at gcc dot gnu.org
2023-10-04 5:25 ` pinskia at gcc dot gnu.org
2023-10-04 13:48 ` hkzhang455 at gmail dot com
2023-10-04 13:49 ` hkzhang455 at gmail dot com
2023-10-04 23:58 ` pinskia at gcc dot gnu.org
2023-10-05 0:03 ` pinskia at gcc dot gnu.org
2023-10-06 2:48 ` hkzhang455 at gmail dot com
2023-10-06 2:59 ` pinskia at gcc dot gnu.org
2023-10-06 16:16 ` hkzhang455 at gmail dot com [this message]
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=bug-111672-4-G6GnB0dUFu@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).