public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: JonY <10walls@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Cygwin/MinGW: Do not version lto plugins
Date: Wed, 9 Sep 2020 09:21:49 +0200	[thread overview]
Message-ID: <CAFiYyc1hAenw+Sdr=dDNpO_yZVyPSoNpPAimao=zX61V-reQ6A@mail.gmail.com> (raw)
In-Reply-To: <82361830-475f-85ab-11bb-c4d8a595754b@gmail.com>

On Wed, Sep 9, 2020 at 2:28 AM JonY via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
> Hello,
>
> The lto plugis are tied to the built GCC anyway, so there isn't much
> point to versioning them.

In fact the lto plugins are not tied to the built GCCs very much, instead
we try to ensure compatibility so that a single plugin can be used with
multiple GCC versions.

> * gcc/config.host: Remove version string
> * lto-plugin/Makefile.am: Use libtool -avoid-version
> * lto-plugin/Makefile.in: Regenerate
>
> This patch has been in use with Cygwin gcc for a long time and should be
> pushed upstream. Patch OK?

The libtool docs are not very specific here but does this affect the
result for Linux ELF platforms at all?

Richard.

>

  reply	other threads:[~2020-09-09  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09  0:26 JonY
2020-09-09  7:21 ` Richard Biener [this message]
2020-09-09  7:32   ` JonY
2020-09-10  0:26     ` JonY
2020-09-10  9:44       ` Richard Biener
2020-09-10 11:57         ` JonY
2020-09-21 11:33           ` Martin Liška
2020-09-21 11:37             ` Richard Biener
2020-09-21 11:41               ` Martin Liška
2020-09-21 11:38             ` Martin Liška
2020-09-21 13:09               ` JonY
2020-09-21 13:23                 ` Martin Liška

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='CAFiYyc1hAenw+Sdr=dDNpO_yZVyPSoNpPAimao=zX61V-reQ6A@mail.gmail.com' \
    --to=richard.guenther@gmail.com \
    --cc=10walls@gmail.com \
    --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).