From: Jeffrey A Law <law@cygnus.com>
To: Axel Thimm <Axel.Thimm@physik.fu-berlin.de>
Cc: egcs@egcs.cygnus.com
Subject: Re: alpha-dec-osf4.0b problems (was Re: Snapshot)
Date: Wed, 30 Jun 1999 15:43:00 -0000 [thread overview]
Message-ID: <14189.928445037@upchuck.cygnus.com> (raw)
Message-ID: <19990630154300.yVip-oNZEoOvDtqgmL13NzOadtPRN2AVBVhjKUICqbc@z> (raw)
In-Reply-To: <19990603194613.A4029@physik.fu-berlin.de>
In message < 19990603194613.A4029@physik.fu-berlin.de >you write:
> Unfortunately alpha-dec-osf4.0b still gets stuck on the problem I had
> reported. What exact system have you been using? I used egcs 19990502 and g
> cc
> 2.7.1 for bootstrapping on an EV4.5 (21064). When I reported the problem so
> me
> time ago, Alexandre Olivia for instance wrote that he had no problems
> compiling egcs on alphas, so I assume this is might be an OS revision probl
> em.
>
> > /amd/titania/usr/scratch1/thimm/work/build/egcs/alpha-dec-osf4.0b/gcc/xgc
> c -B/amd/titania/usr/scratch1/thimm/work/build/egcs/alpha-dec-osf4.0b/gcc/
> -B/home/thimm/public/gcc-2.95_19990602/alpha-dec-osf4.0/alpha-dec-osf4.0b/b
> in/ -c -DHAVE_CONFIG_H -g -O2 -I. -I/home/thimm/work/src/egcs/libiberty/../
> include /home/thimm/work/src/egcs/libiberty/vasprintf.c
> > xgcc: Internal compiler error: program cc1 got fatal signal 11
Can you repost the full testcase? This is the case that Richard was
supposed to have fixed.
jeff
next prev parent reply other threads:[~1999-06-30 15:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-01 9:59 Snapshot Jeffrey A Law
1999-06-03 10:46 ` alpha-dec-osf4.0b problems (was Re: Snapshot) Axel Thimm
1999-06-03 14:29 ` Jeffrey A Law [this message]
1999-06-30 15:43 ` Jeffrey A Law
1999-06-30 15:43 ` Axel Thimm
1999-06-30 15:43 ` Snapshot Jeffrey A Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=14189.928445037@upchuck.cygnus.com \
--to=law@cygnus.com \
--cc=Axel.Thimm@physik.fu-berlin.de \
--cc=egcs@egcs.cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).