public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/110334] [13/14 Regresssion] unused functions not eliminated before LTO streaming Date: Thu, 22 Jun 2023 11:15:15 +0000 [thread overview] Message-ID: <bug-110334-4-V7Ud5jTwFc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110334-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110334 --- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> --- So it's actually that we require the instantiations but we are not able to fully optimize avx::[rect_]memset* before LTO streaming. In fact we're not too far from that: void skvx::Vec<2, unsigned int>::Vec (struct Vec * const this, unsigned int D.78460) { unsigned int _3(D); <bb 2> [local count: 1073741824]: MEM[(struct VecStorage *)this_2(D)] ={v} {CLOBBER}; MEM[(struct Vec *)this_2(D)] ={v} {CLOBBER}; MEM[(struct Vec *)this_2(D)].val = _3(D); MEM[(struct Vec *)this_2(D) + 4B] ={v} {CLOBBER}; MEM[(struct Vec *)this_2(D) + 4B].val = _3(D); return; } void skvx::Vec<4, unsigned int>::Vec (struct Vec * const this, unsigned int D.78672) { unsigned int _3(D); struct Vec * _4; struct Vec * _5; <bb 2> [local count: 1073741824]: MEM[(struct VecStorage *)this_2(D)] ={v} {CLOBBER}; _4 = &MEM[(struct VecStorage *)this_2(D)].lo; skvx::Vec<2, unsigned int>::Vec (_4, _3(D)); _5 = &MEM[(struct VecStorage *)this_2(D)].hi; skvx::Vec<2, unsigned int>::Vec (_5, _3(D)); return; } void avx::memsetT<unsigned int> (unsigned int * buffer, unsigned int value, int count) { struct Vec wideValue; long unsigned int _17; <bb 2> [local count: 118111600]: MEM[(struct VecStorage *)&wideValue] ={v} {CLOBBER}; skvx::Vec<4, unsigned int>::Vec (&MEM[(struct VecStorage *)&wideValue].lo, value_8(D)); skvx::Vec<4, unsigned int>::Vec (&MEM[(struct VecStorage *)&wideValue].hi, value_8(D)); we go inlining skvx::Vec<8, unsigned int>::Vec here which eventually expands __attribute__((always_inline)) void skvx::VecStorage<8, unsigned int>::VecStorage (struct VecStorage * const this, unsigned int s) { but we do not inline into that function and as we do not iterate early inlining we stop here. Removing all always_inline from the TU fixes the issue.
next prev parent reply other threads:[~2023-06-22 11:15 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-21 7:05 [Bug ipa/110334] New: " rguenth at gcc dot gnu.org 2023-06-21 7:06 ` [Bug ipa/110334] " rguenth at gcc dot gnu.org 2023-06-21 7:08 ` rguenth at gcc dot gnu.org 2023-06-21 7:12 ` rguenth at gcc dot gnu.org 2023-06-22 11:15 ` rguenth at gcc dot gnu.org [this message] 2023-06-22 11:45 ` rguenth at gcc dot gnu.org 2023-06-22 12:02 ` rguenth at gcc dot gnu.org 2023-06-23 10:47 ` hubicka at gcc dot gnu.org 2023-06-23 11:21 ` rguenth at gcc dot gnu.org 2023-06-23 12:59 ` hubicka at ucw dot cz 2023-06-23 13:07 ` Jan Hubicka 2023-06-23 13:07 ` hubicka at ucw dot cz 2023-06-26 6:39 ` rguenther at suse dot de 2023-06-26 17:50 ` hubicka at ucw dot cz 2023-06-27 6:41 ` rguenther at suse dot de 2023-06-28 10:00 ` Jan Hubicka 2023-06-28 4:42 ` cvs-commit at gcc dot gnu.org 2023-06-28 10:00 ` hubicka at ucw dot cz 2023-06-28 10:20 ` rguenther at suse dot de 2023-06-28 10:45 ` hubicka at ucw dot cz 2023-06-28 21:06 ` cvs-commit at gcc dot gnu.org 2023-07-03 7:05 ` jakub at gcc dot gnu.org 2023-07-10 7:40 ` rguenth at gcc dot gnu.org 2023-07-10 8:24 ` rguenth at gcc dot gnu.org 2023-07-10 8:24 ` rguenth at gcc dot gnu.org 2023-07-11 14:45 ` hubicka at ucw dot cz 2023-07-11 14:46 ` hubicka at ucw dot cz 2023-07-12 7:05 ` rguenther at suse dot de 2023-07-27 9:26 ` rguenth at gcc dot gnu.org 2023-11-25 10:00 ` egallager at gcc dot gnu.org 2023-11-27 7:28 ` rguenth at gcc dot gnu.org 2024-05-21 9:16 ` jakub 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-110334-4-V7Ud5jTwFc@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).