public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Roman Zippel <zippel@linux-m68k.org>
To: Mark Mitchell <mark@codesourcery.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC 3.0 Status Report
Date: Tue, 12 Jun 2001 16:16:00 -0000	[thread overview]
Message-ID: <3B26A2B5.222A5454@linux-m68k.org> (raw)
In-Reply-To: <20010611214848B.mitchell@codesourcery.com>

Hi,

Mark Mitchell wrote:

> 68K: Bootstrap problem.  PR1795.  If this is not fixed soon, it
>      can wait for 3.0.1.

I think we have a choice here between here between a compiler that
doesn't work at all or a compiler that might work, as there was
obviously no testing done for quite some time. At bootstrap/3090, c/3092
and c/3095 there are the minimum changes described needed to get a sort
of working compiler, but even that produces more than 100 failures
during check, about half of them are regressions to 2.95. I have some
patches to reduce it to 74 failures and I'd like to help to analyze/fix
more of them.
BTW there are two new regression from 3.0 to 3.1, I'll can post them
later.

bye, Roman

  parent reply	other threads:[~2001-06-12 16:16 UTC|newest]

Thread overview: 107+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 21:48 Mark Mitchell
2001-06-11 22:31 ` Loren James Rittle
2001-06-12  0:56 ` Joseph S. Myers
2001-06-12  1:17   ` Mark Mitchell
2001-06-12  1:57 ` Nathan Sidwell
2001-06-12  9:37   ` Tom Tromey
2001-06-12  2:53 ` GCC 3.0 Status Report (the ARM bits) Richard Earnshaw
2001-06-12  4:51   ` Nathan Sidwell
2001-06-13  0:34   ` Philip Blundell
2001-06-13  9:06     ` Mark Mitchell
2001-06-12  3:42 ` GCC 3.0 Status Report Joseph S. Myers
2001-06-12  5:01   ` Franz Sirl
2001-06-12 19:39     ` Stan Shebs
2001-06-13  9:39       ` Mark Mitchell
2001-06-13 11:58         ` Franz Sirl
2001-06-12  5:32 ` Bernd Schmidt
2001-06-12  8:01   ` Geert Bosch
2001-06-12  8:13 ` GCC 3.0 Success on sparc-sun-solaris2.8 (Was: GCC 3.0 Status Report) Geert Bosch
2001-06-12 16:16 ` Roman Zippel [this message]
2001-06-12 16:21   ` GCC 3.0 Status Report Mark Mitchell
2001-06-13  5:11 ` Joseph S. Myers
2001-06-13  6:00   ` Gerald Pfeifer
2001-06-13  9:45   ` Mark Mitchell
  -- strict thread matches above, loose matches on Subject: below --
2001-06-12 17:42 Robert Schweikert
2001-06-12 18:38 ` Mark Mitchell
2001-06-05 13:23 Mark Mitchell
2001-06-05 13:49 ` Richard Henderson
2001-06-05 14:15 ` Rainer Orth
2001-06-05 18:09   ` Mark Mitchell
2001-06-06  4:54     ` Rainer Orth
2001-06-05 15:16 ` Joseph S. Myers
2001-06-05 15:33 ` benjamin kosnik
2001-06-05 15:56   ` Mark Mitchell
2001-06-05 15:56 ` Franz Sirl
2001-06-05 16:04   ` Mark Mitchell
2001-06-05 21:04 ` Alexandre Petit-Bianco
2001-06-05 23:08   ` Mark Mitchell
2001-05-21 18:48 Mark Mitchell
2001-05-21 20:23 ` Daniel Berlin
2001-05-22  1:44 ` Dennis Bjorklund
2001-05-22  2:33   ` Joseph S. Myers
2001-05-22  7:58   ` Mark Mitchell
2001-05-22 10:52     ` Dennis Bjorklund
2001-05-22  3:37 ` Joseph S. Myers
2001-05-22  3:53   ` Gerald Pfeifer
2001-05-22 13:51 ` Phil Edwards
2001-05-22 14:02   ` Mark Mitchell
2001-05-22 14:22 ` Toon Moene
2001-05-22 14:37   ` Mark Mitchell
2001-05-17  2:29 Christian Iseli
2001-05-14 14:28 Mark Mitchell
2001-05-14 16:44 ` Joseph S. Myers
2001-05-17  9:27   ` Joe Buck
2001-06-11 10:08     ` Joern Rennecke
2001-05-02 16:09 Mike Stump
2001-05-07  9:14 ` Joe Buck
2001-05-01 18:56 Mike Stump
2001-05-02  8:47 ` Mark Mitchell
2001-05-01 17:22 Mark Mitchell
2001-04-19 23:33 Michael Elizabeth Chastain
2001-04-19 13:27 Michael Elizabeth Chastain
2001-04-19 13:32 ` John David Anglin
     [not found] <200104182009.NAA09066@bosch.cygnus.com>
2001-04-19 13:07 ` John David Anglin
2001-04-19 13:34   ` Mark Mitchell
2001-04-19 13:39     ` John David Anglin
2001-04-19 15:41   ` Mark Mitchell
2001-04-19 17:43     ` Joe Buck
2001-04-19 17:54       ` Mark Mitchell
2001-04-19 17:30   ` Benjamin Kosnik
2001-04-22  8:41   ` Fergus Henderson
2001-04-18 12:34 Michael Elizabeth Chastain
     [not found] <1654.987568477@slagheap.cygnus.com>
2001-04-18 10:38 ` John David Anglin
     [not found] <no.id>
2001-04-17 19:11 ` John David Anglin
2001-04-18  0:55   ` Mark Mitchell
2001-04-18  9:00     ` John David Anglin
2001-04-18 13:51     ` John David Anglin
2001-04-20 13:36       ` Mark Mitchell
2001-04-17 16:13 John David Anglin
2001-04-17 16:38 ` Gabriel Dos Reis
2001-04-17 18:40   ` John David Anglin
2001-04-17 10:32 Michael Elizabeth Chastain
2001-04-17  0:32 Mark Mitchell
2001-04-17 16:31 ` Toon Moene
2001-04-17 16:37   ` Mark Mitchell
2001-04-18  7:02 ` Andreas Schwab
2001-04-18 19:51   ` Mark Mitchell
2001-04-19  2:13     ` Gabriel Dos Reis
2001-04-19  8:33       ` Mark Mitchell
2001-04-19 13:36     ` Phil Edwards
2001-04-03 10:38 Mark Mitchell
2001-04-03 13:24 ` Joseph S. Myers
2001-04-03 14:22   ` Toon Moene
2001-03-27  8:55 Mark Mitchell
2001-03-27  9:51 ` David Edelsohn
2001-03-20  4:18 Peter Bienstman
2001-03-19 12:23 Mark Mitchell
2001-03-19 13:35 ` Craig Rodrigues
2001-03-19 16:04   ` Mark Mitchell
2001-03-19 17:16 ` Geoff Keating
2001-03-19 17:26   ` Mark Mitchell
2001-03-19 18:42     ` Stan Shebs
2001-03-19 19:07       ` Daniel Berlin
2001-03-19 19:53         ` Stan Shebs
2001-03-19 20:18           ` Mark Mitchell
2001-03-19 17:43   ` Daniel Berlin
2001-03-19 18:15     ` Geoff Keating
2001-03-19 18:11   ` Daniel Berlin

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=3B26A2B5.222A5454@linux-m68k.org \
    --to=zippel@linux-m68k.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mark@codesourcery.com \
    /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).