Subject: Re: [sv-cc] VPIs for changing the log file..
From: Raghuraman R (raghu@ti.com)
Date: Mon Apr 14 2003 - 20:38:46 PDT
Joao,
Thanks for the response.
So, there is no solution to change the log file midway during a
simulation. With whom should this issue be taken up? Should VPI be
enhanced or is it a problem of the simulator vendor and hence the issue
to be taken up with him only?
Thanks.
Joao Geada wrote:
> Raghuraman,
>
> as far as I am aware, VPI is currently forbidden to manipulate the log file in
> use by the simulator
> (this is implicitly described in IEEE 1364-2001, section 27.22, vpi_mcd_close)
>
> Specifically, there is an mcd channel describing the simulator log file, but
> vpi cannot modify that stream (ie cannot close the current stream and then
> reopen it to a different file)
>
> However, I believe you can get the name of the log file from vpi_mcd_name
> (use channel descriptor 1 to get the log file)
>
> Joao
> ==============================================================================
> Joao Geada, PhD Principal Engineer Verif Tech Group
> Synopsys, Inc TEL: (508) 263-8083
> 377 Simarano Drive, Suite 300, FAX: (508) 263-8069
> Marlboro, MA 01752, USA
> ==============================================================================
>
>
> -----Original Message-----
> From: owner-sv-cc@eda.org [mailto:owner-sv-cc@eda.org]On Behalf Of
> Raghuraman R
> Sent: Friday, April 11, 2003 4:24 AM
> To: sv-cc@eda.org
> Subject: [sv-cc] VPIs for changing the log file..
>
>
> Hi,
>
> I would like to know if there is any vpi call to change the logfile
> during simulation. I know of the vpi_mcd_* calls but it is for any
> user-specific displays.
>
> For example, if I am running a big simulation job running for 48 hours,
> then the log file that gets generated is a 16 GB file or so which cannot
> be edited or read easily. So if there is a vpi call to change the log
> file, it will be good for the users, who can look at the smaller log
> files. This is also needed when multiple vector files are simulated in
> one run and users would like to have one log for each file.
>
> The prototype could be
>
> int vpi_change_log("<file name>", mode (append|write));
>
> Similarly there should be a call to get the current log file name
>
> char * vpi_get_logfilename();
>
> Otherwise, logfile could be declared as an object which can be edited
> using the vpi_put_value and value obtained through vpi_get_value. The
> object type could be enumerated on the types of vpiBinStrVal etc.
-- Regds,Raghuraman R ASIC Texas Instruments (India) Ltd. Phone : +91-80-5099113 http://www.india.ti.com/~raghu
* Think. *
This archive was generated by hypermail 2b28 : Mon Apr 14 2003 - 20:40:07 PDT