Menu

Code Commit Log


Commit Date  
[r214] by obarthel

- Fixed the constructor/destructor invocation sequence for the SAS/C and
GCC 68k library builds.

2005-03-20 12:14:09 Tree
[r213] by obarthel

- Modified the SAS/C constructor/destructor invocation sequence, now that
the names of the functions assigned through the new macros are different.

2005-03-20 11:57:11 Tree
[r212] by obarthel

- Turns out that the constructor/destructor calling sequence
was still wrongish for the OS4 library. So I had to change
it *again*. Which probably means that the 68k library will
need further changes...

2005-03-20 11:18:06 Tree
[r211] by obarthel

- assertion failures early on during program initialization
should no longer spell big trouble on account of the stdio
data structures possibly not being in a well-defined and
initialized state.

2005-03-19 11:06:57 Tree
[r210] by obarthel

- Moved the call chain printing out of stdlib_main.c and into
separate files.

- Removed some more redundant data from stdlib_main.c.

- Added the first real C99 function: _Exit().

2005-03-19 10:15:56 Tree
[r209] by obarthel

- Reorganized the local header files, removing redundancies.

- Dropped unused stub code which is now redundant because of
the constructor/destructor mechanism.

2005-03-18 12:38:25 Tree
[r208] by obarthel

- fcntl() did not work for sockets. Fixed.

2005-03-16 09:28:37 Tree
[r207] by obarthel

- Re-added the long word alignment check for MC68020 I didn't commit
at home.

2005-03-15 11:18:32 Tree
[r206] by obarthel

- ftruncate() ended up changing the current file position, contrary
to what it is supposed to do. Fixed.

2005-03-14 10:03:06 Tree
[r205] by obarthel

- Turns out that the 68k GCC port does not sort constructor and
destructor functions in any way at all. I reimplemented the
entire library constructor/destructor functionality to use the
same approach as libnix.

2005-03-12 14:10:09 Tree
Older >
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.