Re: [PATCH v2] configure: Avoid eh_frame bloat in release builds
Lauri Kasanen <[email protected]>
| Newsgroups | gmane.comp.video.mplayer.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sat, 13 Feb 2016 16:53:17 +0100 Reimar Döffinger <[email protected]> wrote: > > -fno-async provides the majority of the size benefit indeed, the > > difference was just bytes. Attaching v2. > > I also suspect, as we are checking it to work anyway, that this > shouldn't be gnu only. > Seems reasonable to believe that other compilers might have the > same option. Google says clang supports the option, but I cannot test that. > > The few C++ files in mplayer and ffmpeg do not use exceptions > > (incidentally, -fno-exceptions and -fno-rtti should be added to > > CXXFLAGS, they have size impact as well). > > To my knowledge, -fno-rtti changes ABI, and those C++ files are > mostly there to use C++ library (which might use RTTI and exceptions, > to the exceptions thing might not matter). > So I don't believe these options are safe to add. Those options are quite safe when the code doesn't use the features. The C++ library's internals do not matter, it's made so that programs with and without rtti and exceptions work. If this were a C++ library instead of a program, then they wouldn't be safe to add, in case a user of the library used the features. - Lauri _______________________________________________ MPlayer-dev-eng mailing list [email protected] https://lists.mplayerhq.hu/mailman/listinfo/mplayer-dev-eng