From: Jakub Jelinek <jakub@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH: toplev.c] PR jit/64721: don't install signal-handlers when running within libgccjit
Date: Thu, 01 Jan 2015 00:00:00 -0000 [thread overview]
Message-ID: <20150122212853.GP1746@tucnak.redhat.com> (raw)
In-Reply-To: <1421880243-21485-1-git-send-email-dmalcolm@redhat.com>
On Wed, Jan 21, 2015 at 05:44:03PM -0500, David Malcolm wrote:
> Don't install signal handlers in toplev.c if we're called from libgccjit,
> only install them if we're called from main.c, thus avoiding
> touching process-wide state from a shared library (see the PR for
> details of how this is currently leading to SIGSEGV on errors in
> "make check-jit").
>
> Is this one sufficiently obvious to still be applicable in stage 4?
> (assuming bootstrap?)
>
> gcc/ChangeLog:
> PR jit/64721
> * main.c (main): Construct toplev instances with init_signals=true.
> * toplev.c (general_init): Add param "init_signals", and use it to
> conditionalize the calls to signal and host_hooks.extra_signals.
> (toplev::toplev): Add param "init_signals".
> (toplev::main): When invoking general_init, pass m_init_signals
> to control whether signal-handlers are installed.
> * toplev.h (toplev::toplev): Add param "init_signals".
> (toplev::m_init_signals): New field.
>
> gcc/jit/ChangeLog:
> PR jit/64721
> * jit-playback.c (gcc::jit::playback::context::compile): Construct
> toplev instances with init_signals=false.
Ok for stage4.
Jakub
prev parent reply other threads:[~2015-01-22 21:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 0:00 David Malcolm
2015-01-01 0:00 ` Jakub Jelinek [this message]
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=20150122212853.GP1746@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--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).