I would like to discuss my plans for merging the dfp-branch, which is
nearing completion. I have been merging all of our infrastructure and
non-specific patches into the trunk for the last couple of days. I'm
at a stage where I can't do any more without introducing the DFP
changes.
I have been thinking about a piecemeal way to merge the branch that
ensures that the patches are (a) manageable for reviewers and (b)
don't break the trunk for even a brief period. Our changes will only
be active for a couple of targets (powerpc64-linux and i?86-linux) and
should not be noticed by anyone who isn't interested. :-)
Here is a proposed merge schedule (allowing a day or so between each
step for any breakage to be noticed and fixed):
1. Import decNumber package (a software implementation of decimal
floating point arithmetic) into the gcc directory.
2. Merge in changes to real.{h,c} and its dfp.{h,c} analogue.
3. Merge in libcpp and C (only) front-end changes.
4. Merge in middle-end changes and internals documentation.
5. Merge in i?86 and powerpc64 backend changes. This is the bare
minimum changes required to support mov* patterns and implement
calling conventions.
6. Merge in configury/build system changes for the runtime library.
7. Merge in the testsuite (a collection of standalone tests in
gcc.dg/dfp/ that only run when the compiler under test is
dfp-capable).
Any comments?
Cheers, Ben
