public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/104136] Gcc cannot compile wrf_r for power10 using -Ofast Date: Thu, 20 Jan 2022 18:27:48 +0000 [thread overview] Message-ID: <bug-104136-4-WJuhgzZq6s@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104136-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104136 --- Comment #1 from Michael Meissner <meissner at gcc dot gnu.org> --- Created attachment 52244 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52244&action=edit Patch to mark XXSPLTIW and XXSPLTIDP as possibly being prefixed If you compile module_advect_em.F90 with -Ofast -mcpu=power10, one module is large enough that we can't use a single conditional jump to span the function. Instead, we have to reverse the condition, and do a conditional jump around an unconditional branch. It turns out when xxspltiw and xxspltdp instructions were generated, they were not marked as being prefixed (i.e. length of 12 bytes instead of 4 bytes). This meant the calculations for the branch length were off, which in turn meant the assembler raised an error because it couldn't do the conditional jump. The fix is to set the maybe_prefixed attribute so that insns with the type 'vecperm' might be prefixed. Then in the code that optionally puts a 'p' in front of the insn skip doing so for the permutes (i.e. load constant with splat instruction).
next prev parent reply other threads:[~2022-01-20 18:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-19 23:58 [Bug target/104136] New: " meissner at gcc dot gnu.org 2022-01-20 0:00 ` [Bug target/104136] " meissner at gcc dot gnu.org 2022-01-20 18:27 ` meissner at gcc dot gnu.org [this message] 2022-01-20 19:48 ` meissner at gcc dot gnu.org 2022-01-21 19:51 ` meissner at gcc dot gnu.org 2022-01-21 23:09 ` cvs-commit at gcc dot gnu.org 2022-01-22 2:34 ` meissner at gcc dot gnu.org 2022-01-22 2:35 ` meissner 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-104136-4-WJuhgzZq6s@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: linkBe 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).