From: Randy Rude <randy.rude@gdcanada.com>
To: Peter Barada <pbarada@mail.wm.sps.mot.com>
Cc: peter@baradas.org, gcc@gcc.gnu.org, crossgcc@sources.redhat.com
Subject: Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)
Date: Wed, 21 May 2003 16:56:00 -0000 [thread overview]
Message-ID: <1053536138.14557.7.camel@d1d6k111.bowman.gdcanada.com> (raw)
In-Reply-To: <200305211509.h4LF98K00400@hyper.wm.sps.mot.com>
On Wed, 2003-05-21 at 09:09, Peter Barada wrote:
>
> >This looks familiar. Try applying the hashtab.c portion of this patch:
> >http://gcc.gnu.org/ml/gcc-patches/2003-04/msg00726.html
>
> Cool, I'll try it and see what happens.
>
> I'm wondering why you didn't file a PR back in April against gcc-3.3
> that stated that m68k-elf won't build? At least that way someone
> would have *seen* that its broken and hopefully would've applied your
> patch(or created a better one). I'm also wondering how many newlib
> targets are affected by this bug?
I have to plead ignorance of the process. I sent this patch to both you
and gcc-patches. I assumed that would trigger someone into filing a
PR. Apparently I assumed incorrectly?
Randy
next prev parent reply other threads:[~2003-05-21 16:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-20 6:12 Peter Barada
2003-05-20 6:53 ` Erik Christiansen
2003-05-20 10:53 ` Kai Ruottu
2003-05-20 10:44 ` Kai Ruottu
2003-05-21 4:55 ` Peter Barada
2003-05-21 7:13 ` Peter Barada
2003-05-21 15:05 ` Randy Rude
2003-05-21 15:38 ` Peter Barada
2003-05-21 16:56 ` Randy Rude [this message]
2003-05-21 17:28 ` Joe Buck
2003-05-21 17:39 ` DJ Delorie
2003-05-22 14:59 ` Randy Rude
2003-05-22 17:36 ` DJ Delorie
2003-05-23 19:40 ` Randy Rude
2003-05-22 3:14 ` Peter Barada
2003-05-22 12:17 ` Kai Ruottu
2003-05-22 13:33 ` Peter Barada
2003-05-23 3:25 ` Peter Barada
2003-05-20 16:19 ` DJ Delorie
2003-05-20 21:06 ` Kaveh R. Ghazi
2003-05-20 21:44 ` DJ Delorie
2003-05-23 15:30 ` Kaveh R. Ghazi
2003-05-23 17:49 ` Joe Buck
2003-05-23 18:17 ` Peter Barada
2003-05-23 18:17 ` Joe Buck
2003-05-23 18:39 ` Peter Barada
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=1053536138.14557.7.camel@d1d6k111.bowman.gdcanada.com \
--to=randy.rude@gdcanada.com \
--cc=crossgcc@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=pbarada@mail.wm.sps.mot.com \
--cc=peter@baradas.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).