public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: mark.fallon@oracle.com
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: c/6987: failure at  s390_final_chunkify when more than 4K bytes for globals
Date: Thu, 13 Jun 2002 17:16:00 -0000	[thread overview]
Message-ID: <20020613204607.8875.qmail@sources.redhat.com> (raw)

The following reply was made to PR c/6987; it has been noted by GNATS.

From: mark.fallon@oracle.com
To: gcc-gnats@gcc.gnu.org
Cc: Tom_Russell@ca.ibm.com
Subject: c/6987: failure at  s390_final_chunkify when more than 4K bytes for globals
Date: 11 Jun 2002 01:01:53 -0000

 >Number:         6987
 >Category:       c
 >Synopsis:       failure at  s390_final_chunkify when more than 4K bytes for globals
 >Confidential:   no
 >Severity:       critical
 >Priority:       medium
 >Responsible:    unassigned
 >State:          open
 >Class:          sw-bug
 >Submitter-Id:   net
 >Arrival-Date:   Mon Jun 10 18:06:00 PDT 2002
 >Closed-Date:
 >Last-Modified:
 >Originator:     mark.fallon@oracle.com
 >Release:        gcc version 2.95.3 20010315 (SuSE)
 >Organization:
 >Environment:
 cat /proc/version
 Linux version 2.4.7-SuSE-SMP (root@k_deflt.suse.de) (gcc version 2.95.3 20010315 (SuSE)) #1 SMP Fri Oct 26 00:53:12 GMT 2001
 >Description:
 
 ----------------------- gen.pl -----------------------------
 $max = $ENV{MAX} || 4096;
 
 foreach $i (0 .. $max) {
    print "extern long i_$i;\n";
 }
 print "void test()\n{\n";
 foreach $i (0 .. $max) {
    print "  i_$i = $i;\n";
 }
 print "}\n";
 
 ------------------------------------------------------------
 
 linux1:~ # MAX=1024 perl gen.pl > gen.c; cc -c gen.c
 /tmp/ccQk1Bdb.s: Assembler messages:
 /tmp/ccQk1Bdb.s:5141: Error: operand out of range (4096 not between 0 and 4095)
 linux1:~ # MAX=3243 perl gen.pl > gen.c; cc -c gen.c
 (insn 2565 17766 2568 (set (mem/f:SI (reg:SI 1 %r1) 0)
         (reg:SI 2 %r2)) 48 {*movsi} (nil)
     (nil))
 
 (insn 16223 16220 25962 (set (reg:SI 1 %r1)
         (mem/u:SI (symbol_ref/u:SI ("*.LC3243")) 0)) 48 {*movsi} (nil)
     (expr_list:REG_EQUAL (symbol_ref:SI ("i_3243"))
         (nil)))
 s390 multiple literalpool support:
  No code label between this insn 1800 9804gen.c: In function `test':
 gen.c:6491: Internal compiler error in `s390_final_chunkify', at config/s390/s390.c:1888
 Please submit a full bug report.
 See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
 linux1:~ #
 linux1:~ # cc -v
 Reading specs from /usr/lib/gcc-lib/s390-suse-linux/2.95.3/specs
 gcc version 2.95.3 20010315 (SuSE)
 
 linux1:/proc # cat version
 Linux version 2.4.7-SuSE-SMP (root@k_deflt.suse.de) (gcc version 2.95.3 20010315 (SuSE)) #1 SMP Fri Oct 26 00:53:12 GMT 2001
 
 This is a critical problem holding up our system build process. 
 
 >How-To-Repeat:
 
 >Fix:
 
 >Release-Note:
 >Audit-Trail:
 >Unformatted:


             reply	other threads:[~2002-06-13 20:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 17:16 mark.fallon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-21  5:56 uweigand
2002-06-10 18:06 mark.fallon

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=20020613204607.8875.qmail@sources.redhat.com \
    --to=mark.fallon@oracle.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@gcc.gnu.org \
    /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).