public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "charlet at act-europe dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload Date: Mon, 26 Jan 2004 08:15:00 -0000 [thread overview] Message-ID: <20040126081459.31745.qmail@sources.redhat.com> (raw) In-Reply-To: <20040117230657.13722.schwab@suse.de> ------- Additional Comments From charlet at act-europe dot fr 2004-01-26 08:14 ------- Subject: Re: [3.4/3.5 regression] [ia64] ICE in push_secondary_reload > However, it is my understanding that breaks that affect only Ada are > *not* considered critical, and in fact that there is no obligation for > anyone to attempt to build the Ada front end. I normally do not > bother building it even on platforms that can handle it (ia64-hpux > cannot, as the runtime has not been ported). This is why I did not Even if the run time has not been tailored for ia64-hpux, you can still build the generic part, which is more than enough for doing a bootstrap. > respond very fast to this bug report. I am willing to change my > habits if the policy has changed, but not otherwise. As shown by most of the Ada regressions recently, most of these regressions actually show real bugs in the non Ada part of GCC, so I believe this is in the interest of everyone to take Ada reports into consideration. I believe the policy you are stating was fine as long as Ada was not properly maintained, which is no longer the case. I'd suggest reconsidering the state of Ada, given the efforts invested recently on this front-end (as shown by the regular syncs and by the handling of Ada PRs in bugzilla). Arno -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13722
next prev parent reply other threads:[~2004-01-26 8:15 UTC|newest] Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-01-17 23:07 [Bug bootstrap/13722] New: [3.4/3.5 regression] [ia64] Ada bootstrap failure schwab at suse dot de 2004-01-17 23:09 ` [Bug bootstrap/13722] " pinskia at gcc dot gnu dot org 2004-01-18 2:13 ` zack at codesourcery dot com 2004-01-18 10:50 ` charlet at act-europe dot fr 2004-01-18 19:44 ` zack at codesourcery dot com 2004-01-18 21:32 ` charlet at act-europe dot fr 2004-01-18 21:42 ` zack at codesourcery dot com 2004-01-18 21:48 ` charlet at act-europe dot fr 2004-01-18 22:29 ` zack at codesourcery dot com 2004-01-18 22:31 ` charlet at act-europe dot fr 2004-01-18 22:33 ` zack at codesourcery dot com 2004-01-18 22:34 ` charlet at act-europe dot fr 2004-01-19 13:14 ` debian-gcc at lists dot debian dot org 2004-01-20 14:12 ` schwab at suse dot de 2004-01-21 13:16 ` rakdver at gcc dot gnu dot org 2004-01-21 14:13 ` [Bug target/13722] [3.4/3.5 regression] [ia64] ICE in push_secondary_reload schwab at suse dot de 2004-01-21 16:54 ` dhazeghi at yahoo dot com 2004-01-22 2:13 ` wilson at specifixinc dot com 2004-01-22 2:26 ` zack at codesourcery dot com 2004-01-22 5:21 ` wilson at specifixinc dot com 2004-01-22 8:23 ` zack at codesourcery dot com 2004-01-22 20:14 ` zack at gcc dot gnu dot org 2004-01-22 20:20 ` zack at codesourcery dot com 2004-01-22 22:05 ` rth at redhat dot com 2004-01-22 22:17 ` wilson at specifixinc dot com 2004-01-23 8:24 ` rth at redhat dot com 2004-01-23 8:35 ` zack at codesourcery dot com 2004-01-23 21:33 ` schwab at suse dot de 2004-01-23 21:51 ` zack at codesourcery dot com 2004-01-23 22:05 ` schwab at suse dot de 2004-01-23 22:18 ` zack at codesourcery dot com 2004-01-23 22:55 ` wilson at specifixinc dot com 2004-01-23 22:58 ` schwab at suse dot de 2004-01-23 23:22 ` wilson at specifixinc dot com 2004-01-24 0:04 ` schwab at suse dot de 2004-01-24 0:19 ` wilson at specifixinc dot com 2004-01-24 0:29 ` rth at redhat dot com 2004-01-24 1:28 ` zack at codesourcery dot com 2004-01-24 1:36 ` zack at codesourcery dot com 2004-01-24 1:52 ` zack at codesourcery dot com 2004-01-24 1:57 ` schwab at suse dot de 2004-01-24 2:20 ` zack at codesourcery dot com 2004-01-24 3:31 ` wilson at specifixinc dot com 2004-01-24 3:35 ` zack at codesourcery dot com 2004-01-24 3:55 ` wilson at specifixinc dot com 2004-01-24 14:10 ` schwab at suse dot de 2004-01-24 17:38 ` wilson at specifixinc dot com 2004-01-24 20:17 ` wilson at specifixinc dot com 2004-01-25 4:10 ` wilson at specifixinc dot com 2004-01-25 22:33 ` zack at codesourcery dot com 2004-01-26 8:14 ` Arnaud Charlet 2004-01-26 8:15 ` charlet at act-europe dot fr [this message] 2004-01-26 18:03 ` zack at codesourcery dot com 2004-01-27 0:08 ` wilson at specifixinc dot com 2004-01-27 17:51 ` ahs3 at fc dot hp dot com 2004-01-27 18:13 ` zack at codesourcery dot com 2004-01-27 18:43 ` ahs3 at fc dot hp dot com 2004-01-27 20:00 ` schwab at suse dot de 2004-01-28 18:13 ` zack at codesourcery dot com 2004-01-28 20:07 ` doko at cs dot tu-berlin dot de 2004-01-28 21:27 ` wilson at specifixinc dot com 2004-01-28 21:39 ` zack at gcc dot gnu dot org 2004-01-28 22:08 ` wilson at specifixinc dot com 2004-01-29 6:47 ` doko at cs dot tu-berlin dot de 2004-01-30 2:25 ` wilson at specifixinc dot com
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=20040126081459.31745.qmail@sources.redhat.com \ --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).