diff options
| author | Alan Modra <amodra@gmail.com> | 2020-06-06 11:28:08 +0930 |
|---|---|---|
| committer | Alan Modra <amodra@gmail.com> | 2020-06-06 11:28:08 +0930 |
| commit | 070558eb0deed3fc798c41ec75db75f99660a4e1 (patch) | |
| tree | 6df538d3d8258fe7d178ede7962f9c6ae8461d57 /ld/testsuite/lib | |
| parent | 62b5b3d836853730d40c5cc89015f831baf3131c (diff) | |
| download | gdb-070558eb0deed3fc798c41ec75db75f99660a4e1.zip gdb-070558eb0deed3fc798c41ec75db75f99660a4e1.tar.gz gdb-070558eb0deed3fc798c41ec75db75f99660a4e1.tar.bz2 | |
ld -plugin options when plugins are disabled
This patch makes ld accept and ignore -plugin options when configured
with --disable-plugins. The idea is to allow using a linker built
without plugin support with a gcc built with plugin support. Quite
obviously such a combination won't work if using LTO, but gcc has a
habit of passing a bunch of -plugin and -plugin-opt arguments to ld
even when not generating or linking LTO objects.
Why do I want to do this? Well, it lets me and other binutils
developers answer the question as to whether plugin support breaks
binutils in some areas. Which it does for some targets.
* lexsup.c (ld_options): Accept -plugin and -plugin-opt when
!ENABLE_PLUGINS.
* testsuite/lib/ld-lib.exp (check_plugin_api_available): Adjust.
Diffstat (limited to 'ld/testsuite/lib')
| -rw-r--r-- | ld/testsuite/lib/ld-lib.exp | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/ld/testsuite/lib/ld-lib.exp b/ld/testsuite/lib/ld-lib.exp index 015eda6..6535881 100644 --- a/ld/testsuite/lib/ld-lib.exp +++ b/ld/testsuite/lib/ld-lib.exp @@ -1135,7 +1135,8 @@ proc check_plugin_api_available { } { if {![info exists plugin_api_available_saved]} { # Check if the ld used by gcc supports --plugin. set ld_output [remote_exec host $ld "--help"] - if { [ string first "-plugin PLUGIN" $ld_output ] >= 0 } { + if { [regexp -- "-plugin PLUGIN \[^\n\r\]*" $ld_output line] + && ![regexp "ignored" $line] } { set plugin_api_available_saved 1 } else { set plugin_api_available_saved 0 |