public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin 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: Tue, 14 Mar 2023 10:11:21 +0000 [thread overview] Message-ID: <bug-109109-4-LUVNk3nsnp@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 #14 from Martin Liška <marxin at gcc dot gnu.org> --- Btw. the problematic instruction that assembly the page_id_t: # /tmp/trxundo.ii:181919: if (__builtin_expect(!undo_block, (0))) { addl $48, %esp #, # /tmp/trxundo.ii:181915: buf_block_t* undo_block = buf_page_get_gen(page_id_t(rseg->space->id, movl %eax, -56(%ebp) # _39, %sfp # /tmp/trxundo.ii:181919: if (__builtin_expect(!undo_block, (0))) { testl %eax, %eax # _39 je .L636 #, # /tmp/trxundo.ii:181923: saved = page_id_t(rseg->space->id, hdr_page_no); movl (%esi), %eax # rseg_35(D)->space, rseg_35(D)->space # /tmp/trxundo.ii:181923: saved = page_id_t(rseg->space->id, hdr_page_no); movl -44(%ebp), %ebx # %sfp, tmp82 # /tmp/trxundo.ii:58816: m_id(uint64_t{space} << 32 | page_no) {} movl 44(%eax), %edx # _9->id, _69 # /tmp/trxundo.ii:181923: saved = page_id_t(rseg->space->id, hdr_page_no); movl saved@GOT(%ebx), %ecx #, tmp164 movl %edx, (%ecx) # _69, saved.m_id movl %edx, 4(%ecx) # _69, saved.m_id # /tmp/trxundo.ii:181924: if (saved.raw() == 0) movl %edx, %ecx # _69, tmp213 orl %edx, %ecx # tmp214, tmp215 je .L662 #, for my adjusted code: saved = page_id_t(rseg->space->id, hdr_page_no); if (saved.raw() == 0) __builtin_abort ();
next prev parent reply other threads:[~2023-03-14 10:11 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 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 [this message] 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-LUVNk3nsnp@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).