Red Hat g++ packaging question

[Peter J. Stieber]

I have an Intel Core 2 Quad (Q9650) box running

2.6.27.9-159.fc10.x86_64 #1 SMP

I use C++ and currently have the following compiler loaded...

g++ (GCC) 4.3.2 20081105 (Red Hat 4.3.2-7)

I perform nightly build on the machine and I seem to be getting random
g++ errors...

<BuildLogOutput>
/c++/4.3.2/vector:75,
                   from /usr/local/wx289/include/wx-2.8/wx/dynarray.h:20,
                   from /usr/local/wx289/include/wx-2.8/wx/arrstr.h:24,
                   from /usr/local/wx289/include/wx-2.8/wx/filename.h:27,
                   from
/home/pstieber/SimLibSource/SimLib/Log/ProtoBufLog.cpp:36:
/usr/lib/gcc/x86_64-redhat-linux/4.3.2/../../../../include/c++/4.3.2/bits/vector.tcc: 

In member function ‘void std::vector<_Tp,
_Alloc>::_M_assign_aux(_InputIterator, _InputIterator,
std::input_iterator_tag)’:
/usr/lib/gcc/x86_64-redhat-linux/4.3.2/../../../../include/c++/4.3.2/bits/vector.tcc:210: 

internal compiler error: in cp_parser_lookup_name, at cp/parser.c:16202
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugzilla.redhat.com/bugzilla> for instructions.
The bug is not reproducible, so it is likely a hardware or OS problem.
</BuildLogOutput>

Note that the output says "The bug is not reproducible".  The error 
appears in my build log, but the code was compiled.  It seems as if the 
compiler is built to attempt the compile twice, and it was successful on 
the second attempt.  Is this possible?

I was using ccache running, but I disabled it by setting CCACHE_DISABLE=1.

We have noticed a few bugs in g++ 4.3.2 that have been reported as fixed 
in 4.3.3.  Is there a way to determine if this version will be 
distributed soon?

Is it possible that 4.3.3 will be in Fedora 11 so it isn't going to be 
released in Fedora 10?

How would one determine this?

Thanks in advance,
Pete