Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: mergesort code segfaulting on smallish arrays Date: Sat, 09 Nov 2019 12:47:25 -0800 Organization: None to speak of Lines: 18 Message-ID: References: <87mud63p3b.fsf@bsb.me.uk> <%QBxF.59077$VR.21809@fx39.iad> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: reader02.eternal-september.org; posting-host="04d7f252c942ed664178d1ace563d1fb"; logging-data="26670"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX183QCB8QUiizrk3kdNF09NN" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:OeuQAVcszSd5B4FEUJQj3A0cgM8= sha1:ZIbCqvVieDDzxZ3p01K5rjpf8Uo= Xref: csiph.com comp.lang.c:147851 Richard Damon writes: > On 11/9/19 11:49 AM, Bonita Montero wrote: [...] >> There should be no compiler with an int larger than 32 bit. > > Yes, I currently know of none, which is why that assumption may be > acceptable, but it is possible. I've used machines with 64-bit short, int, long, and long long (Cray vector machines). char probably would have been 64 bits if there hasn't been a requirement for UNIX compatibility. [...] -- Keith Thompson (The_Other_Keith) kst-u@mib.org Working, but not speaking, for Philips Healthcare void Void(void) { Void(); } /* The recursive call of the void */