This is the mail archive of the gcc@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]

gcc2 merge



I've just checked in the long delayed merge from gcc2 snapshot 980929.

The major change brought over in this merge is the initial i18n support for
gcc.

If you've ever thought about calling warn, pedwarn, fatal, fprintf etc, then I
recommend you read ABOUT-GCC-NLS and ABOUT-NLS which describe the basic
concepts.

i18n support is far from complete.  I suspect there's some error/warning
messages we've added that may need to be tweaked.  Each front end will need
to be converted as well as backends which emit any kind of errors/warnings.
Oh what fun.

The "intl" subdirectory itself will probably move out of the gcc directory
at some point in the future.  It can/should be shared across various tools
that already have some i18n support like texinfo, binutils, & gas.


The rs6000/ppc port has not been merged.  The changes from gcc are merely
formatting changes. David Edelson and I are still discussing ways to handle
them.  Hopefully we'll reach an agreement soon.

Aside from i18n the changes for this snapshot were relatively minor.  You
can find the details in FSFChangeLog and a few tidbits in ChangeLog.

The tags "before-merge-gcc2-980929" and "after-merge-gcc2-980929" mark the
state of the tree immediately before and immediately after the merge.

It is possible this merge will introduce some short term instability.  I'm
going to run through a matrix of builds again starting tomorrow night (-O0,
-O2, -O9) to try and sweep out any dusty corners.

jeff


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