public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/113359] [13/14 Regression] LTO miscompilation of ceph on aarch64 and x86_64 Date: Thu, 04 Apr 2024 11:40:53 +0000 [thread overview] Message-ID: <bug-113359-4-3sobRTVlK6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113359-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113359 --- Comment #23 from Jan Hubicka <hubicka at gcc dot gnu.org> --- The patch looks reasonable. We probably could hash the padding vectors at summary generation time to reduce WPA overhead, but that can be done incrementally next stage1. I however wonder if we really guarantee to copy the paddings everywhere else then the total scalarization part? (i.e. in all paths through the RTL expansion)
next prev parent reply other threads:[~2024-04-04 11:40 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-12 18:31 [Bug tree-optimization/113359] New: [13 Regression] LTO miscompilation of ceph on aarch64 jakub at gcc dot gnu.org 2024-01-12 18:31 ` [Bug tree-optimization/113359] " jakub at gcc dot gnu.org 2024-01-12 18:32 ` jakub at gcc dot gnu.org 2024-01-12 18:32 ` jakub at gcc dot gnu.org 2024-01-12 18:33 ` jakub at gcc dot gnu.org 2024-01-12 18:34 ` [Bug ipa/113359] " jakub at gcc dot gnu.org 2024-01-12 19:54 ` jakub at gcc dot gnu.org 2024-01-12 19:56 ` jakub at gcc dot gnu.org 2024-01-12 20:29 ` pinskia at gcc dot gnu.org 2024-01-15 8:24 ` rguenth at gcc dot gnu.org 2024-02-05 21:48 ` jamborm at gcc dot gnu.org 2024-02-06 8:29 ` rguenth at gcc dot gnu.org 2024-02-06 10:00 ` hubicka at gcc dot gnu.org 2024-02-06 12:39 ` jakub at gcc dot gnu.org 2024-02-06 12:47 ` rguenther at suse dot de 2024-02-07 17:01 ` jamborm at gcc dot gnu.org 2024-02-19 15:31 ` jamborm at gcc dot gnu.org 2024-03-09 21:44 ` pinskia at gcc dot gnu.org 2024-03-09 21:45 ` sjames at gcc dot gnu.org 2024-03-09 21:45 ` [Bug ipa/113359] [13/14 " pinskia at gcc dot gnu.org 2024-03-15 15:02 ` law at gcc dot gnu.org 2024-03-15 15:13 ` avieira at gcc dot gnu.org 2024-03-15 15:25 ` law at gcc dot gnu.org 2024-03-26 10:42 ` [Bug ipa/113359] [13/14 Regression] LTO miscompilation of ceph on aarch64 and x86_64 rguenth at gcc dot gnu.org 2024-03-28 8:59 ` jamborm at gcc dot gnu.org 2024-04-04 11:40 ` hubicka at gcc dot gnu.org [this message] 2024-04-04 21:22 ` jamborm at gcc dot gnu.org 2024-04-08 16:57 ` cvs-commit at gcc dot gnu.org 2024-04-08 16:59 ` jamborm at gcc dot gnu.org 2024-04-08 17:01 ` [Bug ipa/113359] [13 " jakub at gcc dot gnu.org 2024-04-09 6:33 ` rguenth at gcc dot gnu.org 2024-05-14 11:22 ` cvs-commit at gcc dot gnu.org 2024-05-14 11:58 ` jamborm at gcc dot gnu.org 2024-05-14 12:00 ` jamborm at gcc dot gnu.org 2024-05-17 14:29 ` dkm at gcc dot gnu.org 2024-05-20 15:10 ` jamborm at gcc dot gnu.org 2024-05-20 15:13 ` dkm 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-113359-4-3sobRTVlK6@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).