public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kewen.Lin" <linkw@linux.ibm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Peter Bergner <bergner@linux.ibm.com>,
	David Edelsohn <dje.gcc@gmail.com>,
	Segher Boessenkool <segher@kernel.crashing.org>
Subject: PING^3 [PATCH] rs6000: Handle unresolved overloaded builtin [PR105485]
Date: Thu, 28 Jul 2022 16:45:59 +0800	[thread overview]
Message-ID: <e281dffa-eec1-b70f-0215-372f42349555@linux.ibm.com> (raw)
In-Reply-To: <79282dcf-cca9-7ff3-aa25-e0d380e3b185@linux.ibm.com>

Hi,

Gentle ping https://gcc.gnu.org/pipermail/gcc-patches/2022-May/594699.html

BR,
Kewen

> 
>> on 2022/5/13 13:29, Kewen.Lin via Gcc-patches wrote:
>>> Hi,
>>>
>>> PR105485 exposes that new builtin function framework doesn't handle
>>> unresolved overloaded builtin function well.  With new builtin
>>> function support, we don't have builtin info for any overloaded
>>> rs6000_gen_builtins enum, since they are expected to be resolved to
>>> one specific instance.  So when function rs6000_gimple_fold_builtin
>>> faces one unresolved overloaded builtin, the access for builtin info
>>> becomes out of bound and gets ICE then.
>>>
>>> We should not try to fold one unresolved overloaded builtin there
>>> and as the previous support we should emit one error message during
>>> expansion phase like "unresolved overload for builtin ...".
>>>
>>> Bootstrapped and regtested on powerpc64-linux-gnu P8 and
>>> powerpc64le-linux-gnu P9 and P10.
>>>
>>> Is it ok for trunk?
>>>
>>> BR,
>>> Kewen
>>> -----
>>> 	PR target/105485
>>>
>>> gcc/ChangeLog:
>>>
>>> 	* config/rs6000/rs6000-builtin.cc (rs6000_gimple_fold_builtin): Add
>>> 	the handling for unresolved overloaded builtin function.
>>> 	(rs6000_expand_builtin): Likewise.
>>>
>>> gcc/testsuite/ChangeLog:
>>>
>>> 	* g++.target/powerpc/pr105485.C: New test.
>>>
>>> ---
>>>  gcc/config/rs6000/rs6000-builtin.cc         | 13 +++++++++++++
>>>  gcc/testsuite/g++.target/powerpc/pr105485.C |  9 +++++++++
>>>  2 files changed, 22 insertions(+)
>>>  create mode 100644 gcc/testsuite/g++.target/powerpc/pr105485.C
>>>
>>> diff --git a/gcc/config/rs6000/rs6000-builtin.cc b/gcc/config/rs6000/rs6000-builtin.cc
>>> index e925ba9fad9..e102305c90c 100644
>>> --- a/gcc/config/rs6000/rs6000-builtin.cc
>>> +++ b/gcc/config/rs6000/rs6000-builtin.cc
>>> @@ -1294,6 +1294,11 @@ rs6000_gimple_fold_builtin (gimple_stmt_iterator *gsi)
>>>    enum tree_code bcode;
>>>    gimple *g;
>>>
>>> +  /* For an unresolved overloaded builtin, return early here since there
>>> +     is no builtin info for it and we are unable to fold it.  */
>>> +  if (fn_code > RS6000_OVLD_NONE)
>>> +    return false;
>>> +
>>>    size_t uns_fncode = (size_t) fn_code;
>>>    enum insn_code icode = rs6000_builtin_info[uns_fncode].icode;
>>>    const char *fn_name1 = rs6000_builtin_info[uns_fncode].bifname;
>>> @@ -3295,6 +3300,14 @@ rs6000_expand_builtin (tree exp, rtx target, rtx /* subtarget */,
>>>    tree fndecl = TREE_OPERAND (CALL_EXPR_FN (exp), 0);
>>>    enum rs6000_gen_builtins fcode
>>>      = (enum rs6000_gen_builtins) DECL_MD_FUNCTION_CODE (fndecl);
>>> +
>>> +  /* Emit error message if it's an unresolved overloaded builtin.  */
>>> +  if (fcode > RS6000_OVLD_NONE)
>>> +    {
>>> +      error ("unresolved overload for builtin %qF", fndecl);
>>> +      return const0_rtx;
>>> +    }
>>> +
>>>    size_t uns_fcode = (size_t)fcode;
>>>    enum insn_code icode = rs6000_builtin_info[uns_fcode].icode;
>>>
>>> diff --git a/gcc/testsuite/g++.target/powerpc/pr105485.C b/gcc/testsuite/g++.target/powerpc/pr105485.C
>>> new file mode 100644
>>> index 00000000000..a3b8290df8c
>>> --- /dev/null
>>> +++ b/gcc/testsuite/g++.target/powerpc/pr105485.C
>>> @@ -0,0 +1,9 @@
>>> +/* It's to verify no ICE here, ignore error/warning messages since
>>> +   they are not test points here.  */
>>> +/* { dg-excess-errors "pr105485" } */
>>> +
>>> +template <class> void __builtin_vec_vslv();
>>> +typedef  __attribute__((altivec(vector__))) char T;
>>> +T b (T c, T d) {
>>> +    return __builtin_vec_vslv(c, d);
>>> +}

  reply	other threads:[~2022-07-28  8:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-13  5:29 Kewen.Lin
2022-06-06  8:50 ` PING^1 " Kewen.Lin
2022-06-23  2:02   ` PING^2 " Kewen.Lin
2022-07-28  8:45     ` Kewen.Lin [this message]
2022-08-15  8:06       ` PING^4 " Kewen.Lin
2022-08-29  6:26         ` PING^5 " Kewen.Lin

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=e281dffa-eec1-b70f-0215-372f42349555@linux.ibm.com \
    --to=linkw@linux.ibm.com \
    --cc=bergner@linux.ibm.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=segher@kernel.crashing.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).