From: Uros Bizjak <ubizjak@gmail.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, bootstrap]: Add bootstrap-lto-noplugin build configuration (PR65537)
Date: Wed, 25 Mar 2015 19:16:00 -0000 [thread overview]
Message-ID: <CAFULd4aKXP_38Q4w5UXbHSYXh3PEzb=wFM_X_aqg22d3t55m6A@mail.gmail.com> (raw)
In-Reply-To: <20150325142354.GP1746@tucnak.redhat.com>
On Wed, Mar 25, 2015 at 3:23 PM, Jakub Jelinek <jakub@redhat.com> wrote:
>> Attached patch introduces bootstrap-lto-noplugin bootstrap
>> configuration for hosts that do not support linker plugin (e.g. CentOS
>> 5.11 with binutils 2.17). Also, the patch adds some additional
>> documentation to bootstrap-lto option.
>>
>> config/ChangeLog:
>>
>> 2015-03-24 Uros Bizjak <ubizjak@gmail.com>
>>
>> PR bootstrap/65537
>> * bootstrap-lto-noplugin.mk: New build configuration.
>>
>> gcc/ChangeLog:
>>
>> 2015-03-24 Uros Bizjak <ubizjak@gmail.com>
>>
>> PR bootstrap/65537
>> * doc/install.texi (Building a native compiler): Document new
>> bootstrap-lto-noplugin configuration. Mention that bootstrap-lto
>> configuration assumes that the host supports the linker plugin.
>>
>> Patch was bootstrapped and tested on x86_64-linux-gnu (CentOS 5.11)
>> host, configured with --with-build-config=bootstrap-lto build
>> configuration.
>
> and not --with-build-config=bootstrap-lto-noplugin ?
Oh ... with bootstrap-lto-noplugin option. The bootstrap with linker
plugin does not work at all on CentOS 5.11.
Uros.
next prev parent reply other threads:[~2015-03-25 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 16:43 Uros Bizjak
2015-03-25 14:24 ` Jakub Jelinek
2015-03-25 19:16 ` Uros Bizjak [this message]
2015-03-26 1:11 ` Jan Hubicka
2015-03-26 8:20 ` Uros Bizjak
2015-04-06 12:45 ` Gerald Pfeifer
2015-04-06 17:19 ` Sandra Loosemore
2015-04-08 12:13 ` Gerald Pfeifer
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='CAFULd4aKXP_38Q4w5UXbHSYXh3PEzb=wFM_X_aqg22d3t55m6A@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@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).