Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Keith Thompson Newsgroups: comp.lang.c Subject: Re: More problems with lcc-win Date: Wed, 15 Mar 2017 08:24:44 -0700 Organization: None to speak of Lines: 22 Message-ID: References: <20d9275b-7502-4ad0-b343-5cecf8c6ea90@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: mx02.eternal-september.org; posting-host="1d05d6df43238c69e85c0f471787c307"; logging-data="15294"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19COeYK4Bxy18E4D7uXnIT4" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:7Kj7aqYnHcR9+EJcGjDOXNoygaI= sha1:+c4M4Lcajl7GHmsBDVUGdujWtFc= Xref: csiph.com comp.lang.c:106134 mertesthomas@gmail.com writes: > I looked at the lcc-win32 source of fseeki64 (provided by Jacob > Navia) and it seems ok. At least it does not look like returning an > argument (like I can see in my tests). I looked also at the C > run-time library of lcc-win32. The disassembled code there seems to > correspond with the provided source code. Still I have problems > with fseeki64 even after a fresh install of lcc-win32. Maybe it is > an issue with the calling convention. I narrowed the problem of > fseeki64 down and it is part of the program testlcc_4.c (see below). > Could someone else also try testlcc_4.c with the 32-bit version of > lcc-win32? [snip] If you want to discuss problems with lcc-win, as opposed to the C language, I suggest that either comp.compilers.lcc or jacob's support channels would be a better place than comp.lang.c. -- 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"