public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/64780] toplevel configure should reject jit as a language if --enable-host-shared is not supplied
Date: Tue, 27 Jan 2015 15:46:00 -0000	[thread overview]
Message-ID: <bug-64780-4-tSiJbr0CYs@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-64780-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64780

--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
We seem to have two choices here:

(A) default to --enable-host-shared when jit is an enabled language
(B) have the toplevel configure reject jit as language if --enable-host-shared
is not supplied.

FWIW apparently Darwin defaults to position-independent code, so it's not
explicitly needed there.

That said, I think I prefer (B), since there is a performance cost: my thinking
here is that there are people who perform benchmarking of GCC (and publish
their results on prominent websites).  If they turn on the jit and use the same
configuration to do their benchmarking of the rest of GCC, they'll see GCC 5 be
apparently slower than earlier releases.  You're a gcc expert, and you ran into
this issue, so it's clearly unreasonable to expect a 3rd-party reviewer to
notice this detail on their own.

So I'm thinking of implementing (B), and putting in a note in the error message
recommending that people configure and build GCC twice to avoid the performance
hit, so that it can be self-documenting.


  reply	other threads:[~2015-01-27 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-25  1:56 [Bug jit/64780] New: " pinskia at gcc dot gnu.org
2015-01-27 15:46 ` dmalcolm at gcc dot gnu.org [this message]
2015-01-27 17:13 ` [Bug jit/64780] " dmalcolm at gcc dot gnu.org
2015-01-29 16:26 ` dmalcolm at gcc dot gnu.org
2015-03-13 17:32 ` dmalcolm at gcc dot gnu.org

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=bug-64780-4-tSiJbr0CYs@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).