Bug 2255744 - [aarch64] error: unrecognizable insn
Summary: [aarch64] error: unrecognizable insn
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gcc
Version: 39
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: 2255745 2259059
TreeView+ depends on / blocked
 
Reported: 2023-12-24 14:00 UTC by Germano Massullo (Thetra)
Modified: 2024-03-20 12:24 UTC (History)
13 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-02-13 13:16:43 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
GNU Compiler Collection 111677 0 P3 NEW [12/13/14 Regression] darktable build on aarch64 fails with unrecognizable insn due to -fstack-protector changes 2023-12-29 23:22:45 UTC

Description Germano Massullo (Thetra) 2023-12-24 14:00:54 UTC 
Hello, the following GCC builds fail only on aarch64, therefore I suspect that there may be a problem on GCC
https://koji.fedoraproject.org/koji/taskinfo?taskID=110749060


/builddir/build/BUILD/darktable-4.6.0/src/common/bilateral.c:297:1: error: unrecognizable insn:
  297 | }
      | ^
(insn 563 562 564 3 (set (mem/c:TF (plus:DI (reg/f:DI 31 sp)
                (const_int 512 [0x200])) [64  S16 A8])
        (reg:TF 54 v22)) -1
     (expr_list:REG_DEAD (reg:TF 54 v22)
        (nil)))


Reproducible: Always
Comment 1 Jakub Jelinek 2024-02-13 13:16:43 UTC 
Should be already fixed in gcc-14.0.1-0.6.fc40.
Comment 2 Miloš Komarčević 2024-03-11 11:17:39 UTC 
Any plans to include in f38 & f39 as well please? AFAICT, the fix has already been backported to the gcc-13 branch upstream...
Comment 3 Jonathan Wakely 2024-03-11 14:41:05 UTC 
If the patch is in the upstream branch then it will make it to Fedora when the package is updated to a new upstream snapshot, which happens routinely. No backports are needed.
Comment 4 Miloš Komarčević 2024-03-20 12:24:51 UTC 
Thanks, I see that gcc-13.2.1-7 is now on the way.
Note You need to log in before you can comment on or make changes to this bug.