public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, binutils@sourceware.org
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 3/3] Support the PGO build for binutils+gdb
Date: Thu, 17 Dec 2020 17:54:18 +0100	[thread overview]
Message-ID: <bc5f6c8c-a38a-c96c-1414-c28e4eb9eda4@ubuntu.com> (raw)
In-Reply-To: <20201029191132.137382-4-hjl.tools@gmail.com>

On 10/29/20 8:11 PM, H.J. Lu via Binutils wrote:
> diff --git a/configure.ac b/configure.ac
> index 7c4bdff0fa..eea9a21099 100644
> --- a/configure.ac
> +++ b/configure.ac
> +  if test "$enable_pgo_build" = "lto"; then
> +    AC_MSG_CHECKING([whether the compiler supports -flto=jobserver])
> +    old_CFLAGS="$CFLAGS"
> +    PGO_BUILD_LTO_CFLAGS="-flto=jobserver"

that should add -ffat-lto-objects unless you are configuring with --disable-static.

> +    CFLAGS="$CFLAGS $PGO_BUILD_LTO_CFLAGS"
> +    AC_COMPILE_IFELSE([AC_LANG_SOURCE([int foo;])],,
> +		      [PGO_BUILD_LTO_CFLAGS=])
> +    CFLAGS="$old_CFLAGS"
> +    if test -n "$PGO_BUILD_LTO_CFLAGS"; then
> +      AC_MSG_RESULT([yes])
> +    else
> +      AC_MSG_RESULT([no])
> +      AC_MSG_WARN([LTO is disabled for the PGO build])
> +    fi
> +  fi

Matthias

  parent reply	other threads:[~2020-12-17 16:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29 19:11 [PATCH 0/3] Enable PGO/LTO " H.J. Lu
2020-10-29 19:11 ` [PATCH 1/3] GCC: Pass --plugin to AR and RANLIB H.J. Lu
2021-01-11 14:58   ` Luis Machado
2021-01-11 16:48     ` Hans-Peter Nilsson
2020-10-29 19:11 ` [PATCH 2/3] Binutils: " H.J. Lu
2020-10-29 19:11 ` [PATCH 3/3] Support the PGO build for binutils+gdb H.J. Lu
2020-12-17 16:16   ` Matthias Klose
2020-12-17 16:54   ` Matthias Klose [this message]
2020-11-16 13:11 ` PING [PATCH 0/3] Enable PGO/LTO " H.J. Lu
2020-11-27 15:21 ` Martin Liška
2020-12-15 17:10 ` PING^1 " H.J. Lu

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=bc5f6c8c-a38a-c96c-1414-c28e4eb9eda4@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=binutils@sourceware.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.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).