public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher 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, 05 Dec 2023 14:19:28 +0000 [thread overview]
Message-ID: <bug-112707-4-B0Xsbv72Qt@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 #13 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Peter Bergner from comment #12)
> I'll note that you don't always
> get an assembler error, since gcc still passes -many to the assembler for
> non --enable-checking gcc builds, which causes it to accept the fctid insn.
Hrm. Was that an oversight? Should we always do that now? Can you prepare a
patch (and test on some common configs) please?
next prev parent reply other threads:[~2023-12-05 14:19 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
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 [this message]
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-B0Xsbv72Qt@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).