public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sjames at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/113059] New: [14 regression] fftw fails tests for -O3 -m32 -march=znver2 since r14-6210-ge44ed92dbbe9d4 Date: Mon, 18 Dec 2023 09:12:46 +0000 [thread overview] Message-ID: <bug-113059-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113059 Bug ID: 113059 Summary: [14 regression] fftw fails tests for -O3 -m32 -march=znver2 since r14-6210-ge44ed92dbbe9d4 Product: gcc Version: 14.0 Status: UNCONFIRMED Keywords: wrong-code Severity: normal Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: sjames at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- fftw started failing tests (very inconsistently - almost always fails, but sometimes w/ segfault, sometimes with wrong results) since r14-6210-ge44ed92dbbe9d4. Might be a continuation of PR112572. We had pinskia's workaround patch applied until r14-6210-ge44ed92dbbe9d4 landed so I may need to double check. I can reproduce with the following: ``` ./configure CFLAGS="-O3 -m32 -march=znver2 -ggdb3" make -j$(nproc) make -j$(nproc) check ``` Just `tests/bench --verbose=1 --verify //obrd896` seems to be a good crasher for me. ``` Program received signal SIGSEGV, Segmentation fault. r2cf_32 (R0=0xffff97c0, R1=0xffff98d0, Cr=0xffff97c0, Ci=<optimized out>, rs=<optimized out>, csr=0x56690040, csi=0x0, v=<optimized out>, ivs=1, ovs=1) at r2cf_32.c:490 490 Ci[WS(csi, 8)] = T29 - T28; (gdb) bt #0 r2cf_32 (R0=0xffff97c0, R1=0xffff98d0, Cr=0xffff97c0, Ci=<optimized out>, rs=<optimized out>, csr=0x56690040, csi=0x0, v=<optimized out>, ivs=1, ovs=1) at r2cf_32.c:490 #1 0x56632963 in dobatch_r2hc (ego=0x566916b0, I=0x56680e80, O=0x56680e80, buf=0xffff97c0, batchsz=1) at direct-r2c.c:91 #2 0x56632a5d in iterate (ego=0x566916b0, I=<optimized out>, O=<optimized out>, dobatch=0x56632880 <dobatch_r2hc>) at direct-r2c.c:142 #3 0x565a09f5 in fftw_rdft_solve (ego_=0x566916b0, p_=0x566921d0) at solve.c:29 #4 0x565603eb in measure (iter=1, p=<optimized out>, pln=<optimized out>) at timer.c:136 #5 fftw_measure_execution_time (plnr=0x56684690, pln=0x566916b0, p=0x566921d0) at timer.c:159 #6 0x5655d853 in evaluate_plan (ego=ego@entry=0x56684690, pln=pln@entry=0x566916b0, p=p@entry=0x566921d0) at planner.c:460 #7 0x5655e773 in search0 (ego=ego@entry=0x56684690, p=p@entry=0x566921d0, slvndx=slvndx@entry=0xffffbbac, flagsp=<optimized out>) at planner.c:529 #8 0x5655eb37 in search (flagsp=0xffffbbb0, slvndx=0xffffbbac, p=0x566921d0, ego=0x56684690) at planner.c:600 #9 mkplan (ego=<optimized out>, p=<optimized out>) at planner.c:711 [...] ``` Reducing is challenging so far, as FFTW is massive. I'm not going to waste much more time on that, but I'll do the usual bisecting object files and such now.
next reply other threads:[~2023-12-18 9:12 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-18 9:12 sjames at gcc dot gnu.org [this message] 2023-12-18 9:30 ` [Bug target/113059] " rguenth at gcc dot gnu.org 2023-12-22 9:47 ` jakub at gcc dot gnu.org 2023-12-22 13:55 ` sjames at gcc dot gnu.org 2023-12-22 16:51 ` jakub at gcc dot gnu.org 2023-12-22 17:57 ` jakub at gcc dot gnu.org 2023-12-22 18:11 ` jakub at gcc dot gnu.org 2023-12-22 18:11 ` jakub at gcc dot gnu.org 2023-12-22 18:14 ` jakub at gcc dot gnu.org 2023-12-22 18:30 ` fw at gcc dot gnu.org 2023-12-22 18:40 ` jakub at gcc dot gnu.org 2023-12-22 18:41 ` jakub at gcc dot gnu.org 2024-01-09 16:03 ` jakub at gcc dot gnu.org 2024-01-10 9:10 ` rguenth at gcc dot gnu.org 2024-01-10 9:19 ` jakub at gcc dot gnu.org 2024-01-10 9:53 ` rguenther at suse dot de 2024-01-10 18:24 ` pinskia at gcc dot gnu.org 2024-01-30 7:59 ` sjames at gcc dot gnu.org 2024-01-30 9:23 ` jakub at gcc dot gnu.org 2024-01-30 10:25 ` rguenth at gcc dot gnu.org 2024-01-30 10:32 ` jakub at gcc dot gnu.org 2024-01-30 10:45 ` jakub at gcc dot gnu.org 2024-01-30 10:46 ` rguenther at suse dot de 2024-01-30 10:47 ` rguenth at gcc dot gnu.org 2024-01-30 11:17 ` jakub at gcc dot gnu.org 2024-01-30 11:39 ` jakub at gcc dot gnu.org 2024-02-05 8:36 ` cvs-commit at gcc dot gnu.org 2024-02-05 8:38 ` [Bug target/113059] [15 " jakub at gcc dot gnu.org 2024-02-23 15:49 ` sjames at gcc dot gnu.org 2024-02-23 15:49 ` sjames at gcc dot gnu.org 2024-03-06 16:44 ` sjames 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-113059-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: 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).