public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: JonY <10walls@gmail.com>, Richard Biener <richard.guenther@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Cygwin/MinGW: Do not version lto plugins
Date: Mon, 21 Sep 2020 13:33:33 +0200	[thread overview]
Message-ID: <c2b236bd-cf9e-04de-b224-e6ee1cf09995@suse.cz> (raw)
In-Reply-To: <853d52ec-40dd-8b98-e323-61d6179f6c4d@gmail.com>

On 9/10/20 1:57 PM, JonY via Gcc-patches wrote:
> On 9/10/20 9:44 AM, Richard Biener wrote:
>>>
>>> I can confirm liblto is still loaded correctly from the logs, likewise
>>> renaming it away will cause an error.
>>>
>>> Seems to be fine on Linux.
>>
>> OK then.
>>
>> Thanks,
>> Richard.
>>
> 
> Thanks for reviewing, pushed to master branch
> ae6cf62861b5e9acb518b016ddbe7f783206f65f.
> 

Hello.

I see the patch broke auto-loading support in bintuils which
automatically try to load plugins in bfd-plugins folder:

One example:
[  108s] ar cr libbuiltins.a builtins.o alias.o bind.o break.o builtin.o caller.o cd.o colon.o command.o common.o declare.o echo.o enable.o eval.o evalfile.o evalstring.o exec.o exit.o fc.o fg_bg.o hash.o help.o history.o jobs.o kill.o let.o mapfile.o pushd.o read.o return.o set.o setattr.o shift.o source.o suspend.o test.o times.o trap.o type.o ulimit.o umask.o wait.o getopts.o shopt.o printf.o getopt.o bashgetopt.o complete.o
[  108s] ar: builtins.o: plugin needed to handle lto object

Thanks,
Martin

  reply	other threads:[~2020-09-21 11:33 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
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 [this message]
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=c2b236bd-cf9e-04de-b224-e6ee1cf09995@suse.cz \
    --to=mliska@suse.cz \
    --cc=10walls@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=richard.guenther@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).