This is the mail archive of the cygwin-developers@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

-fno-rtti


Is there any strong reason currently to use the -fno-rtti flag in
building the cygwin DLL?  AFAICT from the archives, the reasons
have been to do with executable size.  From a quick test, it seems
to make no more than a small difference in the size of the DLL
(less than 1%) and doesn't seem to change the run-time size of
objects (tho' this wasn't a very scientific test).  Also, the DLL
seems to work fine when compiled with rtti.

The main reason for asking (other than my usual simple minded
curiosity) is that I would like to use dynamic_cast in some
cygserver code I'm writing.  If the decision is to keep
the -fno-rtti flag for the DLL, I can build the objects for the
cygserver executable with rtti (which I'm assuming wouldn't be a
problem), but given the intertwining of the code base, it might be
"cleaner" to compile it all up with the same set of flags.

// Conrad




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]