From: Jakub Jelinek <jakub@redhat.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Phil Muldoon <pmuldoon@redhat.com>, DJ Delorie <dj@redhat.com>,
Alexandre Oliva <aoliva@redhat.com>,
Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
gcc-patches@gcc.gnu.org
Subject: Re: libcc1
Date: Wed, 29 Oct 2014 20:43:00 -0000 [thread overview]
Message-ID: <20141029201059.GV10376@tucnak.redhat.com> (raw)
In-Reply-To: <20141029104551.GR10376@tucnak.redhat.com>
On Wed, Oct 29, 2014 at 11:45:51AM +0100, Jakub Jelinek wrote:
> On Wed, Oct 29, 2014 at 11:37:26AM +0100, Paolo Bonzini wrote:
> > On 10/29/2014 11:31 AM, Jakub Jelinek wrote:
> > > shouldn't libcc1 be in build_tools instead?
> > > I mean, it is a library meant to be dlopened by gdb and gcc
> > > plugin that uses that library, so in canadian-cross should be
> > > for the build target, where the resulting compiler will be run
> > > and where gdb will be run.
> >
> > That is host, not build. Build is the system you are on.
>
> Oops, sorry, mixed that, sure, it should be host tool then.
>
> So without the first two hunks and third hunk changed so that it
> doesn't bootstrap it? Doesn't that mean that when bootstrapping
> natively it will be built by the system compiler rather than the
> newly built compiler? I think fixincludes is only built during
> stage1 normally, we don't need libcc1 during stage1/stage2 unless
> not bootstrapping, it is needed just for installation and testing.
>
> --- configure.ac 2014-10-28 14:39:53.018852391 +0100
> +++ configure.ac 2014-10-29 11:43:19.873216226 +0100
> @@ -2677,6 +2677,7 @@ for module in ${configdirs} ; do
> fi
> case ${module},${bootstrap_fixincludes} in
> fixincludes,no) host_bootstrap_suffix=no-bootstrap ;;
> + libcc1,*) host_bootstrap_suffix=no-bootstrap ;;
> *) host_bootstrap_suffix=$bootstrap_suffix ;;
> esac
> extrasub_host="$extrasub_host
Makefile.def has:
host_modules= { module= libcc1; bootstrap=true;
extra_configure_flags=--enable-shared; };
wonder if that bootstrap=true; is desirable there.
Jakub
next prev parent reply other threads:[~2014-10-29 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 10:35 libcc1 Jakub Jelinek
2014-10-29 10:37 ` libcc1 Paolo Bonzini
2014-10-29 10:48 ` libcc1 Jakub Jelinek
2014-10-29 10:51 ` libcc1 Paolo Bonzini
2014-10-29 20:43 ` Jakub Jelinek [this message]
2014-10-30 8:51 ` libcc1 Paolo Bonzini
2014-10-31 11:03 ` [PATCH] Don't bootstrap libcc1 Jakub Jelinek
2014-10-31 11:16 ` Richard Biener
2014-10-29 11:01 ` libcc1 Phil Muldoon
2014-10-29 11:24 ` libcc1 Paolo Bonzini
2014-10-29 11:46 ` libcc1 Phil Muldoon
2014-10-29 14:32 ` libcc1 Phil Muldoon
2014-10-29 14:39 ` libcc1 Phil Muldoon
2014-10-29 20:49 ` libcc1 Jeff Law
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=20141029201059.GV10376@tucnak.redhat.com \
--to=jakub@redhat.com \
--cc=Ralf.Wildenhues@gmx.de \
--cc=aoliva@redhat.com \
--cc=bonzini@gnu.org \
--cc=dj@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pmuldoon@redhat.com \
/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).