Jump to content

Wildcard in irun command line


nguthrie
 Share

Recommended Posts

I am trying to change the verbosity of one of my agents from the command line using the +uvm_set_verbosity option.  The examples in the UVM user guide show this:

+uvm_set_verbosity=uvm_test_top.env.agent1.*,_ALL_,UVM_FULL

When I add this to the irun command I get an error:


irun: No match.


I found that I needed to escape the * with a \ to make this work

+uvm_set_verbosity=uvm_test_top.env.agent1.\*,_ALL_,UVM_FULL

 

Is this a bug in irun?  Or do all simulators have an issue with wildcards and therefore this is a UVM documentation issue?

Edited by nguthrie
Link to comment
Share on other sites

hi,

 

that is a simple shell issue. the shell will expand the meta characters such as *,? ...  and pass the expanded result to the tool. the backslash simply tells the shell to avoid any expansion. unfortunately what is being expanded is shell dependent. you may work around with the following

 

- prefix with backslash

- put the whole argument into quotes '

- put the  argument subject to shell expansion into a .f file and -f include the file

 

/uwe

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...