public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: jeroen dobbelaere <jeroen.dobbelaere@acunia.com>
Cc: Richard.Earnshaw@arm.com, gcc-patches@gcc.gnu.org
Subject: Re: Fix arm-linux bootstrap problem on cvs.
Date: Wed, 03 Jul 2002 08:42:00 -0000	[thread overview]
Message-ID: <200207031541.QAA13617@cam-mail2.cambridge.arm.com> (raw)
In-Reply-To: Your message of "Wed, 03 Jul 2002 17:35:08 +0200." <3D2319AC.7040103@acunia.com>


> > 
> > Ok once bootstrap and regtest are successfully completed.  However, 
> > ChangeLog entries should be:
> > 
> [..]
> 
> This will be difficult : for the last few weeks, the tests could not be run
> as the compiler didn't work.
> 

It should be possible to compare it with an unmodified compiler built with 
checking disabled.

R.

  reply	other threads:[~2002-07-03 15:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-03  6:30 jeroen dobbelaere
2002-07-03  8:34 ` Richard Earnshaw
2002-07-03  8:41   ` jeroen dobbelaere
2002-07-03  8:42     ` Richard Earnshaw [this message]
2002-07-03  8:52       ` jeroen dobbelaere
2002-07-04  0:24       ` [patch] " jeroen dobbelaere
2002-07-05  1:36         ` Richard Earnshaw
2002-07-05  2:24           ` jeroen dobbelaere
2002-07-05  2:28             ` Andreas Schwab
2002-07-05  2:44               ` jeroen dobbelaere
2002-07-05  8:07           ` jeroen dobbelaere
2002-07-08  0:50             ` jeroen dobbelaere
2002-07-08  3:42               ` Richard Earnshaw
2002-07-12  0:55                 ` jeroen dobbelaere
2002-07-15  2:26                   ` Richard Earnshaw
2002-07-15  8:36                     ` jeroen dobbelaere
2002-07-15  8:47                       ` Richard Earnshaw
2002-07-16  1:03                         ` jeroen dobbelaere
2002-07-16  9:10                         ` Richard Earnshaw

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=200207031541.QAA13617@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jeroen.dobbelaere@acunia.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).