public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Antoni Boucher <antoyo@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-1036] libgccjit: Support getting the size of a float [PR105829]
Date: Fri, 10 Jun 2022 02:02:23 +0000 (GMT)	[thread overview]
Message-ID: <20220610020223.3118F3857B94@sourceware.org> (raw)

https://gcc.gnu.org/g:5940b4e59f8e198dbf7e8b733561ef72a9ba2cbc

commit r13-1036-g5940b4e59f8e198dbf7e8b733561ef72a9ba2cbc
Author: Antoni Boucher <bouanto@zoho.com>
Date:   Thu Jun 9 21:37:23 2022 -0400

    libgccjit: Support getting the size of a float [PR105829]
    
    2022-06-09  Antoni Boucher  <bouanto@zoho.com>
    
    gcc/jit/
            PR jit/105829
            * libgccjit.cc: Add support for floating-point types in
            gcc_jit_type_get_size.
    
    gcc/testsuite/
            PR jit/105829
            * jit.dg/test-types.c: Add tests for gcc_jit_type_get_size.

Diff:
---
 gcc/jit/libgccjit.cc              | 4 ++--
 gcc/testsuite/jit.dg/test-types.c | 3 +++
 2 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/gcc/jit/libgccjit.cc b/gcc/jit/libgccjit.cc
index cc6486c9cad..0e76097b4ba 100644
--- a/gcc/jit/libgccjit.cc
+++ b/gcc/jit/libgccjit.cc
@@ -545,8 +545,8 @@ gcc_jit_type_get_size (gcc_jit_type *type)
 {
   RETURN_VAL_IF_FAIL (type, -1, NULL, NULL, "NULL type");
   RETURN_VAL_IF_FAIL
-    (type->is_int (), -1, NULL, NULL,
-     "only getting the size of an integer type is supported for now");
+    (type->is_int () || type->is_float (), -1, NULL, NULL,
+     "only getting the size of integer or floating-point types is supported for now");
   return type->get_size ();
 }
 
diff --git a/gcc/testsuite/jit.dg/test-types.c b/gcc/testsuite/jit.dg/test-types.c
index 6836597d14e..a01944e35fa 100644
--- a/gcc/testsuite/jit.dg/test-types.c
+++ b/gcc/testsuite/jit.dg/test-types.c
@@ -489,4 +489,7 @@ verify_code (gcc_jit_context *ctxt, gcc_jit_result *result)
     CHECK (gcc_jit_compatible_types (
       gcc_jit_context_get_type (ctxt, GCC_JIT_TYPE_LONG),
       gcc_jit_context_get_type (ctxt, GCC_JIT_TYPE_INT64_T)));
+
+  CHECK_VALUE (gcc_jit_type_get_size (gcc_jit_context_get_type (ctxt, GCC_JIT_TYPE_FLOAT)), sizeof (float));
+  CHECK_VALUE (gcc_jit_type_get_size (gcc_jit_context_get_type (ctxt, GCC_JIT_TYPE_DOUBLE)), sizeof (double));
 }


                 reply	other threads:[~2022-06-10  2:02 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220610020223.3118F3857B94@sourceware.org \
    --to=antoyo@gcc.gnu.org \
    --cc=gcc-cvs@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).