Hi there,
On Mon, Nov 13, 2000 at 17:37:50 -0500, Brandon D. Valentine wrote:
> Honestly there is not much that can be done about it.
True, unless you can point the gcc developers to that bug.
But the point is actually (IMHO): You need to do something about it,
and be it a workaround, otherwise segfaulting "w3m"s will appear in
Linux distributions.
> or dump. There's little point in compiling w3m with -O2 anyway. It
> just builds bigger binaries, and with an application this simple would
> you rather optimize a few cpu cycles or a few bytes of memory?
I've only had good experiences with optimizations -O2. With -O6 (newer
"egcs"s or "gcc"s), size indeed increases, and speed hardly noticable
only in few cases. I don't know about Linux by heart right now, but
the -O2 option doesn't really account for more size on Solaris. If
rendering speed is really not an issue in "w3m", perhaps optimizing
with "-Os" would be best. :)
Greetings,
Moritz.
This archive was generated by hypermail 2b29 : Tue Nov 14 2000 - 01:10:32 CST