public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112707] [14 regression] gcc 14 outputs invalid assembly on ppc: Error: unrecognized opcode: `fctid'
Date: Tue, 28 Nov 2023 02:26:13 +0000	[thread overview]
Message-ID: <bug-112707-4-IIjYZeiiSY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112707-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Kewen Lin <linkw at gcc dot gnu.org> ---
(In reply to HaoChen Gui from comment #9)
> (In reply to Segher Boessenkool from comment #8)
> > Yeah, it tested for ISA 2.04 before.  That was an attempt at including 476
> > probably?
> > 
> > We really should have a TARGET_FCTID, on for TARGET_POWERPC64 or for cpu 476
> > (so
> > NOT user-selectable separately, of course!); not try to use pre-existing
> > flags for this, which might work but will forever stay confusing.
> > 
> > So either a separate OPTION_FCTID for in rs6000-cpus.def, or TARGET_FCTID. 
> > Either
> > works for me.
> > 
> > (Background: in ISA 1.xx it was for 64-bit implementations only.  But it
> > does not
> > need 64-bit registers or a 64-bit integer pipeline at all, it is an FP
> > instruction
> > that works on FP registers, which always are 64-bit.  The instruction was
> > implemented
> > on the 476).
> 
> Thanks for your explanation.
> 
> I found "fctid" is supported on PPC64 and PPC476 from assembler source code.
> {“fctid”,       XRC(63,814,0),  XRA_MASK,    PPC64,     PPCVLE,        
> {FRT, FRB}},
> {“fctid”,       XRC(63,814,0),  XRA_MASK,    PPC476,    PPCVLE,        
> {FRT, FRB}},
> 
> But powerpc7450 only enables PPC. That's why assembler complains.
>   { "7450",    PPC_OPCODE_PPC | PPC_OPCODE_7450 | PPC_OPCODE_ALTIVEC, 0 },
> 
> My question is: can "fctid" be executed on powerpc7450 such a 32bit
> processor? If it's supported, should the assembler be changed also (replace
> the PPC64 with PPC for fctid)?

Good question, I think it's no, the assembler implementation looks to match the
documentation, as I can't find insn fctid in powerpc7450 doc:
https://www.nxp.com.cn/docs/en/reference-manual/MPC7450UM.pdf

  parent reply	other threads:[~2023-11-28  2:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25  3:30 [Bug c/112707] New: " csfore at posteo dot net
2023-11-25  3:31 ` [Bug target/112707] [14 regression] " csfore at posteo dot net
2023-11-25  3:31 ` csfore at posteo dot net
2023-11-25  3:37 ` pinskia at gcc dot gnu.org
2023-11-27  2:19 ` guihaoc at gcc dot gnu.org
2023-11-27  2:23 ` csfore at posteo dot net
2023-11-27  2:28 ` csfore at posteo dot net
2023-11-27  2:39 ` csfore at posteo dot net
2023-11-27 13:30 ` segher at gcc dot gnu.org
2023-11-28  1:56 ` guihaoc at gcc dot gnu.org
2023-11-28  2:26 ` linkw at gcc dot gnu.org [this message]
2023-12-04 23:02 ` bergner at gcc dot gnu.org
2023-12-05  0:52 ` bergner at gcc dot gnu.org
2023-12-05 14:19 ` segher at gcc dot gnu.org
2023-12-05 17:46 ` bergner at gcc dot gnu.org
2023-12-11  0:46 ` cvs-commit at gcc dot gnu.org
2023-12-11  0:47 ` cvs-commit at gcc dot gnu.org
2023-12-11  0:48 ` guihaoc 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-112707-4-IIjYZeiiSY@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).