luke
/
iverilog
mirror of https://github.com/steveicarus/iverilog.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
iverilog/vvp/vvp_cleanup.h

57 lines
2.2 KiB
C
Raw Normal View History

More end of simulation memory cleanup. This patch adds some more memory freeing routines to vvp and the vpi library. Much more to do before this is finished.
2009-01-24 01:04:44 +01:00
#ifndef __vvp_cleanup_H
#define __vvp_cleanup_H
/*
* Copyright (c) 2009 Cary R. (cygcary@yahoo.com)
*
* This source code is free software; you can redistribute it
* and/or modify it in source code form under the terms of the GNU
* General Public License as published by the Free Software
* Foundation; either version 2 of the License, or (at your option)
* any later version.
*
* This program is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU General Public License for more details.
*
* You should have received a copy of the GNU General Public License
* along with this program; if not, write to the Free Software
* Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA
*/
# include "pointers.h"
# include "vpi_priv.h"
# include "vvp_net.h"
/* Routines used to cleanup the runtime memory when it is all finished. */
Add memory freeing and pool management for valgrind. This patch adds code to free most of the memory when vvp finishes. It also adds valgrind hooks to manage the various memory pools. The functionality is enabled by passing --with-valgrind to configure. It requires that the valgrind/memcheck.h header from a recent version of valgrind be available. It check for the existence of this file, but not that it is new enough (version 3.1.3 is known to not work and version 3.4.0 is known to work). You can still use valgrind when this option is not given, but you will have memory that is not released and the memory pools show as a single block. With this vvp is 100% clean for many of the tests in the test suite. There are still a few things that need to be cleaned up, but it should be much easier to find any real leaks now. Enabling this causes a negligible increase in run time and memory. The memory could be a problem for very large simulations. The increase in run time is only noticeable on very short simulations where it should not matter.
2009-01-30 02:23:09 +01:00
extern void codespace_delete(void);
Add island EOS cleanup code This cleans up most of the memory allocated when building and island and the branches that connect to it.
2009-02-07 03:05:12 +01:00
extern void dec_str_delete(void);
More end of simulation memory cleanup. This patch adds some more memory freeing routines to vvp and the vpi library. Much more to do before this is finished.
2009-01-24 01:04:44 +01:00
extern void def_table_delete(void);
Add island EOS cleanup code This cleans up most of the memory allocated when building and island and the branches that connect to it.
2009-02-07 03:05:12 +01:00
extern void island_delete(void);
More end of simulation memory cleanup. This patch adds some more memory freeing routines to vvp and the vpi library. Much more to do before this is finished.
2009-01-24 01:04:44 +01:00
extern void vpi_mcd_delete(void);
extern void load_module_delete(void);
Add memory freeing and pool management for valgrind. This patch adds code to free most of the memory when vvp finishes. It also adds valgrind hooks to manage the various memory pools. The functionality is enabled by passing --with-valgrind to configure. It requires that the valgrind/memcheck.h header from a recent version of valgrind be available. It check for the existence of this file, but not that it is new enough (version 3.1.3 is known to not work and version 3.4.0 is known to work). You can still use valgrind when this option is not given, but you will have memory that is not released and the memory pools show as a single block. With this vvp is 100% clean for many of the tests in the test suite. There are still a few things that need to be cleaned up, but it should be much easier to find any real leaks now. Enabling this causes a negligible increase in run time and memory. The memory could be a problem for very large simulations. The increase in run time is only noticeable on very short simulations where it should not matter.
2009-01-30 02:23:09 +01:00
extern void modpath_delete(void);
Add island EOS cleanup code This cleans up most of the memory allocated when building and island and the branches that connect to it.
2009-02-07 03:05:12 +01:00
extern void root_table_delete(void);
Add memory freeing and pool management for valgrind. This patch adds code to free most of the memory when vvp finishes. It also adds valgrind hooks to manage the various memory pools. The functionality is enabled by passing --with-valgrind to configure. It requires that the valgrind/memcheck.h header from a recent version of valgrind be available. It check for the existence of this file, but not that it is new enough (version 3.1.3 is known to not work and version 3.4.0 is known to work). You can still use valgrind when this option is not given, but you will have memory that is not released and the memory pools show as a single block. With this vvp is 100% clean for many of the tests in the test suite. There are still a few things that need to be cleaned up, but it should be much easier to find any real leaks now. Enabling this causes a negligible increase in run time and memory. The memory could be a problem for very large simulations. The increase in run time is only noticeable on very short simulations where it should not matter.
2009-01-30 02:23:09 +01:00
extern void signal_pool_delete(void);
extern void udp_defns_delete(void);
extern void vpi_handle_delete(void);
extern void vvp_net_pool_delete(void);
extern void A_delete(struct __vpiHandle *item);
extern void PV_delete(struct __vpiHandle *item);
extern void constant_delete(struct __vpiHandle *item);
extern void contexts_delete(struct __vpiScope *scope);
extern void memory_delete(struct __vpiHandle *item);
extern void named_event_delete(struct __vpiHandle *item);
extern void parameter_delete(struct __vpiHandle *item);
extern void signal_delete(struct __vpiHandle *item);
More vvp EOS memory cleanup. This patch cleans up callbacks for arrays, named events and real variables. It also cleans up the decimal index constants for net array words.
2009-01-31 03:36:07 +01:00
extern void real_delete(struct __vpiHandle *item);
Add memory freeing and pool management for valgrind. This patch adds code to free most of the memory when vvp finishes. It also adds valgrind hooks to manage the various memory pools. The functionality is enabled by passing --with-valgrind to configure. It requires that the valgrind/memcheck.h header from a recent version of valgrind be available. It check for the existence of this file, but not that it is new enough (version 3.1.3 is known to not work and version 3.4.0 is known to work). You can still use valgrind when this option is not given, but you will have memory that is not released and the memory pools show as a single block. With this vvp is 100% clean for many of the tests in the test suite. There are still a few things that need to be cleaned up, but it should be much easier to find any real leaks now. Enabling this causes a negligible increase in run time and memory. The memory could be a problem for very large simulations. The increase in run time is only noticeable on very short simulations where it should not matter.
2009-01-30 02:23:09 +01:00
extern void thread_vthr_delete(struct __vpiHandle *item);
extern void thread_word_delete(struct __vpiHandle *item);
extern void vpi_call_delete(struct __vpiHandle *item);
extern void vthreads_delete(vthread_t base);
extern void vvp_net_delete(vvp_net_t *item);
More end of simulation memory cleanup. This patch adds some more memory freeing routines to vvp and the vpi library. Much more to do before this is finished.
2009-01-24 01:04:44 +01:00
#endif