public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Eric Botcazou <ebotcazou@adacore.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org,  Ian Lance Taylor <iant@google.com>
Subject: Re: Phase 1 of gcc-in-cxx now complete
Date: Thu, 25 Jun 2009 22:47:00 -0000	[thread overview]
Message-ID: <200906260040.32239.ebotcazou@adacore.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0906252215460.15911@digraph.polyomino.org.uk>

> I think the right approach is not documenting observations like that, but
> investigating the causes of failures with older compilers and making it
> build with as wide a range of versions of GCC (and ideally at least one
> non-GCC C++ compiler, probably an EDG-based one such as the Intel
> compiler) as is reasonable.

Yes, I don't think we should require GCC to build GCC, this would be a step 
backwards in my opinion.  I can experiment with the Sun Studio compiler.

-- 
Eric Botcazou

  reply	other threads:[~2009-06-25 22:39 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-25 20:33 Ian Lance Taylor
2009-06-25 21:39 ` Richard Guenther
2009-06-25 22:17 ` Phase 1 of gcc-in-cxx now complete (Ada) Laurent GUERBY
2009-06-25 22:19   ` Richard Guenther
2009-06-25 22:38     ` Ian Lance Taylor
2009-06-26 11:20       ` Laurent GUERBY
2009-06-26 14:48         ` Ian Lance Taylor
2009-06-26 15:36           ` Arnaud Charlet
2009-06-26 15:59           ` Laurent GUERBY
2009-06-26 17:32             ` Ian Lance Taylor
2009-06-26 17:36               ` Arnaud Charlet
2009-06-26 17:38               ` Robert Dewar
2009-06-26 17:59                 ` Arnaud Charlet
2009-06-26 18:07                 ` Ian Lance Taylor
2009-06-26 18:18                   ` Robert Dewar
2009-06-26 19:24                     ` Laurent GUERBY
2009-06-26 19:24                       ` Arnaud Charlet
2009-06-26 23:53                         ` Ian Lance Taylor
2009-06-27 11:24                           ` Laurent GUERBY
2009-06-27 11:54                             ` Eric Botcazou
2009-06-27 12:53                               ` Laurent GUERBY
2009-06-27 13:39                                 ` Laurent GUERBY
2009-06-27 16:14                                 ` Paolo Bonzini
2009-06-27 10:55       ` Eric Botcazou
2009-06-25 22:51   ` Ian Lance Taylor
2009-06-25 22:29 ` Phase 1 of gcc-in-cxx now complete Joseph S. Myers
2009-06-25 22:47   ` Eric Botcazou [this message]
2009-06-25 22:49   ` Joe Buck
2009-06-26  7:09     ` Gabriel Dos Reis
2009-06-26 14:12       ` Jack Howarth
2009-06-26 18:21 ` Adam Nemet
2009-06-27 16:51 ` Adam Nemet
2009-06-27 18:07 ` David Edelsohn
2009-06-27 19:50   ` Sebastian Pop
2009-06-27  0:26 Matt
2009-06-27  9:48 ` Ian Lance Taylor
2009-06-27 10:35   ` Richard Guenther
2009-06-27 13:41     ` Daniel Berlin
2009-06-27 15:19       ` Robert Dewar
2009-06-28  3:09     ` Ian Lance Taylor
2009-06-29 13:10       ` NightStrike
2009-06-29 13:13         ` Andrew Haley
2009-06-29 16:26         ` Gabriel Dos Reis

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=200906260040.32239.ebotcazou@adacore.com \
    --to=ebotcazou@adacore.com \
    --cc=gcc@gcc.gnu.org \
    --cc=iant@google.com \
    --cc=joseph@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).