[ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change, waste more stack space.

[Thomas Weidenmueller]

While you love to bash gcc just because it has it's flaws there's many
reasons so many projects use it, even commercial ones.
MSVC/Intel/Whatever isn't really free. The number of systems they target
is comperatively low and most importantly you rely on the vendor as no
sources are available. They may be better in certain areas but not in
all, and in some they're worse. All of them have bugs, not just gcc...
And the most important thing: There's no other compiler that allows you
to target that many different architectures as gcc.

Besides, adding a standard calling convention feature to gcc shouldn't
be that big of a deal... These things are done with symbol attributes,
maybe I'm going to work on something like that in the summer.

- Thomas

Alex Ionescu wrote:
> That's all great except that every other compiler on the planet lets you
> specify the default convention PER PROJECT. Are you saying that with GCC, I
> need to recompile the compiler for every single application I want to ship?
> Maybe I have a fastcall stub DLL, a stdcall program and a cdecl C compatible
> DLL. I need three compilers for that? That's rubbish.
> 
> Fortunately, gcc does support a flag, -mrtd. Oh, but guess what, it's been
> broken since 2.95.
> 
> -----Original Message-----
> From: ros-dev-bounces at reactos.org [mailto:ros-dev-bounces at reactos.org] On
> Behalf Of hto at mail.cnt.ru
> Sent: April-24-07 9:09 PM
> To: ReactOS Development List
> Subject: Re: [ros-dev] [ros-diffs] [dgorbachev] 26483: Undo r26482 change,
> waste more stack space.
> 
>> stdcall default can be by altering spec file.  If mingw/cygwin don't 
>> update there spec file in gcc that is there problem.  As well there is a 
>> flag to make stdcall default |-mrtd.  Little bit of a confusing name.  
>> Yes its provided for some strange reason mingw and cygwin don't use it.  
>> Windows is not the only OS with stdcall default.  Some unix's its also 
>> default nothing that strange other than mingw/cygwin not using it.  If 
>> in time rosbe becomes its own complier in gcc with its own spec file 
>> there is not reason why reactos cannot have it.  Its the maintainers of 
>> mingw/cygwin that have set the defaults without it.  So over the stdcall 
>> one either get up mingw/cygwin ribs or request rosbe gets a spec file of 
>> its own in gcc with reactos preferred settings.|
> 
> That is not strange. GCC's aim to provide uniform environment on 
> different machines.
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
> 
> _______________________________________________
> Ros-dev mailing list
> Ros-dev at reactos.org
> http://www.reactos.org/mailman/listinfo/ros-dev
>