The new gcc-4.0-pre has a better detection of problems with uninitialized
variables and prints the new "warning: FOO is used uninitialized". We are going
through this warnings because there is a higher chance that the code is really
broken.

The following problems were found in the module sch:

/usr/src/packages/BUILD/ooo-build-1.9.100/build/src680-m100/sch/source/ui/dlg/tplabel.cxx:
In member function ‘virtual BOOL SchAxisLabelTabPage::FillItemSet(SfxItemSet&)’:
/usr/src/packages/BUILD/ooo-build-1.9.100/build/src680-m100/sch/source/ui/dlg/tplabel.cxx:174:
warning: ‘eOrient’ is used uninitialized in this function

The variable ‘eOrient’ is used this way:

BOOL SchAxisLabelTabPage::FillItemSet( SfxItemSet& rOutAttrs )
{
        SvxChartTextOrient eOrient;
...
    BOOL bStacked = aOrientHlp.GetStackedState() == STATE_CHECK;
    if( bStacked != m_bInitialStacking )
    {
        if( bStacked )
        {
            eOrient = CHTXTORIENT_STACKED;
            rOutAttrs.Put( SfxInt32Item( SCHATTR_TEXT_DEGREES, 0 ) );
        }
    }
        
    if( eOrient != CHTXTORIENT_STACKED )
        {
...

It is set to CHTXTORIENT_STACKED only in some special cases but it is checked in
all cases. It might look that there is a small chance that the variable is set
to CHTXTORIENT_STACKED by default. I think that the chance is not so small
because the method could be called more times and the value CHTXTORIENT_STACKED
could be saved in the memory stack from the previous call.

I'll attach a patch that initializes the variable.