This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Testing a plugin optimization with 'make check' (slashes in options)
- From: Matthew Fortune <Matthew dot Fortune at imgtec dot com>
- To: Steve Ellcey <Steve dot Ellcey at imgtec dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 1 May 2013 20:53:28 +0000
- Subject: RE: Testing a plugin optimization with 'make check' (slashes in options)
- References: <166f2cb5-a063-4bca-a1ad-275e37f3ab4a at BAMAIL02 dot ba dot imgtec dot org>
Hi,
> I was wondering if someone would tell me how to pass an option that
> contains slashes into 'make check'?
>
> For example if I want to test a compiler using a simulator and the -O3 option
> I can run:
>
> make check RUNTESTFLAGS="--target_board='mips-sim-mti32/-O3'"
>
> I want to run this:
>
> make check RUNTESTFLAGS="--target_board='mips-sim-mti32/-
> fplugin=/home/sellcey/plugin/dynopt.so'"
Using a brace expansion may help here though I haven't checked. Forward slashes are for the first set of run variants and braces are for the second set. Given the separator for brace expansion is , then the forwards slashes would hopefully not matter. It's a bit of a guess though:
make check RUNTESTFLAGS="--target_board='mips-sim-mti32\{-fplugin=/home/sellcey/plugin/dynopt.so\}'"
Matthew
>
> But the slashes in the plugin path are messing things up (I tried putting 1, 2,
> or 3 backslashes in front of the forward slashes in the path but that did not
> help and I tried putting /home/sellcey/plugin/dynopt.so in single quotes,
> that did not help either.
>
> Steve Ellcey
> sellcey@imgtec.com