| 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 <2020> 2021 2022 2023 2024 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: profiling an IOC |
| From: | "Johnson, Andrew N. via Tech-talk" <tech-talk at aps.anl.gov> |
| To: | "D. Peter Siddons" <siddons at bnl.gov> |
| Cc: | EPICS tech-talk <tech-talk at aps.anl.gov> |
| Date: | Fri, 17 Jul 2020 20:44:33 +0000 |
|
Hi Pete,
On Jul 17, 2020, at 3:19 PM, Siddons, David via Tech-talk <tech-talk at aps.anl.gov> wrote:
I’ve never tried gprof myself, but I can answer the build question.
If you’re just profiling the code in a specific module you could add them to the USR_CFLAGS and/or USR_CXXFLAGS variables in a specific Makefile. However if you want them to apply to everything during a rebuild we have a set of similar variables that are
strictly for use from the command-line, so you would say something like
make rebuild CMD_CFLAGS=-pg CMD_CXXFLAGS=-pg These variables have been present since 3.14.12.5.
Note that if you use this when building Base you may be running profiling during the build process itself as we build and run the antelope and e_flex programs (our versions of lex and yacc) and makeBpt as part of the build. The other build-time tools are
all scripts though.
HTH,
- Andrew
--
Complexity comes for free, simplicity you have to work for.
|