public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug target/112308] New: [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32'
@ 2023-10-31 10:19 tschwinge at gcc dot gnu.org
  2023-10-31 12:04 ` [Bug target/112308] " rguenth at gcc dot gnu.org
                   ` (3 more replies)
  0 siblings, 4 replies; 5+ messages in thread
From: tschwinge at gcc dot gnu.org @ 2023-10-31 10:19 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112308

            Bug ID: 112308
           Summary: [14 Regression] GCN: 'error: literal operands are not
                    supported' for 'v_add_co_u32'
           Product: gcc
           Version: 14.0
            Status: UNCONFIRMED
          Keywords: rejects-valid, testsuite-fail
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: tschwinge at gcc dot gnu.org
                CC: ams at gcc dot gnu.org, jules at gcc dot gnu.org
  Target Milestone: ---
            Target: GCN

(Assuming my tacking is to be believed) something in Git commit
r14-4720-gaf4bb221153359f5948da917d5ef2df738bb1e61..r14-4986-g4d3d2cdb574488223d023b590c3a34ddd93f4dae
regresses (or, likely, exposes?) the following:

    PASS: gcc.c-torture/compile/pr48596.c   -O0  (test for excess errors)
    PASS: gcc.c-torture/compile/pr48596.c   -O1  (test for excess errors)
    PASS: gcc.c-torture/compile/pr48596.c   -O2  (test for excess errors)
    [-PASS:-]{+FAIL:+} gcc.c-torture/compile/pr48596.c   -O3
-fomit-frame-pointer -funroll-loops -fpeel-loops -ftracer -finline-functions 
(test for excess errors)
    [-PASS:-]{+FAIL:+} gcc.c-torture/compile/pr48596.c   -O3 -g  (test for
excess errors)
    PASS: gcc.c-torture/compile/pr48596.c   -Os  (test for excess errors)

    /tmp/ccZPdmCF.s:123:33: error: literal operands are not supported
            v_add_co_u32    v4, s[22:23], v7, 80
                                              ^

That's the only instance of 'error: literal operands are not supported' I can
find in all test logs.

That's for '-march=gfx90a', and that's LLVM 13.0.1, in case that's relevant. 
(I'm happy to just have this FAIL if the issue is due to old/buggy LLVM.)

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/112308] [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32'
  2023-10-31 10:19 [Bug target/112308] New: [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32' tschwinge at gcc dot gnu.org
@ 2023-10-31 12:04 ` rguenth at gcc dot gnu.org
  2023-11-09 14:43 ` ams at gcc dot gnu.org
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 5+ messages in thread
From: rguenth at gcc dot gnu.org @ 2023-10-31 12:04 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112308

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.0

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/112308] [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32'
  2023-10-31 10:19 [Bug target/112308] New: [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32' tschwinge at gcc dot gnu.org
  2023-10-31 12:04 ` [Bug target/112308] " rguenth at gcc dot gnu.org
@ 2023-11-09 14:43 ` ams at gcc dot gnu.org
  2023-11-10 11:24 ` cvs-commit at gcc dot gnu.org
  2023-11-10 11:25 ` ams at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: ams at gcc dot gnu.org @ 2023-11-09 14:43 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112308

Andrew Stubbs <ams at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2023-11-09
     Ever confirmed|0                           |1
           Assignee|unassigned at gcc dot gnu.org      |ams at gcc dot gnu.org

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/112308] [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32'
  2023-10-31 10:19 [Bug target/112308] New: [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32' tschwinge at gcc dot gnu.org
  2023-10-31 12:04 ` [Bug target/112308] " rguenth at gcc dot gnu.org
  2023-11-09 14:43 ` ams at gcc dot gnu.org
@ 2023-11-10 11:24 ` cvs-commit at gcc dot gnu.org
  2023-11-10 11:25 ` ams at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2023-11-10 11:24 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112308

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Stubbs <ams@gcc.gnu.org>:

https://gcc.gnu.org/g:e24b0fed9234716c146aaf6f8c1b39170e43a6f3

commit r14-5318-ge24b0fed9234716c146aaf6f8c1b39170e43a6f3
Author: Andrew Stubbs <ams@codesourcery.com>
Date:   Fri Nov 10 11:13:55 2023 +0000

    amdgcn: Fix v_add constraints (pr112308)

    The instruction doesn't allow "B" constants for the vop3b encoding (used
when
    the cc register isn't VCC), so fix the pattern and all the insns that might
get
    split to it post-reload.

    Also switch to the new constraint format for ease of adding new
alternatives.

    gcc/ChangeLog:

            PR target/112308
            * config/gcn/gcn-valu.md (add<mode>3<exec_clobber>): Fix B
constraint
            and switch to the new format.
            (add<mode>3_dup<exec_clobber>): Likewise.
            (add<mode>3_vcc<exec_vcc>): Likewise.
            (add<mode>3_vcc_dup<exec_vcc>): Likewise.
            (add<mode>3_vcc_zext_dup): Likewise.
            (add<mode>3_vcc_zext_dup_exec): Likewise.
            (add<mode>3_vcc_zext_dup2): Likewise.
            (add<mode>3_vcc_zext_dup2_exec): Likewise.

^ permalink raw reply	[flat|nested] 5+ messages in thread

* [Bug target/112308] [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32'
  2023-10-31 10:19 [Bug target/112308] New: [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32' tschwinge at gcc dot gnu.org
                   ` (2 preceding siblings ...)
  2023-11-10 11:24 ` cvs-commit at gcc dot gnu.org
@ 2023-11-10 11:25 ` ams at gcc dot gnu.org
  3 siblings, 0 replies; 5+ messages in thread
From: ams at gcc dot gnu.org @ 2023-11-10 11:25 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112308

Andrew Stubbs <ams at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #2 from Andrew Stubbs <ams at gcc dot gnu.org> ---
This should be fixed now.

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2023-11-10 11:25 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-10-31 10:19 [Bug target/112308] New: [14 Regression] GCN: 'error: literal operands are not supported' for 'v_add_co_u32' tschwinge at gcc dot gnu.org
2023-10-31 12:04 ` [Bug target/112308] " rguenth at gcc dot gnu.org
2023-11-09 14:43 ` ams at gcc dot gnu.org
2023-11-10 11:24 ` cvs-commit at gcc dot gnu.org
2023-11-10 11:25 ` ams at gcc dot gnu.org

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).