Re: failure building gcc-3.3 (broken libiberty/vsprintf.c or build?)

[Joe Buck <jbuck at synopsys dot com>]

On Wed, May 21, 2003 at 10:55:38AM -0600, Randy Rude wrote:
> 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?

You assumed incorrectly.  The process really works the other way around;
patches usually get more attention if they fix a PR that gets flagged as
high priority.  So you really want to get your PRs in at the same time
as, or before, your patches.  It's really unlikely that someone will
respond to a proposed patch by creating a PR.


-- 
Q. What's more of a headache than a bug in a compiler.
A. Bugs in six compilers.  -- Mark Johnson

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com