GCC - Vista Memory Cripple

[Roger Oberholtzer]

On Fri, 2007-03-30 at 19:26 +1000, James McDonald wrote:
> On Thu, Mar 29, 2007 at 08:24:51AM +0200, Roger Oberholtzer wrote:
> > On Thu, 2007-03-29 at 13:31 +1000, James McDonald wrote:
> > > http://www.trnicely.net/misc/vista.html
> > 
> > The title is a bit of sensationalism. Who copyrights info like this? It
> > is not a clear description of the problem. gcc must interface with
> > Windows at some point to get memory. Perhaps it uses a depreciated API
> > that now exhibits this behavior. Windows is full of APIs. You have to
> > choose the right one.  The title makes it sound like Vista senses gcc
> > and gets nasty. I suspect gcc is simply not up-to-date.
> > 
> > Does the same source program compiled with gcc and then with MSVC++ have
> > the limit in both cases? I am guessing it does not. What libs are used?
> > Perhaps they are incorrect. malloc() and all are not really compiler
> > items. They are library functions like any other.
> > 
> > Interesting read, but I suspect Thomas would have done well to have
> > mentioned if he had contacted the gcc folk to see if it is a known
> > issue.
> > 
> > -- 
> > Roger Oberholtzer
> >
> I don't know much about the GCC problem but it seems to be something
> that will probably be fixed within a few weeks / months....
> 
> You are probably right re him using some API that's so deprecated that
> it just won't work.

Or even the gcc libs themselves. After all, they are not the standard
GNU C libs. They are MINGW or some such thing. We opted ffor running
MSVC++ under CrossOver Office on Linux to get W32 bins. Of course, our
MSVC++ compiler is a bit long in the tooth. I have not heard if anyone
is trying our stuff on Vista yet. We have some low level data analyses
that really are happiest with lots of memory. Hate to rework them just
for Vista.

-- 
Roger Oberholtzer

OPQ Systems / Ramb?ll RST

Ramb?ll Sverige AB
Kapellgr?nd 7
P.O. Box 4205
SE-102 65 Stockholm, Sweden

Tel: Int +46 8-615 60 20
Fax: Int +46 8-31 42 23