public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/19865] [4.0 Regression] ice / gnat bug detected.
Date: Tue, 15 Feb 2005 16:16:00 -0000 [thread overview]
Message-ID: <20050215023907.28396.qmail@sourceware.org> (raw)
In-Reply-To: <20050209180751.19865.pluto@pld-linux.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-15 02:39 -------
(In reply to comment #8)
> Did you mean MOVE_RATIO?
Yes. A value of 2 should be able to reproduce it. If we have any bigger value, the gimplifier will not
produce the CONST_DECL which we will SRA on it.
Here is the smallest testcase which I could get:
package body PR19865 is
type Integer_List is array (Positive range <>) of Integer;
type Integer_List_Access is access all Integer_List;
No_Argument : aliased Integer_List := (1 .. 0 => 0);
package Cache_Args is
Table : aliased Integer_List_Access := null;
end Cache_Args;
procedure Build_Dynamic_Library (Options : Integer_List);
procedure Test is
Lib_Opts : Integer_List_Access := No_Argument'Unrestricted_Access;
begin
for Index in 1 .. 1 loop
Cache_Args.Table(Index) := 0;
end loop;
Build_Dynamic_Library (Lib_Opts.all);
end Test;
procedure Build_Dynamic_Library (Options : Integer_List) is
begin
null;
end Build_Dynamic_Library;
end PR19865;
package PR19865 is
procedure Test;
end PR19865;
Write it out to a file called t.ada and run gnatchop on it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19865
next prev parent reply other threads:[~2005-02-15 2:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 23:35 [Bug ada/19865] New: " pluto at pld-linux dot org
2005-02-10 0:07 ` [Bug ada/19865] " mmazur at kernel dot pl
2005-02-10 0:33 ` [Bug ada/19865] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-02-10 12:24 ` awreynolds at mac dot com
2005-02-15 0:09 ` bosch at gcc dot gnu dot org
2005-02-15 1:23 ` pinskia at gcc dot gnu dot org
2005-02-15 1:32 ` dnovillo at gcc dot gnu dot org
2005-02-15 1:56 ` uweigand at gcc dot gnu dot org
2005-02-15 2:39 ` dnovillo at gcc dot gnu dot org
2005-02-15 3:14 ` pinskia at gcc dot gnu dot org
2005-02-15 4:20 ` dnovillo at gcc dot gnu dot org
2005-02-15 4:44 ` pinskia at gcc dot gnu dot org
2005-02-15 5:08 ` dnovillo at redhat dot com
2005-02-15 5:45 ` pinskia at gcc dot gnu dot org
2005-02-15 5:48 ` uweigand at gcc dot gnu dot org
2005-02-15 16:16 ` pinskia at gcc dot gnu dot org [this message]
2005-02-15 20:52 ` [Bug middle-end/19865] " uweigand at gcc dot gnu dot org
2005-02-16 19:17 ` dnovillo at redhat dot com
2005-02-17 0:16 ` dnovillo at gcc dot gnu dot org
2005-02-17 0:16 ` cvs-commit at gcc dot gnu dot org
2005-02-17 1:31 ` pinskia at gcc dot gnu dot org
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=20050215023907.28396.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).