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] [14 regression] fftw fails tests for -O3 -m32 -march=znver2 since r14-6210-ge44ed92dbbe9d4 Date: Fri, 22 Dec 2023 13:55:56 +0000 [thread overview] Message-ID: <bug-113059-4-jXp0f64MCM@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113059-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113059 --- Comment #2 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Jakub Jelinek from comment #1) > Any progress with the bisection? sorry, not yet. I've been away from the computer mostly for an emergency. I did make a start, but I got frustrated with how the Makefile deps seem broken (replacing a .o and running 'make' doesn't trigger a rebuild correctly in all cases). > Or at least details what exactly are you compiling (with what patches etc.)? I can reproduce it consistently with: ``` wget https://www.fftw.org/fftw-3.3.10.tar.gz tar xvf fftw-3.3.10.tar.xz && cd fftw-3.3.10 ./configure CFLAGS="-O3 -m32 -march=znver2 -ggdb3" make -j$(nproc) make -j$(nproc) check ``` Let me know if you need more.
next prev parent reply other threads:[~2023-12-22 13:55 UTC|newest] Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-12-18 9:12 [Bug target/113059] New: " sjames at gcc dot gnu.org 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 [this message] 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-jXp0f64MCM@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).