public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: dave.anglin@nrc.ca
To: gcc-gnats@gcc.gnu.org
Subject: c/4008: ICE: variable sized type and nested function
Date: Sun, 12 Aug 2001 14:36:00 -0000	[thread overview]
Message-ID: <20010812213349.4638.qmail@sourceware.cygnus.com> (raw)

>Number:         4008
>Category:       c
>Synopsis:       ICE: variable sized type and nested function
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Sun Aug 12 14:36:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Dave Anglin
>Release:        3.0.1 (prerealease) and 3.1 (prerelease)
>Organization:
>Environment:
i686-pc-linux-gnu and hppa1.1-hp-hpux10.20
>Description:
The testfile xxx.c causes various ICEs.  It was derived from compile/20010605-1.c.  Currently, compile/20010605-1.c fails on the PA.  Since there is a problem with the return of a variable sized type in a nested function, I wondered if there would also be with a variable sized parameter in a nested function.

With gcc-3.0.1 on the PA:

266 (hiauly1)dave> gcc -o xxx xxx.c
xxx.c: In function `block_parm':
xxx.c:13: Internal compiler error in size_binop, at fold-const.c:1914

On the PA, there is a problem with pa.h not doing appropriate checks after calling int_size_in_bytes for a return of -1.
However, even with this fixed, the test code still causes an ICE.  Part of the problem is assign_parms is called before the static chain list is built.  
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="xxx.c"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="xxx.c"

aW50Cm1haW4gKGludCBhcmdjLCBjaGFyICoqYXJndikKewogIGNvbnN0IGludCBzaXplID0gMTA7
CgogIHR5cGVkZWYgc3RydWN0IHsKICAgIGNoYXIgdmFsW3NpemVdOwogIH0gYmxvY2s7CgogIGlu
dCBibG9ja19wYXJtIChibG9jayBiKQogICAgewogICAgICByZXR1cm4gc2l6ZW9mIChiKTsKICAg
IH0KCiAgYmxvY2sgYTsKCiAgaWYgKGJsb2NrX3Bhcm0gKGEpICE9IHNpemUpCiAgICBhYm9ydCAo
KTsKCiAgZXhpdCAoMCk7Cn0K


             reply	other threads:[~2001-08-12 14:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-12 14:36 dave.anglin [this message]
2002-11-05  7:40 bangerth
2003-04-07  8:52 ehrhardt

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=20010812213349.4638.qmail@sourceware.cygnus.com \
    --to=dave.anglin@nrc.ca \
    --cc=gcc-gnats@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).