Experimental Physics and
Industrial Control System

Hi Mark
> I don’t know for what version of gcc or Linux I was using when I
> built it in 2013.  Is there a way to determine that?  Any idea what
> could cause this?
The following works for me:

$ strings -a /usr/lib/epics/lib/linux-x86_64-debug/libCom.so|grep 'GCC: ('
GCC: (Debian 8.3.0-6) 8.3.0

Note that this only works with an unstripped library.

Determining the compiler flags that were used however will be very
difficult. AFAIK ELF doesn't contain any information about compiler
version, compiler flags used etc.

Are the slower versions compiled with -O3?

Martin

-- 
Martin Konrad
Facility for Rare Isotope Beams
Michigan State University
640 South Shaw Lane
East Lansing, MI 48824-1321, USA
Tel. 517-908-7253
Email: konrad at frib.msu.edu

Navigate by Date:

Prev: EPICS shared library performance Mark Rivers via Core-talk

Next: Re: EPICS shared library performance Michael Davidsaver via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024 

Navigate by Thread:

Prev: Re: EPICS shared library performance Konrad, Martin via Core-talk

Next: Build failed: EPICS Base 7 base-7.0-41 AppVeyor via Core-talk

Index: 2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  <2020>  2021  2022  2023  2024