public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* What to include in a bugreport related to boostrapping?
@ 2002-05-31 21:20 Alexander Klein
  2002-05-31 22:00 ` CM
       [not found] ` <200205312325.QAA26435@atrus.synopsys.com>
  0 siblings, 2 replies; 3+ messages in thread
From: Alexander Klein @ 2002-05-31 21:20 UTC (permalink / raw)
  To: gcc

Hi,

When trying to build GCC with versions >=3, they will always explode sooner
or later, depending on the exact version. 3.1, for example, goes through
the boostrapping process, but then dies generating illegal Assembler
instructions while compiling the libraries. Unfortunately, I'm a bit unsure
what I should include to make a useful bugreport.

Should I just report it in the usual way with the .i-file included?

Best regards,

	Alex


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2002-06-07 18:52 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-05-31 21:20 What to include in a bugreport related to boostrapping? Alexander Klein
2002-05-31 22:00 ` CM
     [not found] ` <200205312325.QAA26435@atrus.synopsys.com>
2002-06-07 12:07   ` Problems bootstrapping on m68k-unknown-netbsd1.5.1 (Re: What toinclude in a bugreport related to boostrapping?) Alexander Klein

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).