public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "costamagnagianfranco at yahoo dot it" <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: Tue, 24 Oct 2023 12:55:26 +0000	[thread overview]
Message-ID: <bug-111677-4-e25FlJw5KA@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 #10 from Gianfranco <costamagnagianfranco at yahoo dot it> ---
$ gcc -O3  -fstack-protector-strong  -fopenmp -ffast-math 
-fexpensive-optimizations testcase.i -c

This is the minimal cmdline to trigger the issue I could find.


cat testcase.i
typedef struct {
  int width
} dt_bilateral_t;
typedef dt_aligned_pixel_t[4];
#pragma omp declare simd
void dt_bilateral_splat(dt_bilateral_t *b) {
  int oy = b;
  float *buf;
  long offsets[8];
  for (int slice; slice < b; slice++) {
    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, *src = oy;
    for (int i = 0; i < oy; i++)
      dest[i] += src[i];
  }
}

testcase.i:3:1: warning: no semicolon at end of struct or union
    3 | } dt_bilateral_t;
      | ^
testcase.i:4:9: warning: type defaults to 'int' in declaration of
'dt_aligned_pixel_t' [-Wimplicit-int]
    4 | typedef dt_aligned_pixel_t[4];
      |         ^~~~~~~~~~~~~~~~~~
testcase.i: In function 'dt_bilateral_splat':
testcase.i:7:12: warning: initialization of 'int' from 'dt_bilateral_t *' makes
integer from pointer without a cast [-Wint-conversion]
    7 |   int oy = b;
      |            ^
testcase.i:10:25: warning: comparison between pointer and integer
   10 |   for (int slice; slice < b; slice++) {
      |                         ^
testcase.i:16:25: warning: initialization of 'float *' from 'int' makes pointer
from integer without a cast [-Wint-conversion]
   16 |     float *dest, *src = oy;
      |                         ^~
testcase.i: In function 'dt_bilateral_splat.simdclone.3':
testcase.i:20:1: error: unrecognizable insn:
   20 | }
      | ^
(insn 1109 1108 462 62 (set (mem/c:TF (plus:DI (reg/f:DI 31 sp)
                (const_int 512 [0x200])) [9  S16 A8])
        (reg:TF 55 v23)) -1
     (expr_list:REG_DEAD (reg:TF 55 v23)
        (nil)))
during RTL pass: sched_fusion
testcase.i:20:1: internal compiler error: in get_attr_type, at
config/aarch64/aarch64.md:24655
0xb1c083 internal_error(char const*, ...)
        ???:0
0xb0f58b fancy_abort(char const*, int, char const*)
        ???:0
0x77453f _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
        ???:0
0x774573 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
        ???:0
0x1148503 get_attr_type(rtx_insn*)
        ???:0
0x10f5a2f schedule_block(basic_block_def**, void*)
        ???:0
0x10cb843 schedule_insns()
        ???:0
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <file:///usr/share/doc/gcc-13/README.Bugs> for instructions.

  parent reply	other threads:[~2023-10-24 12:55 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 [this message]
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
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-e25FlJw5KA@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).