public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>
To: egcs@cygnus.com
Cc: ghazi@caip.rutgers.edu
Subject: egcs-971105 powerpc-ibm-aix4.1.4.0 new regression compile/920501-4.c
Date: Sun, 09 Nov 1997 08:06:00 -0000	[thread overview]
Message-ID: <199711091605.LAA00694@caip.rutgers.edu> (raw)

	I got a c-torture regression in egcs-971105 on powerpc-ibm-aix4.1.4.0.

I successfully bootstrapped a clean snapshot using BOOT_CFLAGS='-g -O3
-mminimal-toc' and also a clean snapshot plus Jim's unroll patch at
BOOT_CFLAGS='-g -O3 -funroll-all-loops -mminimal-toc -pipe'.

	Both bootstrapps have these new c-torture problems:

ERROR: 920501-4.c: compiler got signal 6: -O2 -fomit-frame-pointer
ERROR: 920501-4.c: compiler got signal 6: -O3 -fomit-frame-pointer
ERROR: 920501-4.c: compiler got signal 6: -O3 -funroll-all-loops

	Below is some more info about the failure.

		--Kaveh

---------------------------------------------------------------------------

	This is what gets output when compiled by hand with -O2
-fomit-frame-pointer:

compile/920501-4.c: In function `foo':
compile/920501-4.c:49: Could not find a spill register
(insn:QI 657 668 771 (parallel[
            (set (mem:SI (plus:SI (reg:SI 1 r1)
                        (const_int 32808)))
                (lshiftrt:SI (neg:SI (abs:SI (reg/v:SI 66 ctr)))
                    (const_int 31)))
            (clobber (scratch:SI))
        ] ) 540 {sleu+25} (nil)
    (expr_list:REG_UNUSED (scratch:SI)
        (nil)))

IOT/Abort trap in raise at 0xd0078900


---------------------------------------------------------------------------

	Here is the backtrace from cc1 using dbx:


raise(??) at 0xd0078900
abort() at 0xd0019a14
fatal_insn(message = (nil), insn = internal error: assertion failed at line 947
0xd0078900), line 1135 in "toplev.c"
allocate_reload_reg(??, ??, ??, ??), line 5196 in "reload1.c"
unnamed block $b6424, line 5746 in "reload1.c"
choose_reload_regs(??, ??), line 5746 in "reload1.c"
unnamed block $b6384, line 4127 in "reload1.c"
unnamed block $b6382, line 4127 in "reload1.c"
unnamed block $b6381, line 4127 in "reload1.c"
reload_as_needed(??, ??), line 4127 in "reload1.c"
reload1.reload(??, ??, ??), line 2081 in "reload1.c"
global_alloc(??), line 584 in "global.c"
unnamed block $b1372, line 3521 in "toplev.c"
unnamed block $b1371, line 3521 in "toplev.c"
rest_of_compilation(decl = internal error: assertion failed at line 947 in file
0x20058c64), line 3521 in "toplev.c"
finish_function(??), line 7050 in "c-decl.c"
yyparse(), line 144 in "c-parse.y"
compile_file(name = internal error: assertion failed at line 947 in file frame.c
"foo.i"), line 2513 in "toplev.c"
main(argc = 5, argv = 0x2ff22aac, envp = 0xffffffff), line 4394 in "toplev.c"
--
Kaveh R. Ghazi				Project Manager
ghazi@caip.rutgers.edu			ICon CMT Corp.

             reply	other threads:[~1997-11-09  8:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-11-09  8:06 Kaveh R. Ghazi [this message]
1997-11-18  7:52 Kaveh R. Ghazi

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=199711091605.LAA00694@caip.rutgers.edu \
    --to=ghazi@caip.rutgers.edu \
    --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).