On 6 June 2011 06:35, Basile Starynkevitch wrote:
+slashes). When simply passing @option{-fplugin=@var{name}}, the plugin
+is loaded from the @file{plugin} directory using if needed a front-end
+specific subdirectory, so @option{-fplugin=@var{name}} is the same as
+@option{-fplugin=`gcc -print-file-name=plugin`/@var{program}/@var{name}.so} or
+@option{-fplugin=`gcc -print-file-name=plugin`/@var{name}.so}, using
+backquote shell syntax to query the @file{plugin} directory, where
+@var{program} is one of @code{cc1}, @code{cc1plus}, @code{lto1} etc.
I found this hard to read, particularly "using if needed a front-end
specific subdirectory."
Maybe "is loaded from the plugin directory, or one of the front-end
specific subdirectories, so ..."
+This permits some plugins to be available only to some front-ends.
How about "This means some plugins are only available to some
front-ends" instead?
> * doc/plugins.texi (Loading plugins): Plugins are also
> seeked in a front-end specific subdirectory.
> (Plugin callbacks): lto1 plugins can't register pragma handlers.
"Seeked" is not English, the correct word would be "sought" but
"searched for" would also be OK.
> * plugin.c: Update copyright year.
> (PLUGIN_FILE_SUFFIX): New constant macro.
> (add_new_plugin): Search short plugins also in a front-end specific
> subdirectory.
I think this would be clearer as "Also search for short plugins in a ..."
