Op een nazomerse herfstdag (Saturday 30 October 2004 00:58),schreef Ed Allen
Smith:
> In message <[EMAIL PROTECTED]> (on 30 October 2004
>
> 00:15:38 +0200), [EMAIL PROTECTED] (Abe Timmerman) wrote:
> >Op een nazomerse herfstdag (Friday 29 October 2004 23:35),schreef Ed
> > AllenSmith:
> >> In message <[EMAIL PROTECTED]> (on 29 October 2004
> >>
> >> 22:41:32 +0200), [EMAIL PROTECTED] (H.Merijn Brand) wrote:
> >> >On Fri 29 Oct 2004 20:12, Ed Allen Smith <[EMAIL PROTECTED]>
> >wrote:
[snip]
> >> Strongly agreed - for one thing, it's been a while since I worked with
> >> any (computer) language other than Perl! - plus wanting to know for
> >> people with IRIX 6.2-6.4; I note that Abe has a IRIX 6.2 machine doing
> >> smoketesting, although it seems to be doing 5.9.x, which may not have
> >> the problem in question, or it may be that the problem does not show up
> >> on a machine not capable of -64 (IP22 - especially with R4600 - indicate
> >> that it would not be capable, I believe).
> >
> >Nope, I haven't had any success with "-64", it'll only compile with "-32".
>
> -32 (same as -o32) or -n32?
-32, no luck with "-n32", although I cannot remember what the problem was :(
> >My 6.2 box also does 5.8.x, just tell me what to put in the .cfg as extra
> >options and I'll restart the current smoke:
>
> ==
> -Uusemallocwrap
> -Dusemallocwrap
> ==
Smoke is now restarted with this section added to the .cfg
> are the ones I'm using in a run I just started (see below) for testing what
> usemallocwrap is doing. For -n32 vs -32/-o32 (yours may well be defaulting
> to -o32, partially depending on what if anything is in
> /etc/compiler.defaults (or equivalent for older cc's):
>
> ==
> -Accflags='-n32'
> -Accflags='-32'
> ==
I haven't put this section in...
> or, alternatively,
>
> ==
> -Accflags='-n32'
> ==
>
> to lock it on a -n32 run. I am currently starting a run on a -n32/-o32 only
> machine running IRIX 6.5 using -n32 only but both the -Uusemallocwrap and
> -Dusemallocwrap options.
>
> >[iX irix - 6.2 MIPS R4600 Processor Chip Revision: 2.0 (133 MHZ) 1 IP22]
>
> Ah. R4600 == no -mips4, just -mips3. It _should_ be able to do -n32, unless
> the SGI FAQs entry is incorrect.
It's what the manual page for cc says, but I didn't get it to work.
Good luck,
Abe
--
Well, dereferencing that (as CvGV() would do) leads nowhere. Or, as
the Ten Commandments for C Programmers quoth, "Thou shalt not follow
the NULL pointer, for chaos and madness await thee at its end."
-- Jarkko Hietaniemi on p5p @ 2002-05-14
