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 tree-optimization/109109] New: mariadb fails in tests on i586 (non-LTO mode) after r13-4435-g2c089640279614e3
Date: Mon, 13 Mar 2023 13:53:41 +0000 [thread overview]
Message-ID: <bug-109109-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109109
Bug ID: 109109
Summary: mariadb fails in tests on i586 (non-LTO mode) after
r13-4435-g2c089640279614e3
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, rguenth at gcc dot gnu.org
Target Milestone: ---
Created attachment 54648
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54648&action=edit
Unreduced test-case
After the revision I see the following failure in mariadb package:
./mysql-test-run.pl --parallel=32 --force --retry=0 --ssl --suite-timeout=900
--testcase-timeout=30 --mysqld=--binlog-format=mixed --force-restart
--shutdown-timeout=60 --max-test-fail=0 --skip-test=spider
--skip-test-list=unstable-tests innodb_zip.bug36169
...
2023-03-13 13:49:08 4 [ERROR] InnoDB: Cannot add field `col48` in table
`test`.`table0` because after adding it, the row size is 708 which is greater
than maximum allowed size (708 bytes) for a record on index leaf page.
2023-03-13 13:49:08 4 [ERROR] InnoDB: Trying to read 4096 bytes at 4294963200
outside the bounds of the file: ./ibdata1
2023-03-13 13:49:08 4 [ERROR] InnoDB: File './ibdata1' is corrupted
2023-03-13 13:49:08 4 [ERROR] InnoDB: Cannot add field `DB_ROW_ID` in table
`test`.`table1` because after adding it, the row size is 537 which is greater
than maximum allowed size (892 bytes) for a record on index leaf page.
2023-03-13 13:49:08 4 [ERROR] InnoDB: Trying to read 4096 bytes at 1879228416
outside the bounds of the file: ./ibdata1
2023-03-13 13:49:08 4 [ERROR] mariadbd: Index for table 'table2' is corrupt;
try to repair it
I reduced that to a single test-case and a function (see pragma GCC optimize
"-O0"):
g++ /tmp/trxundo.ii -o
/var/tmp/build-root/standard-i586/home/abuild/rpmbuild/BUILD/mariadb-10.11.2/build/storage/innobase/CMakeFiles/innobase.dir/trx/trx0undo.cc.o
-m32 -std=gnu++11 -fomit-frame-pointer -O2 -Wall -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type
-flto=auto -ffat-lto-objects -fno-lto -U_FORTIFY_SOURCE -g -DOPENSSL_LOAD_CONF
-DPIC -fPIC -DFORCE_INIT_OF_VARS -Wno-unused-but-set-variable
-fno-strict-aliasing -Wno-unused-parameter -Wno-error -felide-constructors -pie
-fPIC -fstack-protector --param=ssp-buffer-size=4 -fPIC -Wconversion
-Wno-sign-conversion -fomit-frame-pointer -O2 -Wall -U_FORTIFY_SOURCE
-D_FORTIFY_SOURCE=3 -fstack-protector-strong -funwind-tables
-fasynchronous-unwind-tables -fstack-clash-protection -Werror=return-type
-flto=auto -ffat-lto-objects -fno-lto -U_FORTIFY_SOURCE -g -DOPENSSL_LOAD_CONF
-DPIC -fPIC -DFORCE_INIT_OF_VARS -Wno-unused-but-set-variable
-fno-strict-aliasing -Wno-unused-parameter -Wno-error -felide-constructors
-fno-omit-frame-pointer -DDBUG_OFF -Wall -Wenum-compare -Wenum-conversion
-Wextra -Wformat-security -Wmissing-braces -Wno-format-truncation
-Wno-init-self -Wno-nonnull-compare -Wno-unused-parameter -Woverloaded-virtual
-Wnon-virtual-dtor -Wvla -Wwrite-strings -DHAVE_OPENSSL
-DOPENSSL_API_COMPAT=0x10100000L -fvisibility=hidden -std=gnu++11 -c
next reply other threads:[~2023-03-13 13:53 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 13:53 marxin at gcc dot gnu.org [this message]
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
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@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).