Hello,
Thank you for all the quick and elaborate responses. My problem was the
following:
> After upgrading my Alpha Server 2100 to DU 3.2C I experience strange gcc
> errors for versions 2.7.0 and 2.6.3. The message is:
>
> mips-tfile, /tmp/ccaakcua.s:0 index 4294967295 is out of bounds for lstrs,
max
> is 0, mips-tfile.c line# 4642
The solution for the problem was:
1.) The assembler changed in version 3.2C compared to previous versions causing
the shown problem. One has to recompile the whole gcc package in order to solve
the problem.
2.) Better get version 2.7.2 of gcc, which is known to fix bugs that occured
with 2.7.0 and DU 3.2C.
Thanx a lot to the following people:
Christophe Colle colle_at_krtkg1.rug.ac.be special thanx for the gdb-patch
Arrigo Triulzi arrigo_at_lpac.ac.uk
Claes Sandgren csa_at_loke.soo.dec.com
Dan Riley dsr_at_lns598.lns.cornell.edu
My original question was:
On Mar 7, 10:57am, Gernot M. Fuchs wrote:
> After upgrading my Alpha Server 2100 to DU 3.2C I experience strange gcc
> errors for versions 2.7.0 and 2.6.3. The message is:
>
> mips-tfile, /tmp/ccaakcua.s:0 index 4294967295 is out of bounds for lstrs,
max
> is 0, mips-tfile.c line# 4642
>
> There is enough diskspace on /tmp and the access rights are set to drwxrwxrwt
> and the file ccaakcua.s does exsist during the compilation attempt with a
size
> > 0.
>
> I'm not sure if this has something to do with the upgrade or if it is only a
> coincidence. Version 2.7.0 of gcc was running fine before the OS-upgrade.
> Version 2.6.3 of gcc was installed after the upgrade to verify the behavior
of
> 2.7.0. Has someone had similar experiences?
And here are the quoted answers:
On Mar 7, 5:18pm, Christophe Colle wrote:
> I had exact the same problem. You must recompile gcc to get rid of these
> problems. After downloading and recompilation all my problems were gone
> with gcc.
> I had some problems with gdb, but I'm not sure if you're using gdb to
> debug. You may want to redownload gdb and recompile it. gdb 4.15.1 needs
> a patch to run correctly with DU 3.2c. I'm not sure if there is already
> a new release of gdb. If you need the patch then feel free to mail me.
On Mar 7, 4:45pm, Arrigo Triulzi wrote:
> You do not mention the version of OSF/1 you ugraded from. Version 2.0
> used a slightly different object format and you need to recompile
> under OSF/1 3.2c. You should also seriously consider moving to 2.7.2
> which compiles fine under 3.2c, 2.7.0 has some serious bugs.
On Mar 7, 5:51pm, Christophe Colle wrote:
> I included the patch for gdb below. As you see the patch is mentioned for
> gdb4.15, but i patched gdb4.15.1 with it and I had no problems. just
> move your gdb4.15.1 directory to gdb4.15 while compiling.
>
> Concerning gcc... I forgot to mention that you shouldn't be running
> 2.7.0, but you should try gcc2.7.1 or even better gcc2.7.2 It's known
> that gcc 2.7.0 has some problems on dec alpha.
>
> I compiled gcc2.7.2 without a problem on DU 3.2c a few months ago.
[attached patch file deleted, send mail if you need it]
On Mar 7, 5:54pm, Claes Sandgren wrote:
> There were some changes in defaults for the assembler starting at V3.2C
> Changing to gcc-2.7.1 or higher will fix it, or just just add -g to the
> #define ASM_SPEC in config/alpha/alpha.h.
> Should be looking something like this:
> #define ASM_SPEC "-nocpp %{pg}" --> #define ASM_SPEC "-g -nocpp %{pg}"
> Hopes this helps
On Mar 7, 12:31pm, Dan Riley wrote:
> This is caused by a change in the default behavior of the assembler in
> 3.2c. The recommended fix is to upgrade gcc to version 2.7.2. If you
> can't upgrade to 2.7.2 for some reason, I can tell you how to patch
> the source for 2.7.0, or you can copy over the assembler from an older
> version of OSF.
--
Dr. Gernot M. Fuchs University of North Carolina at Chapel Hill
voice: 919-966-3263 UNC Hospitals/School of Medicine
email: gfuchs_at_pasteur.med.unc.edu CB #7260, Chapel Hill, N.C. 27599
www : http://russell.med.unc.edu/~gfuchs
Received on Thu Mar 07 1996 - 19:49:04 NZDT