public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dave at hiauly1 dot hia dot nrc dot ca" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug rtl-optimization/32296] [4.3 Regression] Bootstrap failure in stage1 on hppa*-*-* Date: Thu, 21 Jun 2007 02:56:00 -0000 [thread overview] Message-ID: <20070621025642.6104.qmail@sourceware.org> (raw) In-Reply-To: <bug-32296-276@http.gcc.gnu.org/bugzilla/> ------- Comment #19 from dave at hiauly1 dot hia dot nrc dot ca 2007-06-21 02:56 ------- Subject: Re: [4.3 Regression] Bootstrap failure in stage1 on hppa*-*-* > Created an attachment (id=13738) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13738&action=view) > --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13738&action=view) > Patch under test With this patch hppa-unknown-linux-gnu bootstraps, although test results are poor. I'm still having problems with hppa64. This looks like it may be a va_list problem. Dave -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32296
next prev parent reply other threads:[~2007-06-21 2:56 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-06-12 0:33 [Bug regression/32296] New: " danglin at gcc dot gnu dot org 2007-06-12 0:40 ` [Bug regression/32296] " pinskia at gcc dot gnu dot org 2007-06-12 0:44 ` [Bug rtl-optimization/32296] [4.3 Regression] " pinskia at gcc dot gnu dot org 2007-06-12 1:01 ` spark at gcc dot gnu dot org 2007-06-12 1:14 ` spark at gcc dot gnu dot org 2007-06-12 1:38 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-12 21:43 ` spark at gcc dot gnu dot org 2007-06-12 23:00 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-12 23:07 ` spark at gcc dot gnu dot org 2007-06-12 23:31 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-13 3:45 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-13 3:48 ` spark at gcc dot gnu dot org 2007-06-13 13:28 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-14 3:54 ` spark at gcc dot gnu dot org 2007-06-14 21:05 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-15 20:05 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-19 19:57 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-19 20:10 ` hjl at lucon dot org 2007-06-19 20:40 ` dave at hiauly1 dot hia dot nrc dot ca 2007-06-19 23:30 ` danglin at gcc dot gnu dot org 2007-06-19 23:32 ` danglin at gcc dot gnu dot org 2007-06-21 2:56 ` dave at hiauly1 dot hia dot nrc dot ca [this message] 2007-06-21 8:53 ` tbm at cyrius dot com 2007-06-29 18:44 ` mmitchel at gcc dot gnu dot org 2007-06-30 15:20 ` danglin 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=20070621025642.6104.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).