public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Michael Cree <mcree@orcon.net.nz>
Cc: jit@gcc.gnu.org
Subject: Re: [committed] jit: add gcc_jit_type_get_vector
Date: Sun, 01 Jan 2017 00:00:00 -0000	[thread overview]
Message-ID: <1502985078.3741.26.camel@redhat.com> (raw)
In-Reply-To: <20170816211520.GA2399@cree.waikato.ac.nz>

On Thu, 2017-08-17 at 09:15 +1200, Michael Cree wrote:
> On Wed, Aug 16, 2017 at 10:01:57AM -0400, David Malcolm wrote:
> > On Wed, 2017-08-16 at 21:58 +1200, Michael Cree wrote:
> > > 
> > > But I have hit a problem which I suspect is a bug in the gcc
> > > optimiser.
> > > 
> > > In the vein of your example above, but working on uint8_t pixel
> > > data
> > > and adding saturation, the jit compiler segfaults in the
> > > optimiser. I
> > > provide below the gimple produced by the function that causes the
> > > problem (I presume that is more useful than the code calling the
> > > gcc_jit routines), 
> > 
> > There's actually a handy entrypoint for generating minimal
> > reproducers
> > for such crashes:
> >   gcc_jit_context_dump_reproducer_to_file
> > 
> > https://gcc.gnu.org/onlinedocs/jit/topics/contexts.html#gcc_jit_con
> > text_dump_reproducer_to_file
> > 
> > Can you add a call to that to your code (after the context is fully
> > populated), and see if the resulting .c file leads to the crash
> > when
> > run?  If so, can you post the .c file here please (or attach it to
> > bugzilla), and hopefully I can then reproduce it at my end.
> 
> Attached.
> 
> Cheers
> Michael.

Thanks.  I'm able to reproduce the crash using that; am investigating.

Dave

  reply	other threads:[~2017-08-17 15:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-01  0:00 does libgccjit support vector types? Michael Cree
2017-01-01  0:00 ` David Malcolm
2017-01-01  0:00   ` Michael Cree
2017-01-01  0:00     ` [committed] jit: add gcc_jit_type_get_vector David Malcolm
2017-01-01  0:00       ` Michael Cree
2017-01-01  0:00         ` David Malcolm
2017-01-01  0:00           ` Michael Cree
2017-01-01  0:00             ` David Malcolm [this message]
2017-01-01  0:00               ` [committed] jit: fix segfault with autovectorization (PR tree-optimization/46805) 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=1502985078.3741.26.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=jit@gcc.gnu.org \
    --cc=mcree@orcon.net.nz \
    /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).