public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98092] [11 Regression] ICE in extract_insn, at recog.c:2315 (error: unrecognizable insn) since r11-4623
Date: Tue, 16 Mar 2021 18:17:14 +0000	[thread overview]
Message-ID: <bug-98092-4-FArMre42im@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98092-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[11 Regression] ICE in      |[11 Regression] ICE in
                   |extract_insn, at            |extract_insn, at
                   |recog.c:2315 (error:        |recog.c:2315 (error:
                   |unrecognizable insn)        |unrecognizable insn) since
                   |                            |r11-4623

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The builtins were added in r11-4623-g05161256d3d2a598966ca1cf676fa0e427570f73 ,
before that it has been rejected with:
pr98092.c: In function ‘h9’:
pr98092.c:4:11: warning: implicit declaration of function
‘__builtin_vec_bcdinvalid’; did you mean ‘__builtin_vec_xxeval’?
[-Wimplicit-function-declaration]
    4 |   return (__builtin_vec_bcdinvalid (un));
      |           ^~~~~~~~~~~~~~~~~~~~~~~~
      |           __builtin_vec_xxeval
pr98092.c:4:3: error: AltiVec argument passed to unprototyped function
    4 |   return (__builtin_vec_bcdinvalid (un));
      |   ^~~~~~

  parent reply	other threads:[~2021-03-16 18:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-02  5:32 [Bug target/98092] New: [11 Regression] ICE in extract_insn, at recog.c:2315 (error: unrecognizable insn) asolokha at gmx dot com
2020-12-02  8:24 ` [Bug target/98092] " rguenth at gcc dot gnu.org
2021-01-14 10:59 ` rguenth at gcc dot gnu.org
2021-01-22 12:46 ` jakub at gcc dot gnu.org
2021-01-22 20:57 ` cel at us dot ibm.com
2021-01-23  1:14 ` segher at gcc dot gnu.org
2021-03-05 14:02 ` jakub at gcc dot gnu.org
2021-03-16 18:17 ` jakub at gcc dot gnu.org [this message]
2021-03-16 18:27 ` [Bug target/98092] [11 Regression] ICE in extract_insn, at recog.c:2315 (error: unrecognizable insn) since r11-4623 segher at gcc dot gnu.org
2021-03-16 19:22 ` cvs-commit at gcc dot gnu.org
2021-03-16 19:25 ` jakub 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-98092-4-FArMre42im@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).