Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.msdos.programmer > #1086 > unrolled thread
| Started by | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| First post | 2013-12-01 08:15 -0800 |
| Last post | 2015-09-06 15:55 -0700 |
| Articles | 20 on this page of 85 — 5 participants |
Back to article view | Back to comp.os.msdos.programmer
Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-01 08:15 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-01 18:42 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-01 19:14 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-02 11:13 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-02 03:21 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-03 06:21 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-02 23:17 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-03 13:31 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-03 06:05 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-03 10:47 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-03 21:18 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-03 12:23 -0500
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-03 16:26 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-03 23:58 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-04 04:31 -0500
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-04 05:01 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-04 02:20 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-05 06:33 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-05 21:37 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-06 12:19 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-06 22:23 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-07 13:48 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-07 16:34 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-08 02:12 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-13 03:32 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-15 04:47 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-15 02:14 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-15 13:21 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-04 23:39 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-05 06:38 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-05 21:40 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-06 04:19 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-06 13:40 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-14 21:07 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-03 22:22 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-04 04:30 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-04 23:21 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-05 04:23 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-05 21:31 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-10 04:59 +0000
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-10 06:17 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-11 02:36 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-11 13:44 +0000
Re: Smaller C compiler Harry Potter <rose.joseph12@yahoo.com> - 2013-12-10 10:41 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-11 03:06 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-11 10:47 -0500
Re: Smaller C compiler Harry Potter <rose.joseph12@yahoo.com> - 2013-12-11 08:01 -0800
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-11 13:40 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-11 22:07 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-25 02:33 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-29 03:24 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-21 15:55 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-29 17:16 +0000
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2013-12-29 21:54 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-29 19:38 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-29 19:36 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2013-12-30 05:07 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2013-12-29 21:58 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-01-05 19:43 -0800
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2014-01-06 15:27 +0000
Re: Smaller C compiler "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> - 2014-01-06 19:51 -0500
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2014-01-07 04:27 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-01-06 21:52 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-02-16 22:57 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-02-25 00:17 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-03-01 21:31 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-03-10 01:46 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-04-20 20:19 -0700
Re: Smaller C compiler Harry Potter <rose.joseph12@yahoo.com> - 2014-04-23 11:20 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-04-23 11:41 -0700
Re: Smaller C compiler Harry Potter <rose.joseph12@yahoo.com> - 2014-04-25 06:08 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-09-14 03:06 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-11-09 03:26 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-11-28 04:06 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2014-12-21 01:56 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-01-10 10:37 -0800
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-04-19 23:55 -0700
Re: Smaller C compiler "Auric__" <not.my.real@email.address> - 2015-04-22 06:13 +0000
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-04-22 00:12 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-04-25 21:11 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-05-16 17:49 -0700
Re: Smaller C compiler "Bill Buckels" <bbuckels@mts.net> - 2015-05-19 20:01 -0500
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-05-19 18:18 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-08-15 02:13 -0700
Re: Smaller C compiler "Alexei A. Frounze" <alexfrunews@gmail.com> - 2015-09-06 15:55 -0700
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
| From | "Rod Pemberton" <dont_use_email@xnohavenotit.cnm> |
|---|---|
| Date | 2014-01-06 19:51 -0500 |
| Message-ID | <op.w9aknrei5zc71u@localhost> |
| In reply to | #1244 |
On Mon, 06 Jan 2014 10:27:28 -0500, Auric__ <not.my.real@email.address> wrote: > Alexei A. Frounze wrote: >> I'll probably support the same compilation scheme for Linux as well. >> I think ELF isn't as bad as PE (at least, when you can invoke syscalls >> without importing anything from DLLs). > > IIRC, the MZ stub isn't really necessary. You can start the PE header at > 0x00 as long as you point 0x3C there (which would set "stack commit size" > = 0). Uh, do you mean the MZ stub isn't needed with Windows? ... AFAIK, DOS doesn't recognize PE. Rod Pemberton
[toc] | [prev] | [next] | [standalone]
| From | "Auric__" <not.my.real@email.address> |
|---|---|
| Date | 2014-01-07 04:27 +0000 |
| Message-ID | <XnsA2ADDA597BDC6auricauricauricauric@78.46.70.116> |
| In reply to | #1245 |
Rod Pemberton wrote: > On Mon, 06 Jan 2014 10:27:28 -0500, Auric__ <not.my.real@email.address> > wrote: >> Alexei A. Frounze wrote: > >>> I'll probably support the same compilation scheme for Linux as well. >>> I think ELF isn't as bad as PE (at least, when you can invoke syscalls >>> without importing anything from DLLs). >> >> IIRC, the MZ stub isn't really necessary. You can start the PE header at >> 0x00 as long as you point 0x3C there (which would set "stack commit size" >> = 0). > > Uh, do you mean the MZ stub isn't needed with Windows? ... Sorry, yes, exactly. I *know* the MZ stub can be left out of OS/2 LXs (but usually isn't); I *believe* the same holds true for PE, and possibly NE & LE.) > AFAIK, DOS doesn't recognize PE. It doesn't, not directly -- but it looks like DOS/4G supports PE (along with NE, LE, & LX). Possibly other extenders do as well. (Of course, since I know absolutely *nothing* about any extenders of any kind, I can't say for sure.) I'm sure there's plenty of discussion on this topic in the Google archives of this group dating back to the early 90's. -- Yeah, that's what we need, elitism and hubris.
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-01-06 21:52 -0800 |
| Message-ID | <lag4og$2js$1@speranza.aioe.org> |
| In reply to | #1246 |
On Monday, January 6, 2014 8:27:51 PM UTC-8, Auric__ wrote: > Rod Pemberton wrote: > > > On Mon, 06 Jan 2014 10:27:28 -0500, Auric__ <not.my.real@email.address> > > wrote: > >> Alexei A. Frounze wrote: > > > >>> I'll probably support the same compilation scheme for Linux as well. > >>> I think ELF isn't as bad as PE (at least, when you can invoke syscalls > >>> without importing anything from DLLs). > >> > >> IIRC, the MZ stub isn't really necessary. You can start the PE header > >> at > >> 0x00 as long as you point 0x3C there (which would set "stack commit > >> size" > >> = 0). > > > > Uh, do you mean the MZ stub isn't needed with Windows? ... > > Sorry, yes, exactly. I *know* the MZ stub can be left out of OS/2 LXs (but > usually isn't); I *believe* the same holds true for PE, and possibly NE & > LE.) > > > AFAIK, DOS doesn't recognize PE. > > It doesn't, not directly -- but it looks like DOS/4G supports PE (along > with > NE, LE, & LX). Possibly other extenders do as well. (Of course, since I > know > absolutely *nothing* about any extenders of any kind, I can't say for > sure.) > > I'm sure there's plenty of discussion on this topic in the Google archives > of this group dating back to the early 90's. Just because you can do something, it doesn't mean you should. :) I deliberately chose not to omit the MZ stub. And it doesn't cost you much. Compare the 128 bytes of the stub with the 128 kilobytes of the whole thing. It's 0.1%. And it wasn't hard to code either, everything had already been done. Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-02-16 22:57 -0800 |
| Message-ID | <ef0e875f-7277-4084-8b3e-82e63307670f@googlegroups.com> |
| In reply to | #1243 |
Basic support for struct/union has just been submitted.
You can do everything with struct and union, except:
- bit-fields, flexible array members
- tight packing (members are naturally aligned)
- passing/returning to/from functions by value; pass/return by reference instead
- initializing at definition time via = { initializer(s) }
Assignment, ?:, ->, ., (unsigned)&((struct someTag*)0)->someMember are OK.
Enjoy. Please report bugs.
Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-02-25 00:17 -0800 |
| Message-ID | <bbe82bdb-f616-4b81-8a1a-60257d227c2d@googlegroups.com> |
| In reply to | #1279 |
On Sunday, February 16, 2014 10:57:22 PM UTC-8, Alexei A. Frounze wrote:
> Basic support for struct/union has just been submitted.
>
> You can do everything with struct and union, except:
> - bit-fields, flexible array members
> - tight packing (members are naturally aligned)
> - passing/returning to/from functions by value; pass/return by reference instead
> - initializing at definition time via = { initializer(s) }
>
> Assignment, ?:, ->, ., (unsigned)&((struct someTag*)0)->someMember are OK.
>
> Enjoy. Please report bugs.
New things:
- short
- long (32-bit and huge mode(l)s only)
- improved extern (now extern directives are generated for NASM automatically as needed, not based on whether or not you use extern in C)
- one bug fixed
Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-03-01 21:31 -0800 |
| Message-ID | <51dcb65d-4439-4e86-9009-102285612b2e@googlegroups.com> |
| In reply to | #1286 |
New things: - typedef - __func__ - bugfixes
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-03-10 01:46 -0700 |
| Message-ID | <e25aba82-7123-4112-86bf-8d8383c29f90@googlegroups.com> |
| In reply to | #1292 |
New things: - enum - #pragma pack() - bugfix
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-04-20 20:19 -0700 |
| Message-ID | <9f0592bb-6f15-493f-a944-9e0ed09f98a9@googlegroups.com> |
| In reply to | #1295 |
Improvements/New things: - bugfixes - support initialization of multidimensional arrays - support initialization of structures - support initialization of structures and arrays inside functions - support static inside functions The compiler should now be much more usable.
[toc] | [prev] | [next] | [standalone]
| From | Harry Potter <rose.joseph12@yahoo.com> |
|---|---|
| Date | 2014-04-23 11:20 -0700 |
| Message-ID | <d0a76b4b-2dd4-4705-889e-0b221eb6fafb@googlegroups.com> |
| In reply to | #1336 |
Where is Smaller C available? I'm wondering if I could use it for DOS programming.
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-04-23 11:41 -0700 |
| Message-ID | <d791da47-72d9-4466-bacc-e2b6f561debc@googlegroups.com> |
| In reply to | #1337 |
On Wednesday, April 23, 2014 11:20:41 AM UTC-7, Harry Potter wrote: > Where is Smaller C available? I'm wondering if I could use it for DOS programming. Google wouldn't tell you anything different, but here you are: http://github.com/alexfru/SmallerC
[toc] | [prev] | [next] | [standalone]
| From | Harry Potter <rose.joseph12@yahoo.com> |
|---|---|
| Date | 2014-04-25 06:08 -0700 |
| Message-ID | <39b90bde-40f1-4c8a-ba93-c687923ec21f@googlegroups.com> |
| In reply to | #1338 |
On Wednesday, April 23, 2014 2:41:23 PM UTC-4, Alexei A. Frounze wrote: > On Wednesday, April 23, 2014 11:20:41 AM UTC-7, Harry Potter wrote: > > > Where is Smaller C available? I'm wondering if I could use it for DOS programming. > > Google wouldn't tell you anything different, but here you are: > http://github.com/alexfru/SmallerC Thank you!
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-09-14 03:06 -0700 |
| Message-ID | <0de5fb90-8e2e-4960-8757-10e01670d269@googlegroups.com> |
| In reply to | #1336 |
I've uploaded binaries for DOS and most of the standard library.
Note: a few things are still missing from the library, most notably: <time.h> functionality, *scanf() functions.
Everyone's welcome to play with the compiler and report bugs.
How to install the .zip file downloaded from https://github.com/alexfru/SmallerC:
1. Create C:\SMLRC (any hard disk or name will do, but make the full path as short as possible) and copy into it the following subdirectories of the .zip file:
BIND
INCLUDE
LIB
TESTS
2. Include C:\SMLRC\BIND in the environment variable PATH
3. Don't forget to have NASM (2.10 is good) installed and also available via PATH
You should now be able to compile the following example from TESTS\hw.c:
/*
How to compile for DOS (all mode(l)s: tiny/.COM, small/.EXE, huge/.EXE):
smlrcc -dost hw.c -o hwdt.com
smlrcc -doss hw.c -o hwds.exe
smlrcc -dosh hw.c -o hwdh.exe
*/
#include <stdio.h>
int main(void)
{
puts("Hello, World!");
return 0;
}
I suggest to stick to the huge memory mode(l) as it supports 32-bit types such as long the functions that consume or return these types. In this mode(l) you can allocate all the available conventional memory via malloc() and you're not limited to objects smaller than 64KB.
The huge memory mode(l) is selected with the "-dosh" option, but you don't need to specify it explicitly when using a DOS version of smlrcc.
What else to know?
smlrcc can consume one or more of .c, .asm, .o or .a files and make an executable out of them.
If the command line is too long (over some 120 characters), you can put it into a file, say, mycmd.txt, and invoke smlrcc with @mycmd.txt (note the @ prefix) and it will extract the command line parameters from the file mycmd.txt. The linker (smlrl) supports this as well.
smlrcc supports the following useful options:
-c (compile only, don't link)
-S (compile to assembly only)
-v (verbose; show executed commands)
-map <mapfile> (produce the map file together with the binary)
You can compile your .c/.asm/.o files directly to a .a library file if you invoke smlrcc like so:
smlrcc [options] <file(s)> -c -o mylib.a
There's more but the documentation hasn't been updated for a while and so here I'm giving the most basic info only.
Enjoy.
Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-11-09 03:26 -0800 |
| Message-ID | <5d3e2ad4-488d-4f0f-89c2-adc877c83eb0@googlegroups.com> |
| In reply to | #1553 |
I've just added support for Windows as both a host and a target platform. This means that there are now executables and libraries for both DOS and Windows and you can develop on either platform for either platform. The standard C library is practically complete (up to what the compiler supports in terms of the C language) and should be usable. There have been some other changes and improvements in the meantime. Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-11-28 04:06 -0800 |
| Message-ID | <c5742978-7677-4c15-88a5-84e20c789883@googlegroups.com> |
| In reply to | #1606 |
I've updated the documentation: https://github.com/alexfru/SmallerC/wiki Thanks, Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2014-12-21 01:56 -0800 |
| Message-ID | <407058ab-448e-4fe6-8926-f8c18f3a3ced@googlegroups.com> |
| In reply to | #1652 |
I've added Linux support (library and binaries). So, finally, all 3 platforms (DOS, Windows and Linux) are the host and the target platforms. Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2015-01-10 10:37 -0800 |
| Message-ID | <98334f0a-c5ae-438c-abb7-72ddaaddfc03@googlegroups.com> |
| In reply to | #1741 |
I've added an option (-ppg) to smlrcc to invoke gcc as a preprocessor and included the va_* macros in stdarg.h. This should help until there's a decent preprocessor in Smaller C. Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2015-04-19 23:55 -0700 |
| Message-ID | <e5957353-90ae-47e0-b733-9389aa046c58@googlegroups.com> |
| In reply to | #1779 |
For those interested, it's now possible to pass and return structures by value (x86 only, though). Alex
[toc] | [prev] | [next] | [standalone]
| From | "Auric__" <not.my.real@email.address> |
|---|---|
| Date | 2015-04-22 06:13 +0000 |
| Message-ID | <XnsA483EC7D7B943auricauricauricauric@213.239.209.88> |
| In reply to | #1871 |
Alexei A. Frounze wrote: > For those interested, it's now possible to pass and return structures by > value (x86 only, though). > Alex Not that this has any bearing on that, but I thought you'd like to know that at least one person here is paying attention and downloading SmallerC. -- You broke those braincells, you pay for them.
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2015-04-22 00:12 -0700 |
| Message-ID | <a864381a-f15c-482b-9ceb-acba3d265be3@googlegroups.com> |
| In reply to | #1872 |
On Tuesday, April 21, 2015 at 11:14:50 PM UTC-7, Auric__ wrote: > Alexei A. Frounze wrote: > > > For those interested, it's now possible to pass and return structures by > > value (x86 only, though). > > Alex > > Not that this has any bearing on that, but I thought you'd like to know that > at least one person here is paying attention and downloading SmallerC. Thanks! :) Alex
[toc] | [prev] | [next] | [standalone]
| From | "Alexei A. Frounze" <alexfrunews@gmail.com> |
|---|---|
| Date | 2015-04-25 21:11 -0700 |
| Message-ID | <57f228e7-8c98-4e76-8cf5-87801ffa2ae3@googlegroups.com> |
| In reply to | #1871 |
A few important bugfixes are uploaded. Alex
[toc] | [prev] | [next] | [standalone]
Page 4 of 5 — ← Prev page 1 2 3 [4] 5 Next page →
Back to top | Article view | comp.os.msdos.programmer
csiph-web