This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: What does "internal error #20000524"?
- From: mike stump <mrs at windriver dot com>
- To: jbuck at synopsys dot COM, zack at codesourcery dot com
- Cc: gcc at gcc dot gnu dot org, rodrigc at mediaone dot net
- Date: Wed, 23 Jan 2002 14:40:43 -0800 (PST)
- Subject: Re: What does "internal error #20000524"?
> Date: Wed, 23 Jan 2002 10:08:19 -0800
> From: Zack Weinberg <zack@codesourcery.com>
> To: Joe Buck <jbuck@synopsys.COM>
> Cc: Craig Rodrigues <rodrigc@mediaone.net>, gcc@gcc.gnu.org
> On Wed, Jan 23, 2002 at 09:50:04AM -0800, Joe Buck wrote:
> > > On Tue, Jan 22, 2002 at 08:08:05PM -0500, Craig Rodrigues wrote:
> > > >
> > > > What do we gain by using the my_friendly_abort() macro vs. doing
> > > > just a plain abort() and getting the same "Internal compiler error"
> > > > messages in the C part of gcc?
> > >
> > > In my opinion, not much, and new code should use plain abort().
> >
> > The advantage of my_friendly_abort is that the user gets an indication
> > of the point in his/her code where the compiler blew up. Often it is
> > possible to work around the compiler bug by rewriting the code at that
> > point in the program.
> These days, plain abort does that too.
One can do a cat bugs/* | grep 'internal compiler error' | sed ... |
sort | uniq -c | sort -nr and then use this to prioritize the work to
be done. This is useful.