public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/111677] [12/13/14 Regression] darktable build on aarch64 fails with unrecognizable insn due to -fstack-protector changes Date: Thu, 25 Jan 2024 15:54:12 +0000 [thread overview] Message-ID: <bug-111677-4-qMXi8YbmGi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111677-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111677 --- Comment #20 from Alex Coplan <acoplan at gcc dot gnu.org> --- I think the testcase in #c10 went latent on the 13 branch but the following (reduced from the attachment) still ICEs on the tip of the 13 branch with -Ofast -fopenmp -fstack-protector-strong: typedef struct { long size_z; int width; } dt_bilateral_t; typedef float dt_aligned_pixel_t[4]; #pragma omp declare simd void dt_bilateral_splat(dt_bilateral_t *b) { float *buf; long offsets[8]; for (; b;) { int firstrow; for (int j = firstrow; j; j++) for (int i; i < b->width; i++) { dt_aligned_pixel_t contrib; for (int k = 0; k < 4; k++) buf[offsets[k]] += contrib[k]; } float *dest; for (int j = (long)b; j; j++) { float *src = (float *)b->size_z; for (int i = 0; i < (long)b; i++) dest[i] += src[i]; } } }
next prev parent reply other threads:[~2024-01-25 15:54 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-03 14:41 [Bug c/111677] New: arm64 build fails unrecognizable insn [REGRESSION] costamagnagianfranco at yahoo dot it 2023-10-03 22:22 ` [Bug target/111677] " pinskia at gcc dot gnu.org 2023-10-06 7:53 ` costamagnagianfranco at yahoo dot it 2023-10-09 10:37 ` costamagnagianfranco at yahoo dot it 2023-10-24 4:30 ` pinskia at gcc dot gnu.org 2023-10-24 4:33 ` [Bug target/111677] [12/13/14 Regression] darktable build on aarch64 fails with unrecognizable insn due to -fstack-protector changes pinskia at gcc dot gnu.org 2023-10-24 4:33 ` pinskia at gcc dot gnu.org 2023-10-24 11:19 ` costamagnagianfranco at yahoo dot it 2023-10-24 11:54 ` costamagnagianfranco at yahoo dot it 2023-10-24 12:48 ` costamagnagianfranco at yahoo dot it 2023-10-24 12:50 ` costamagnagianfranco at yahoo dot it 2023-10-24 12:55 ` costamagnagianfranco at yahoo dot it 2023-10-24 14:42 ` acoplan at gcc dot gnu.org 2023-10-24 21:58 ` pinskia at gcc dot gnu.org 2023-10-25 11:19 ` acoplan at gcc dot gnu.org 2023-11-22 11:42 ` costamagnagianfranco at yahoo dot it 2024-01-12 15:58 ` germano.massullo at gmail dot com 2024-01-12 16:34 ` jakub at gcc dot gnu.org 2024-01-13 6:52 ` pinskia at gcc dot gnu.org 2024-01-13 6:53 ` pinskia at gcc dot gnu.org 2024-01-19 14:01 ` costamagnagianfranco at yahoo dot it 2024-01-19 14:01 ` costamagnagianfranco at yahoo dot it 2024-01-25 15:54 ` acoplan at gcc dot gnu.org [this message] 2024-01-25 20:01 ` [Bug target/111677] [12/13 " pinskia at gcc dot gnu.org 2024-01-29 17:00 ` rsandifo at gcc dot gnu.org 2024-01-30 9:30 ` acoplan at gcc dot gnu.org 2024-01-30 12:05 ` [Bug target/111677] [12/13/14 " acoplan at gcc dot gnu.org 2024-01-30 15:34 ` acoplan at gcc dot gnu.org 2024-01-30 17:49 ` acoplan at gcc dot gnu.org 2024-01-31 14:01 ` cvs-commit at gcc dot gnu.org 2024-01-31 14:03 ` [Bug target/111677] [12/13 " acoplan at gcc dot gnu.org 2024-02-07 10:41 ` cvs-commit at gcc dot gnu.org 2024-02-07 10:44 ` [Bug target/111677] [12 " acoplan at gcc dot gnu.org 2024-02-12 17:14 ` acoplan at gcc dot gnu.org 2024-02-14 11:55 ` cvs-commit at gcc dot gnu.org 2024-02-14 11:57 ` [Bug target/111677] " acoplan at gcc dot gnu.org 2024-02-20 10:14 ` cvs-commit at gcc dot gnu.org 2024-02-20 10:15 ` acoplan 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-111677-4-qMXi8YbmGi@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).