public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/22533] [4.1 regression] Ada ICE during bootstrap on many platforms
Date: Wed, 16 Nov 2005 17:27:00 -0000 [thread overview]
Message-ID: <20051116172749.19653.qmail@sourceware.org> (raw)
In-Reply-To: <bug-22533-7667@http.gcc.gnu.org/bugzilla/>
------- Comment #29 from ebotcazou at gcc dot gnu dot org 2005-11-16 17:27 -------
> So I guess it would be possible right now to fix the bootstrap issue
> by a pure front-end patch. (This doesn't address the more general
> question of whether or not the gimplifier has a bug that can be exposed
> by other front-ends too, of course ...)
OK, thanks for the analysis.
Richard, what do you think? The pure front-end patch Ulrich is talking about
is the Ada FE part of http://gcc.gnu.org/ml/gcc-patches/2005-07/msg01666.html
--
ebotcazou at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kenner at vlsi1 dot ultra
| |dot nyu dot edu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22533
next prev parent reply other threads:[~2005-11-16 17:27 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-22533-7667@http.gcc.gnu.org/bugzilla/>
2005-10-06 19:06 ` [Bug ada/22533] [4.1 regression] ICE in get_base_var ro at gcc dot gnu dot org
2005-10-12 11:55 ` rguenth at gcc dot gnu dot org
2005-10-12 12:43 ` schwab at suse dot de
2005-10-12 19:33 ` laurent at guerby dot net
2005-10-12 19:36 ` pinskia at gcc dot gnu dot org
2005-10-14 17:26 ` pinskia at gcc dot gnu dot org
2005-10-19 3:13 ` pinskia at gcc dot gnu dot org
2005-10-19 3:14 ` pinskia at gcc dot gnu dot org
2005-10-31 4:10 ` mmitchel at gcc dot gnu dot org
2005-11-04 19:29 ` laurent at guerby dot net
2005-11-05 0:23 ` uweigand at gcc dot gnu dot org
2005-11-12 16:52 ` laurent at guerby dot net
2005-11-15 6:31 ` [Bug ada/22533] [4.1 regression] Ada ICE during bootstrap on many platforms ebotcazou at gcc dot gnu dot org
2005-11-15 6:32 ` ebotcazou at gcc dot gnu dot org
2005-11-15 7:47 ` ebotcazou at gcc dot gnu dot org
2005-11-15 18:31 ` uweigand at gcc dot gnu dot org
2005-11-16 17:27 ` ebotcazou at gcc dot gnu dot org [this message]
2005-11-17 1:09 ` uweigand at gcc dot gnu dot org
2005-11-22 1:00 ` [Bug ada/22533] [4.1/4.2 " pluto at agmk dot net
2005-11-23 11:11 ` ebotcazou at gcc dot gnu dot org
2005-11-23 19:16 ` pluto at agmk dot net
2005-11-23 19:36 ` ebotcazou at gcc dot gnu dot org
2005-11-23 19:47 ` pluto at agmk dot net
2005-11-23 23:28 ` ebotcazou at gcc dot gnu dot org
2005-11-23 23:29 ` ebotcazou at gcc dot gnu dot org
2005-11-24 11:14 ` ebotcazou at gcc dot gnu dot org
2005-11-24 14:46 ` pluto at agmk dot net
2005-11-24 20:21 ` pluto at agmk dot net
2005-11-24 23:29 ` debian-gcc at lists dot debian dot org
2005-11-25 16:04 ` pluto at agmk dot net
2005-11-26 11:57 ` pluto at agmk dot net
2005-11-26 12:40 ` pluto at agmk dot net
2005-12-06 7:29 ` ebotcazou at gcc dot gnu dot org
2005-12-22 17:59 ` ebotcazou at gcc dot gnu dot org
2006-01-03 12:38 ` ebotcazou 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=20051116172749.19653.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).