public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Dibyendu Majumdar <mobile@majumdar.org.uk>
Cc: jit@gcc.gnu.org
Subject: Re: Compilation error involving comparison and logical operator
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <1435346872.13727.126.camel@surprise> (raw)
In-Reply-To: <CACXZuxe9yjH2h-JeC4mdUAfxEo=gh7it_wbOZGWRhGeDXC5XUA@mail.gmail.com>

On Fri, 2015-06-26 at 20:24 +0100, Dibyendu Majumdar wrote:
> On 26 June 2015 at 10:42, David Malcolm <dmalcolm@redhat.com> wrote:
> > Note that unlike C, libgccjit has no implicit type-coercion: anywhere
> > you want to treat int as bool or vice versa, or convert between float
> > and int, you need to do it explicitly via a cast
> > (gcc_jit_context_new_cast).
> >
> 
> Couple of questions:
> 
> 1. What is the type of a binary logical operator

By "a binary logical operator" presumably you mean the result of
gcc_jit_context_new_comparison.  This has type GCC_JIT_TYPE_BOOL.


> and what effect does
> the result type in gcc_jit_context_new_binary_op() have?

This defines the type of the resulting rvalue.  I believe you can use
this as another way of doing a cast.


> 2. What is the type of unary logical operator

It depends on the result_type passed in to gcc_jit_context_new_unary_op.

> and what is the effect
> of result type in gcc_jit_context_new_unary_op()?

This defines the type of the resulting rvalue.  As above you can use
this as another way of doing a cast.

> The comparison operator does not take a result type so presumably it
> is always boolean?

Correct.


  reply	other threads:[~2015-06-26 19:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 Dibyendu Majumdar
2015-01-01  0:00 ` David Malcolm
2015-01-01  0:00   ` Dibyendu Majumdar
2015-01-01  0:00     ` David Malcolm
2015-01-01  0:00       ` Dibyendu Majumdar
2015-01-01  0:00         ` David Malcolm [this message]
2015-01-01  0:00           ` Dibyendu Majumdar
2015-01-01  0:00 Dibyendu Majumdar
2015-01-01  0:00 Dibyendu Majumdar

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=1435346872.13727.126.camel@surprise \
    --to=dmalcolm@redhat.com \
    --cc=jit@gcc.gnu.org \
    --cc=mobile@majumdar.org.uk \
    /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).