This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [Ada] Redo handling of consistency check for Optimize_Alignment

From: Arnaud Charlet <charlet at adacore dot com>
To: Andreas Schwab <schwab at suse dot de>
Cc: gcc-patches at gcc dot gnu dot org, Robert Dewar <dewar at adacore dot com>, Gary Dismukes <dismukes at adacore dot com>, Javier Miranda <miranda at adacore dot com>, Ed Schonberg <schonberg at adacore dot com>
Date: Tue, 8 Apr 2008 10:59:16 +0200
Subject: Re: [Ada] Redo handling of consistency check for Optimize_Alignment
References: <20080408083806.GA13263@adacore.com> <je63usg25w.fsf@sykes.suse.de> <20080408085330.GA42446@adacore.com> <je1w5gg1zq.fsf@sykes.suse.de>

> It does not work that way.  *Every* revision must be compilable, or you
> break automatic testers.

Right, I understand that. In some cases it's very hard to do that, although
things will improve soon as we are switching our own repository to subversion,
which will help mapping our changes to FSF changes in a more straightforward
way (currently we are mapping cvs commits to svn commits, which is causing
these temporary glitches).

Arno

References:
- [Ada] Redo handling of consistency check for Optimize_Alignment
  - From: Arnaud Charlet
- Re: [Ada] Redo handling of consistency check for Optimize_Alignment
  - From: Andreas Schwab
- Re: [Ada] Redo handling of consistency check for Optimize_Alignment
  - From: Arnaud Charlet
- Re: [Ada] Redo handling of consistency check for Optimize_Alignment
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]