Re: Want to be a gcc/binutils maintainer?

[Danny Smith <danny_r_smith_2001 at yahoo dot co dot nz>]

 --- Charles Wilson <cwilson@ece.gatech.edu> wrote: > Danny Smith wrote:
> 
> > Egor, I think we do need something like that.  I have just uploaded a
> beta
> > (binaries, src, and diffs) of mingw gcc with fastcall support for mingw
> at
> > SF file release site.
> >
>
https://sourceforge.net/project/showfiles.php?group_id=2435&release_id=60167
> > It is for 2.95.3 but the changes have also been tested successfully on
> gcc
> > trunk (and 3.0.2) with mingw bootstrap. My problem has been trying to
> make
> > the diffs public within the w32 crowd and getting some feedback before
> > going to gcc-patches.
> > 
> 
> Question, Danny:  with your changes, does auto-import continue to work?
Yes, in all my tests.

> (with *non* fastcall symbols only, for now...auto-import-for-fastcall
> probably needs to be added later, but for now...)
> 

fastcall symbols are functions, never data, so no need to auto-import. 
However, all the _nm_ symbols seem to be okay.


> Download this:
> 
> 
>
http://www.neuro.gatech.edu/users/cwilson/cygutils/V1.1/dll-stuff/dll-helpers-0.2.9.tar.bz2
> 
> and run the various tests.
> 
> 
I get broken link messages with that.  I'll try later. FWIW,
dllhelpers-0.2.4-0.2.8 all work before and after changing functions to
__fastcall (and with __fastcall C++ methods), and mixing __stdcall,
__cdecl, and __fastcall in same code.    I don't know how to mark fortran
names as fastcall.

--Chuck 


http://briefcase.yahoo.com.au - Yahoo! Briefcase
- Manage your files online.