Re: [MiNT] gcc 4.2.2 compile error

[MiKRO <miro.kropacek@gmail.com>]

> I would like to be sure: you are compiling a native GCC 4.2.2 on
> FreeMiNT with gcc 2.95, right ?
>
right.

> The question is which executable failed with memory violation ? Was it
> the old GCC 2.95, or the newly compiled GCC 4.2.2 ? And which executable
>   ? cc1 ? xgcc ? other ?
I'd guess it was (x)gcc (remember, stage 2) but I'll check it at home.

> The first cause of access violations is insufficient stack space (as
> discussed here some days ago). You should try to increase the stack of
> the faulty executable (I can't remember the name of the tool to do
> that). But in order to make it possible for the executables generated by
> GCC 4.2.2, you must apply the MiNTLib patch provided by Alan, not yet in
> CVS.
that tool is called 'stack' and yes, my mintlib has all up-to-date
patches which appeared in mintlist (and yes, I rejected that ones
which were replaced with the new one)

so you want to make something like 'stack --fix=512k
path/to/newly/compiled/gcc' ? or bigger stack?

> The latest versions of GCC are know to use an abnormal amount of memory,
> so this may be the problem. If the problem occurs only when compiling a
> specific file, try to disable the optimizations for that file only,
> sometimes it works.
256 MB should be enough, shouldn't be?

> Another advice: during your tests you should configure gcc with
> --disable-multilib, to avoid the build of the 68020 and mshort
> libraries. You will save a lot of time !
>
yes, i know about it, for sure I do

> Good luck (you will need it).
>
;-) Thanks for the tips. That stack issue is very good point.

-- 
MiKRO / Mystic Bytes
http://mikro.atari.org