Re: patch trunk: seek plugin also in a language specific directory when given a short name

2011-06-06 Thread Jonathan Wakely
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-fil

patch trunk: seek plugin also in a language specific directory when given a short name

2011-06-05 Thread Basile Starynkevitch
Hello All, Front-end functions (e.g. pragma-related) are not available to all plugins (e.g. not to plugins fired from lto1). See the http://gcc.gnu.org/ml/gcc/2011-05/msg00321.html discussion. This patch document a little bit that, and search short plugins like -fplugin=name in both `gcc -print-