public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org
Subject: PING: PATCH: PR bootstrap/45954: LTO isn't enabled in stage1 cc1 with --with-build-config=bootstrap-lto
Date: Wed, 20 Oct 2010 03:17:00 -0000	[thread overview]
Message-ID: <AANLkTi=GaTTs9gAGdGyV21fBZRXCY=RLLWAr47rHxHko@mail.gmail.com> (raw)

On Sun, Oct 17, 2010 at 3:07 PM, H.J. Lu <hongjiu.lu@intel.com> wrote:
> Hi,
>
> This patch enables lto for stage1 if LTO is enabled. OK for trunk?
>
> Thanks.
>
>
> H.J.
> ---
> 2010-10-17  H.J. Lu  <hongjiu.lu@intel.com>
>
>        PR bootstrap/45954
>        * configure.ac: Enable lto for stage1 if LTO is enabled.
>        * configure: Regenerated.
>
> diff --git a/configure b/configure
> index b1fbfaa..1397c11 100755
> --- a/configure
> +++ b/configure
> @@ -6711,7 +6711,11 @@ fi
>
>
>  # By default, C is the only stage 1 language.
> -stage1_languages=,c,
> +if test "$enable_lto" = "yes" ; then
> +  stage1_languages=,c,lto,
> +else
> +  stage1_languages=,c,
> +fi
>
>  # Target libraries that we bootstrap.
>  bootstrap_target_libs=,target-libgcc,
> @@ -6905,7 +6909,12 @@ if test "${enable_stage1_languages+set}" = set; then :
>   enableval=$enable_stage1_languages; case ,${enable_stage1_languages}, in
>     ,no,|,,)
>       # Set it to something that will have no effect in the loop below
> -      enable_stage1_languages=c ;;
> +      if test "$enable_lto" = "yes" ; then
> +        enable_stage1_languages=c,lto
> +      else
> +        enable_stage1_languages=c
> +      fi
> +      ;;
>     ,yes,)
>       enable_stage1_languages=`echo $new_enable_languages | \
>        sed -e "s/^,//" -e "s/,$//" ` ;;
> diff --git a/configure.ac b/configure.ac
> index bf5fe3a..f4521bd 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -1817,7 +1817,11 @@ fi],[if test x"$default_enable_lto" = x"yes" ; then
>
>
>  # By default, C is the only stage 1 language.
> -stage1_languages=,c,
> +if test "$enable_lto" = "yes" ; then
> +  stage1_languages=,c,lto,
> +else
> +  stage1_languages=,c,
> +fi
>
>  # Target libraries that we bootstrap.
>  bootstrap_target_libs=,target-libgcc,
> @@ -2012,7 +2016,12 @@ if test -d ${srcdir}/gcc; then
>   [case ,${enable_stage1_languages}, in
>     ,no,|,,)
>       # Set it to something that will have no effect in the loop below
> -      enable_stage1_languages=c ;;
> +      if test "$enable_lto" = "yes" ; then
> +        enable_stage1_languages=c,lto
> +      else
> +        enable_stage1_languages=c
> +      fi
> +      ;;
>     ,yes,)
>       enable_stage1_languages=`echo $new_enable_languages | \
>        sed -e "s/^,//" -e "s/,$//" ` ;;
>

PING

-- 
H.J.

             reply	other threads:[~2010-10-19 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20  3:17 H.J. Lu [this message]
2010-10-20  8:51 ` Paolo Bonzini
2010-10-20 14:20   ` H.J. Lu
2010-10-20 14:40     ` Paolo Bonzini

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='AANLkTi=GaTTs9gAGdGyV21fBZRXCY=RLLWAr47rHxHko@mail.gmail.com' \
    --to=hjl.tools@gmail.com \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@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).