From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,1efdd369be089610 X-Google-Attributes: gid103376,public X-Google-Thread: f65d0,bd4d2fccdf730b16 X-Google-Attributes: gidf65d0,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: gnat-3.10 Date: 1997/07/01 Message-ID: #1/1 X-Deja-AN: 253896537 References: Organization: New York University Newsgroups: comp.lang.ada,gnu.gcc Date: 1997-07-01T00:00:00+00:00 List-Id: Corey says <> Generally the patches we supply *should* apply cleanly to the base. That is certainly the intention. When it is not the case, it is a glitch. Right now, the patch situation is quite messy, because of the very large delta between 2.7.1 and 2.8. Virtually all of our gcc patches are incorporated into 2.8, but not all the 2.8 patches are incorporated into our patch file, only the ones that Ada needs. Keeping this straight is not easy, and that is especially true in the case of the many different targets we support. We are expecting gcc 2.8 to be released very soon, and this should greatly simplify the issue of getting the right version of gcc sources and patches (at least for a transitory moment, the GNAT patch file will become empty or very close to it). The current gcc-272.dif is nearly 6000 lines long (this file originall started out as a very small file of a few critical patches). Furthermore, things are more complicated now because of the appearence of the 2.7.2.1 release (this was a kind of semi-official release demanded by the Linux community to fix one not very important bug that got blown out of proportion), so now we need a gcc-2721.dif as well. As I say, these problems should completely disappear when gcc 2.8 is issued. One of the good things here is that all GNAT patches do get reflected in the main GCC sources that FSF develops almost immediately (that's because the developer of these patches, and the maintainer of the FSF version of GCC are the same person :-)