Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: Unexpected and difficult to understand SIGSEGV Date: Tue, 29 Sep 2015 18:14:49 -0700 Organization: None to speak of Lines: 20 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="945944de09706c9b4e29b53c9d2efdc2"; logging-data="17072"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/fVrqkSfN1Jir1dbhi/VFX" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:0qeNW8e3atm/VxVBZ6eVH20DWdQ= sha1:cehJTdMKSkLiISF2r9ACW2TmWxU= Xref: csiph.com comp.lang.c:71459 "Morten W. Petersen" writes: [...] > To see the entire development cycle, first is getting things to > work correctly and making the code well-designed (and implied > in that, easy to read and understand). And secure. > > The comes speed optimizations, on the C-level, compiler settings, > profiling and so on. > > When all higher-level or reasonable approaches are exhausted, then > Assembly-level programming can begin. [...] And that last step is rarely necessary. -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for JetHead Development, Inc. "We must do something. This is something. Therefore, we must do this." -- Antony Jay and Jonathan Lynn, "Yes Minister"