public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "danglin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/17399] [4.0 Regression] Ada does not bootstrap Date: Mon, 20 Sep 2004 22:52:00 -0000 [thread overview] Message-ID: <20040920225224.16064.qmail@sourceware.org> (raw) In-Reply-To: <20040910153343.17399.phython@gcc.gnu.org> ------- Additional Comments From danglin at gcc dot gnu dot org 2004-09-20 22:52 ------- ../../xgcc -B../../ -c -g -O2 -fPIC -W -Wall -gnatpg g-regexp.adb -o g-reg exp.o g-regexp.adb: In function 'GNAT.REGEXP.COMPILE.CREATE_SECONDARY_TABLE': g-regexp.adb:1087: error: Definition in block 5 does not dominate use in block 1 10 for SSA_NAME: D.1827_717 in statement: ivtmp.868D.4706_563 = &(*table.51D.1823_144)[J99b.52D.1828_3]{lb: 1 sz: D.1827_7 17 * 4}[0]; +===========================GNAT BUG DETECTED==============================+ | 4.0.0 20040920 (experimental) (i686-pc-linux-gnu) verify_ssa failed. | | Error detected at g-regexp.adb:1389:1 | | Please submit a bug report; see http://gcc.gnu.org/bugs.html. | | Include the entire contents of this bug box in the report. | | Include the exact gcc or gnatmake command that you entered. | | Also include sources listed below in gnatchop format | | (concatenated together with no headers between files). | +==========================================================================+ The problem still seems to be there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17399
next prev parent reply other threads:[~2004-09-20 22:52 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-10 15:33 [Bug ada/17399] New: " phython at gcc dot gnu dot org 2004-09-10 15:36 ` [Bug ada/17399] " pinskia at gcc dot gnu dot org 2004-09-10 17:54 ` phython at gcc dot gnu dot org 2004-09-11 17:53 ` [Bug middle-end/17399] [4.0 Regression] " pinskia at gcc dot gnu dot org 2004-09-11 20:06 ` [Bug middle-end/17399] [4.0 Regression] Ada does not bootstrap on ppc-linux pinskia at gcc dot gnu dot org 2004-09-13 0:22 ` phython at gcc dot gnu dot org 2004-09-13 2:00 ` phython at gcc dot gnu dot org 2004-09-13 2:26 ` phython at gcc dot gnu dot org 2004-09-13 2:43 ` giovannibajo at libero dot it 2004-09-13 3:08 ` [Bug ada/17399] " rth at gcc dot gnu dot org 2004-09-13 12:32 ` charlet at gcc dot gnu dot org 2004-09-13 22:44 ` phython at gcc dot gnu dot org 2004-09-14 1:48 ` phython at gcc dot gnu dot org 2004-09-14 8:02 ` charlet at act-europe dot fr 2004-09-14 8:23 ` giovannibajo at libero dot it 2004-09-14 8:25 ` giovannibajo at libero dot it 2004-09-14 16:14 ` [Bug ada/17399] [4.0 Regression] Ada does not bootstrap pinskia at gcc dot gnu dot org 2004-09-16 5:45 ` aaronavay62 at aaronwl dot com 2004-09-16 17:15 ` awreynolds at mac dot com 2004-09-19 6:17 ` aaronavay62 at aaronwl dot com 2004-09-20 22:52 ` danglin at gcc dot gnu dot org [this message] 2004-09-21 18:49 ` pinskia at gcc dot gnu dot org 2004-09-21 19:05 ` pinskia at gcc dot gnu dot org 2004-09-23 4:52 ` aaronavay62 at aaronwl dot com 2004-09-23 17:00 ` dave at hiauly1 dot hia dot nrc dot ca 2004-10-02 0:54 ` pinskia at gcc dot gnu dot org 2004-10-03 17:53 ` 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=20040920225224.16064.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: linkBe 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).