From: Michael Cree <mcree@orcon.net.nz>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org
Subject: Re: [committed] Fix crash accessing builtins in sanitizer.def and after (PR jit/82174)
Date: Sun, 01 Jan 2017 00:00:00 -0000 [thread overview]
Message-ID: <20170917100539.4d4rn3fdsk6uk4xh@tower> (raw)
In-Reply-To: <1505419774-35690-1-git-send-email-dmalcolm@redhat.com>
On Thu, Sep 14, 2017 at 04:09:34PM -0400, David Malcolm wrote:
> Calls to gcc_jit_context_get_builtin_function that accessed builtins
> in sanitizer.def and after (or failed to match any builtin) led to
> a crash accessing a NULL builtin name.
[snip]
> This patch updates jit-builtins.c to cope with such entries, fixing the
> crash.
Thanks for fixing that.
I would now like to get access to the architecture specific builtins.
Any possibility of that being implemented into libgccjit? My project
is basically dead in the water without them.
Secondly, I am trying to work out how to initialise a vector rvalue
with specified values. Something in the vein of
gcc_jit_new_rvalue_from_int() but creating a type with vector
attribute and where each individual element is set to some specified
value and it may not be the same value for each element.
The gcc C manual says "vectors can be subscripted as if the vector
were an array [...]" so I tried initialising a vector with
gcc_jit_context_new_array_access() but that fails with errors that
the vector is not a pointer or array at the time of JIT compilation.
Cheers
Michael.
next prev parent reply other threads:[~2017-09-17 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 0:00 David Malcolm
2017-01-01 0:00 ` Michael Cree [this message]
2017-01-01 0:00 ` David Malcolm
2017-01-01 0:00 ` Michael Cree
2017-01-01 0:00 ` [committed] jit: implement gcc_jit_context_new_rvalue_from_vector David Malcolm
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=20170917100539.4d4rn3fdsk6uk4xh@tower \
--to=mcree@orcon.net.nz \
--cc=dmalcolm@redhat.com \
--cc=jit@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).