<feed xmlns='http://www.w3.org/2005/Atom'>
<title>llvm-project.git/clang/test/Driver/plugin-driver-args.cpp, branch main</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/'/>
<entry>
<title>[driver][test] Only check for unused plugin options (#91522)</title>
<updated>2024-05-09T13:53:57+00:00</updated>
<author>
<name>Jake Egan</name>
<email>Jake.egan@ibm.com</email>
</author>
<published>2024-05-09T13:53:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=4ad3de901e8acfafdeb59406064f24a3c2ea27e8'/>
<id>4ad3de901e8acfafdeb59406064f24a3c2ea27e8</id>
<content type='text'>
This fixes matching `clang: error: argument unused during compilation:
'-Werror' [-Werror,-Wunused-command-line-argument]` on AIX.

---------

Co-authored-by: Hubert Tong &lt;hubert-reinterpretcast@users.noreply.github.com&gt;</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
This fixes matching `clang: error: argument unused during compilation:
'-Werror' [-Werror,-Wunused-command-line-argument]` on AIX.

---------

Co-authored-by: Hubert Tong &lt;hubert-reinterpretcast@users.noreply.github.com&gt;</pre>
</div>
</content>
</entry>
<entry>
<title>[driver] Do not warn about unused plugin flags. (#88948)</title>
<updated>2024-05-06T12:04:12+00:00</updated>
<author>
<name>Michael Kruse</name>
<email>llvm-project@meinersbur.de</email>
</author>
<published>2024-05-06T12:04:12+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=6e31a49931b8b057868a64e89838e3c9b40f9198'/>
<id>6e31a49931b8b057868a64e89838e3c9b40f9198</id>
<content type='text'>
Plugins are not loaded without the -cc1 phase. Do not report them when
running on an assembly file or when linking. Many build tools add these
options to all driver invocations, including LLVM's build system.

Fixes #88173</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Plugins are not loaded without the -cc1 phase. Do not report them when
running on an assembly file or when linking. Many build tools add these
options to all driver invocations, including LLVM's build system.

Fixes #88173</pre>
</div>
</content>
</entry>
<entry>
<title>[clang][driver] Add -fplugin-arg- to pass arguments to plugins</title>
<updated>2021-11-25T09:47:55+00:00</updated>
<author>
<name>Timm Bäder</name>
<email>tbaeder@redhat.com</email>
</author>
<published>2021-11-04T16:40:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.belthelziquor.com/llvm-project.git/commit/?id=3e67cf21a19a0e8917bdbab6f0cecd4880f3fbe2'/>
<id>3e67cf21a19a0e8917bdbab6f0cecd4880f3fbe2</id>
<content type='text'>
From GCC's manpage:
-fplugin-arg-name-key=value
   Define an argument called key with a value of value for the
   plugin called name.

Since we don't have a key-value pair similar to gcc's plugin_argument
struct, simply accept key=value here anyway and pass it along as-is to
plugins.

This translates to the already existing '-plugin-arg-pluginname arg'
that clang cc1 accepts.

There is an ambiguity here because in clang, both the plugin name
as well as the option name can contain dashes, so when e.g. passing

 -fplugin-arg-foo-bar-foo

it is not clear whether the plugin is foo-bar and the option is foo,
or the plugin is foo and the option is bar-foo. GCC solves this by
interpreting all dashes as part of the option name. So dashes can't be
part of the plugin name in this case.

Differential Revision: https://reviews.llvm.org/D113250
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
From GCC's manpage:
-fplugin-arg-name-key=value
   Define an argument called key with a value of value for the
   plugin called name.

Since we don't have a key-value pair similar to gcc's plugin_argument
struct, simply accept key=value here anyway and pass it along as-is to
plugins.

This translates to the already existing '-plugin-arg-pluginname arg'
that clang cc1 accepts.

There is an ambiguity here because in clang, both the plugin name
as well as the option name can contain dashes, so when e.g. passing

 -fplugin-arg-foo-bar-foo

it is not clear whether the plugin is foo-bar and the option is foo,
or the plugin is foo and the option is bar-foo. GCC solves this by
interpreting all dashes as part of the option name. So dashes can't be
part of the plugin name in this case.

Differential Revision: https://reviews.llvm.org/D113250
</pre>
</div>
</content>
</entry>
</feed>
