public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109109] [13 Regression] mariadb fails in tests on i586 (non-LTO mode) after r13-4435-g2c089640279614e3 Date: Mon, 13 Mar 2023 16:43:52 +0000 [thread overview] Message-ID: <bug-109109-4-uDsR2XHPxC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109109-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109109 --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Without an actual self-contained reproducer hard to guess. The above mentioned change changes the content of _ZN9page_id_tC2Ejj _Z22trx_undo_get_first_recRK11fil_space_tjtjRPK11buf_block_tP5mtr_tP7dberr_t _ZN5trx_t9apply_logEv _Z17trx_undo_add_pageP10trx_undo_tP5mtr_tP7dberr_t _ZL18trx_undo_free_pageP10trx_rseg_tbjjP5mtr_tP7dberr_t functions from what I can see, so which one of these it is? Another possible way to narrow it down a little bit would be to undo the i386.md hunks from that commit one by one and see which one it is, all the 4 changes are optimizations and all of them are independent of each other (any of them dependent on the i386-expand.cc change which shouldn't change anything on its own). If you narrow it down to one function, then I guess we need to turn it into a self-contained reproducer, add dummy wrapper which calls that function from main with the right arguments and supply dummy callees for the function for functions which aren't inlined.
next prev parent reply other threads:[~2023-03-13 16:43 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-13 13:53 [Bug tree-optimization/109109] New: " marxin at gcc dot gnu.org 2023-03-13 13:55 ` [Bug target/109109] [13 Regression] " rguenth at gcc dot gnu.org 2023-03-13 13:57 ` marxin at gcc dot gnu.org 2023-03-13 16:43 ` jakub at gcc dot gnu.org [this message] 2023-03-13 16:52 ` jakub at gcc dot gnu.org 2023-03-13 21:48 ` marxin at gcc dot gnu.org 2023-03-13 21:50 ` jakub at gcc dot gnu.org 2023-03-13 21:57 ` marxin at gcc dot gnu.org 2023-03-13 21:58 ` marxin at gcc dot gnu.org 2023-03-13 22:01 ` marxin at gcc dot gnu.org 2023-03-13 22:48 ` jakub at gcc dot gnu.org 2023-03-14 7:29 ` marxin at gcc dot gnu.org 2023-03-14 7:30 ` marxin at gcc dot gnu.org 2023-03-14 8:42 ` marxin at gcc dot gnu.org 2023-03-14 9:02 ` jakub at gcc dot gnu.org 2023-03-14 10:11 ` marxin at gcc dot gnu.org 2023-03-14 11:21 ` jakub at gcc dot gnu.org 2023-03-14 11:22 ` marxin at gcc dot gnu.org 2023-03-14 13:46 ` jakub at gcc dot gnu.org 2023-03-14 15:15 ` jakub at gcc dot gnu.org 2023-03-14 18:23 ` jakub at gcc dot gnu.org 2023-03-14 18:26 ` cvs-commit at gcc dot gnu.org 2023-03-14 18:27 ` marxin 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-109109-4-uDsR2XHPxC@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).