public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: kkaempf@progis.de (Klaus Kaempf)
To: egcs@cygnus.com
Subject: egcs-971105: compiler crash on c-torture/execute/920415-1.c
Date: Sat, 08 Nov 1997 07:46:00 -0000	[thread overview]
Message-ID: <9711081541.AA07939@progis.de> (raw)

This bug is still in egcs-971105 for openVMS/Alpha:

gcc 920415-1.c
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=FDCC2450, PC
=00193EE4, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
 Image Name   Module Name     Routine Name    Line Number  rel PC      abs PC 
 GCC-CC1      FLOW            find_basic_bloc       11775 00000C64    00193EE4
 GCC-CC1      FLOW            flow_analysis         11512 00000308    00193588
 GCC-CC1      TOPLEV          rest_of_compila       18415 00004F6C    000BA24C
 GCC-CC1      C-DECL          finish_function       18093 0000D710    0009AAB0
 GCC-CC1      C-PARSE         yyparse               13591 00002D98    00082F28
 GCC-CC1      TOPLEV          compile_file          17528 000031A4    000B8484
 GCC-CC1      TOPLEV          main                  19428 00007180    000BC460
 GCC-CC1      TOPLEV          __main                    0 000000B0    000B5390
                                                        0 837EA170    837EA170
%GCC-E-NOOBJECT, no object file was produced

This is an 32/64 bit bug which also shows up in the Windows NT/Alpha port. It was
fixed in gcc *after* the gcc/egcs split early august. Can someone please get the
right fix from the gcc snapshot ?

-- 
proGIS Software                 E-Mail: kkaempf@progis.de
Dipl.-Inform. Klaus K"ampf      Fax:    0241-47067-29
Jakobstr. 117                   Voice:  0241-47067-11
D-52064 Aachen                  WWW:	http://www.progis.de


                 reply	other threads:[~1997-11-08  7:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=9711081541.AA07939@progis.de \
    --to=kkaempf@progis.de \
    --cc=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).