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: Tue, 14 Mar 2023 09:02:20 +0000	[thread overview]
Message-ID: <bug-109109-4-OmqZqwqiCP@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 #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #12)
> So the problem happens here:
> 
> static
> uint32_t
> trx_undo_free_page(
> 
>  trx_rseg_t* rseg,
>  bool in_history,
> 
>  uint32_t hdr_page_no,
>  uint32_t page_no,
> 
>  mtr_t* mtr,
> 
> 
>  dberr_t* err)
> {
>  do { if (__builtin_expect(!(ulint) (hdr_page_no != page_no), (0))) {
> ut_dbg_assertion_failed("hdr_page_no != page_no",
> "/home/abuild/rpmbuild/BUILD/mariadb-10.11.2/storage/innobase/trx/trx0undo.
> cc", 744); } } while (0);
> 
>  buf_block_t* undo_block = buf_page_get_gen(page_id_t(rseg->space->id,
>             page_no),
>          0, RW_X_LATCH, nullptr,
>          10, mtr, err);
>  if (__builtin_expect(!undo_block, (0))) {
>   return 0xFFFFFFFFU;
>  }
>  buf_block_t* header_block = buf_page_get_gen(page_id_t(rseg->space->id,
>               hdr_page_no), <---- HERE
>            0, RW_X_LATCH, nullptr,
>            10, mtr, err);
>  if (__builtin_expect(!header_block, (0))) {
>   return 0xFFFFFFFFU;
>  }
> ...
> 
> the function arguments are:
> #1  0x570e8874 in trx_undo_free_page (rseg=0x57a56c40 <trx_sys+16768>,
> in_history=false, hdr_page_no=807, page_no=817, mtr=0xef4ac434,
> err=0xef4ac3dc) at /tmp/trxundo.ii:181925
> 
> and the construction of:
> page_id_t(rseg->space->id, hdr_page_no)
> ends in callee (buf_page_get_gen) with the argument:
> 
> (gdb) p page_id
> $5 = {m_id = 0}
> 
> while in good run it should be {m_id = 807} !

Ok, can you please print *rseg , rseg->space[0], *mtr and *err at the start of
the function, so that I can try to construct a self-contained testcase?
I assume both buf_page_get_gen return something non-NULL and it doesn't really
matter otherwise what for the reproducer, since e.g. all the further calls can
be noipa handled as completely dummy or even exit (0).

  parent reply	other threads:[~2023-03-14  9:02 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 [this message]
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-OmqZqwqiCP@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: link
Be 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).