public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "thomas.petazzoni@free-electrons.com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/107728] with -O0, libgcc in the first stage compiler has reference to libc functions Date: Wed, 16 Nov 2022 22:51:30 +0000 [thread overview] Message-ID: <bug-107728-4-tIg15FbbuP@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-107728-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107728 --- Comment #3 from Thomas Petazzoni <thomas.petazzoni@free-electrons.com> --- Thanks for the super quick feedback. Could you clarify "Move over, the functions are not optimized out at -O2 but rather they don't get pulled in glibc building because another function is referenced." ? For the record, we are able to work around this issue by passing -O1 in CFLAGS_FOR_TARGET/CXXFLAGS_FOR_TARGET when building the first stage gcc.
next prev parent reply other threads:[~2022-11-16 22:51 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-11-16 21:43 [Bug bootstrap/107728] New: " thomas.petazzoni@free-electrons.com 2022-11-16 21:54 ` [Bug bootstrap/107728] " pinskia at gcc dot gnu.org 2022-11-16 22:09 ` pinskia at gcc dot gnu.org 2022-11-16 22:51 ` thomas.petazzoni@free-electrons.com [this message] 2022-11-24 16:49 ` arnout at mind dot be 2022-11-24 17:29 ` arnout at mind dot be 2022-11-24 17:31 ` [Bug libgcc/107728] _umoddi3.o has reference to the unwinder at -O0 pinskia at gcc dot gnu.org
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-107728-4-tIg15FbbuP@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: linkBe 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).