Processed: Re: Bug#278081: gcc-3.3: REGRESSION: Doesn't follow precedence
Processing commands for [EMAIL PROTECTED]: > close 278081 Bug#278081: gcc-3.3: REGRESSION: Doesn't follow precedence 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Adam Majer <[EMAIL PROTECTED]> > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
[Bug bootstrap/18125] bootstrap fails in libstdc++'s configure script, ICE on every C++ conftest.
--- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-24 12:58 --- I think this is related to PR 17919 (or is a dup of that bug). I think this is GC related. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18125 --- You are receiving this mail because: --- You reported the bug, or are watching the reporter.
-pthread inconsistency on some arches
Hi!
It looks like gcc behavior with regard to whether -pthread implies
-lpthread, when -shared is specified, is inconsistent across
architectures.
For example (gcc-3.3) gcc/config/sparc/linux.h has:
#define LIB_SPEC \
"%{pthread:-lpthread} \
%{shared:-lc} \
%{!shared:%{mieee-fp:-lieee} %{profile:-lc_p}%{!profile:-lc}}"
Which seems fine. However gcc/config/mips/linux.h has:
#define LIB_SPEC "\
%{shared: -lc} \
%{!static:-rpath-link %R/lib:%R/usr/lib} \
%{!shared: %{pthread:-lpthread} \
%{profile:-lc_p} %{!profile: -lc}}"
Which, if I read it correctly, makes -pthread a no-op when -shared is
specified.
This behavior causes bugs like http://bugs.debian.org/273671
Thiemo Seufer said in that bug report that changing that behavior on mipsel
would probably cause backward incompatibility. If that is really the case, then
I could add some workaround to ekg source, but would like someone to confirm
that, since it seems odd to me, all the more that a very similar (if not
identical) bug was fixed last year by Daniel Jacobowitz for powerpc
http://lists.debian.org/debian-gcc/2003/09/msg00145.html
His two changes to gcc/config/rs6000/sysv4.h basically moved
%{pthread:-lpthread} from within %{!shared:}, so that it took action for the
cases when -shared was specified as well.
regards,
Marcin
--
Marcin Owsiany <[EMAIL PROTECTED]> http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216 FE67 DA2D 0ACA FC5E 3F75 D6F6 3A0D 8AA0 60F4 1216
Bug#278081: gcc-3.3: REGRESSION: Doesn't follow precedence
Package: gcc-3.3
Version: 1:3.3.5-1
Severity: important
IMHO, this bug should be grave since it has a potential for
breaking a lot of software, at least anything that
depends on things like stack operations. That is
stack A;
A.push(5);
A.push(2);
// do a subtraction of 5-2 and push resuls onto stack
A.push( -A.pop() + A.pop());
What it does, it actually A.pop() - A.pop() which is very wrong.
I can reproduce this problem on both gcc 3.3 (default) and gcc 3.4.
gcc 2.95 in woody compiles this code correctly, hence this is a regression.
You can rearrange -X+Y, as well as -X()+Y or -X+Y(), but you cannot do
this for -X()+Y() unless you can guarantee that X() doesn't depend on
Y() and vice-versa.
The following test case will also illustrate this problem. Hopefully
this regression doesn't translate to stable...
>TEST CASE >>
#include
double A(){
static int div;
double r = 10.0/++div+div;
printf( "A() returns: %f iteration %d\n", r, div );
return r;
}
int main()
{
/* EXECUTES A()-A() INSTEAD OF -A()+A() */
printf( "-4.0 is %f\n", -A() + A());
}
<<
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages gcc-3.3 depends on:
ii binutils2.15-4 The GNU assembler, linker and bina
ii cpp-3.3 1:3.3.5-1The GNU C preprocessor
ii gcc-3.3-base1:3.3.5-1The GNU Compiler Collection (base
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libgcc1 1:3.4.2-3GCC support library
-- no debconf information
Bug#278081: (gcc-3.3: REGRESSION: Doesn't follow precedence)
I reported it upstream to, http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18128 - Adam -- Building your applications one byte at a time http://www.galacticasoftware.com
Bug#278081: gcc-3.3: REGRESSION: Doesn't follow precedence
On Sun, Oct 24, 2004 at 01:42:02PM -0500, Adam Majer wrote: > You can rearrange -X+Y, as well as -X()+Y or -X+Y(), but you cannot do > this for -X()+Y() unless you can guarantee that X() doesn't depend on > Y() and vice-versa. Could you quote standard chapter and verse for this? I believe you are incorrect. While the function calls are sequence points, they are not defined to happen in any particular order. >From ISO C 6.5#3: [#3] The grouping of operators and operands is indicated by the syntax. Except as specified later (for the function- call (), &&, ||, ?:, and comma operators), the order of evaluation of subexpressions and the order in which side effects take place are both unspecified. I don't have ISO C++ handy but I believe it is worded similarly. -- Daniel Jacobowitz
Bug#278081: gcc-3.3: REGRESSION: Doesn't follow precedence
close 278081 thanks Daniel Jacobowitz wrote: >On Sun, Oct 24, 2004 at 01:42:02PM -0500, Adam Majer wrote: > > >>You can rearrange -X+Y, as well as -X()+Y or -X+Y(), but you cannot do >>this for -X()+Y() unless you can guarantee that X() doesn't depend on >>Y() and vice-versa. >> >> > >Could you quote standard chapter and verse for this? I believe you are >incorrect. While the function calls are sequence points, they are not >defined to happen in any particular order. > >>From ISO C 6.5#3: > [#3] The grouping of operators and operands is indicated by > the syntax. Except as specified later (for the function- > call (), &&, ||, ?:, and comma operators), the order of > evaluation of subexpressions and the order in which side > effects take place are both unspecified. > >I don't have ISO C++ handy but I believe it is worded similarly. > > Well, upstream already marked the bug as "INVALID RESOLVED"... Anyway, I do remember that the precedence occurs as in order (for above example) unary - + - I would expect X() and Y() to be undetermined until actually evaluated. That is, -X()+Y() -x+Y(), where x=evaluated X() x'+Y(), where x' = -x x'+y, where y=evaluated Y() According to upstream (and ISO C), -X()+Y() can be evaluated as, -X()+Y() -X()+y -x+y x'+y This essentially means that precedence is not followed if Y depends on X or vice-versa. Blah Now I have to go and rewrite some code... - Adam -- Building your applications one byte at a time http://www.galacticasoftware.com
Bug#278081: gcc-3.3: REGRESSION: Doesn't follow precedence
On Sun, Oct 24, 2004 at 02:31:54PM -0500, Adam Majer wrote: > Anyway, I do remember that the precedence occurs as in order (for above > example) > > unary - > + - > > I would expect X() and Y() to be undetermined until actually evaluated. > That is, > > -X()+Y() > -x+Y(), where x=evaluated X() > x'+Y(), where x' = -x > x'+y, where y=evaluated Y() > > According to upstream (and ISO C), -X()+Y() can be evaluated as, > > -X()+Y() > -X()+y > -x+y > x'+y > > This essentially means that precedence is not followed if Y depends on X > or vice-versa. > > Blah Now I have to go and rewrite some code... This isn't a question of precedence, which only affects the way an expression is interpreted. It's strictly a problem of evaluation order. Precedence determines how the expression is parsed, i.e. (-X()) + Y() vs (-X() + Y) () an so forth. -- Daniel Jacobowitz
Bug#277852: gcc-3.4: Please replace 'lib64' with 'lib' in gcc/config/i386/linux64.h on amd64
On Fri, Oct 22, 2004 at 11:18:23PM +0200, Andreas Jochens wrote:
> Package: gcc-3.4
> Severity: wishlist
> Tags: patch
>
> The attached patch changes the directory that gcc-3.4 uses to locate the
> dynamic linker on amd64 from 'lib64' to 'lib'. This is one of the last
> few places where the ugly 'lib64' directory is still used on amd64.
> The dynamic linker is installed in the 'lib' directory by the 'libc6'
> package and this location should also be used by gcc-3.4.
>
> The current usage of 'lib64' in the dynamic linker name makes it very easy
> to make the whole system completely unusable by just removing the 'lib64'
> directory symlink. There have already been a few complaints from people who
> ran into this problem (e.g. someone removed the 'lib64' symlink
> because he wanted to create a separate real 'lib64' directory
> to install some non-free binary-only software which required this).
> +- %{!m32:%{!dynamic-linker:-dynamic-linker
> /lib64/ld-linux-x86-64.so.2}}} \
> ++ %{!m32:%{!dynamic-linker:-dynamic-linker /lib/ld-linux-x86-64.so.2}}}
> \
Um, no.
I am aware that the amd64 port has decided to completely ignore
standard methods of handling the multi-arch issues. However, most of
the other changes are compatible as long as some constructs (e.g.
rpath) are not used. The choice of dynamic loader is not one such.
The ABI specifies:
5.2.1Program Interpreter
There is one valid program interpreter for programs conforming to the
AMD64 ABI:
/lib/ld64.so.1
However, Linux puts this in
/lib64/ld-linux-x86-64.so.2
Debian should not have a different ABI than the rest of the planet.
If you want it to live in /lib, talk to other distributions about
switching to /lib/ld64.so.1 instead.
--
Daniel Jacobowitz
Re: follows me and keeps
Congratulations! You are a winner of our summer RA.TE. GIVE A WAY program. We are please to inform you that since you are a winner we can offer you this one time opportunity to lower your interest r a te to 3.99 percent. Your promotion code is 5616 Activate your code http://www.neoplad.com/ Thank you. Coleman Matthews Promotion Department
Bug#278081: gcc-3.3: REGRESSION: Doesn't follow precedence
Daniel Jacobowitz wrote: >This isn't a question of precedence, which only affects the way an >expression is interpreted. It's strictly a problem of evaluation >order. Precedence determines how the expression is parsed, i.e. >(-X()) + Y() vs (-X() + Y) () an so forth. > > I guess this is much easier on the compiler. In most cases it can optimize the code better than it could do otherwise. For example, -sin(5)+sqrt(5) -> sqrt(5)-sin(5) Does mess things up for people that think (or thought) that order of precedence is equal to order of evaluation. :) - Adam -- Building your applications one byte at a time http://www.galacticasoftware.com
Bug#277852: gcc-3.4: Please replace 'lib64' with 'lib' in gcc/config/i386/linux64.h on amd64
On 04-Oct-24 16:26, Daniel Jacobowitz wrote: > I am aware that the amd64 port has decided to completely ignore > standard methods of handling the multi-arch issues. However, most of > the other changes are compatible as long as some constructs (e.g. > rpath) are not used. The choice of dynamic loader is not one such. > The ABI specifies: > > 5.2.1Program Interpreter > > There is one valid program interpreter for programs conforming to the > AMD64 ABI: >/lib/ld64.so.1 > However, Linux puts this in >/lib64/ld-linux-x86-64.so.2 > > Debian should not have a different ABI than the rest of the planet. > If you want it to live in /lib, talk to other distributions about > switching to /lib/ld64.so.1 instead. Thank you for your reply to my report. The '/lib64' directory is just ugly and I want to get rid of that or at least minimize its use (and I think I am not alone here). To achive that, I recompiled the complete amd64/gcc-3.4 archive using this patch and without the '/lib64' symlink in place. The result is that the '/lib64' symlink may now be dropped without doing any harm. Before that, the whole system stopped working when the '/lib64' symlink was removed. I think it is not a good decision to hard code the '/lib64' directory into nearly every binary on the system, because this directory will likely become deprecated or may even be dropped at a later time. I do not want to wait for other distributions to switch to a reasonable standard. Debian should go ahead here and choose a reasonable standard from the beginning (but of course, it is not up to me to decide that). Most multi-arch proposals I know of use '/lib/ld-linux-x86-64.so.2' as the interpreter name. Furthermore the current 'glibc' package already installs the interpreter at this location (Gentoo libc does the same IIRC). This is why I choose '/lib/ld-linux-x86-64.so.2' and not '/lib/ld64.so.1'. Regards Andreas Jochens
Bug#278105: gcc-defaults: Make a libgcj-dev defaults package
Package: gcc-defaults Severity: wishlist Version: 1.18 Since gcj-3.* no longer depend on the corresponding libgcj*-dev packages, many packages have "gcj, libgcj4-dev" Build-Depends in their control files, which will break when the default version of gcj changes. It would be nice if these packages could instead Build-Depend on "gcj, libgcj-dev" and thus be ensured of getting the correct version. -- Daniel Schepler "Please don't disillusion me. I [EMAIL PROTECTED]haven't had breakfast yet." -- Orson Scott Card
[Bug java/2499] Class members should be inherited from implemented interfaces
-- What|Removed |Added OtherBugsDependingO||18131 nThis|| http://gcc.gnu.org/bugzilla/show_bug.cgi?id=2499 --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
Bug#277852: gcc-3.4: Please replace 'lib64' with 'lib' in gcc/config/i386/linux64.h on amd64
On Sun, Oct 24, 2004 at 11:08:22PM +0200, Andreas Jochens wrote: > On 04-Oct-24 16:26, Daniel Jacobowitz wrote: > > I am aware that the amd64 port has decided to completely ignore > > standard methods of handling the multi-arch issues. However, most of > > the other changes are compatible as long as some constructs (e.g. > > rpath) are not used. The choice of dynamic loader is not one such. > > The ABI specifies: > > > > 5.2.1Program Interpreter > > > > There is one valid program interpreter for programs conforming to the > > AMD64 ABI: > >/lib/ld64.so.1 > > However, Linux puts this in > >/lib64/ld-linux-x86-64.so.2 > > > > Debian should not have a different ABI than the rest of the planet. > > If you want it to live in /lib, talk to other distributions about > > switching to /lib/ld64.so.1 instead. > > Thank you for your reply to my report. > > The '/lib64' directory is just ugly and I want to get rid of that > or at least minimize its use (and I think I am not alone here). You're certainly not alone among the Debian amd64 team. I think you, as a group, are alone in the larger world. I find /lib64 a fairly elegant solution. There is a community list on which x86_64 ABI issues can be discussed. None of the Debian porters have ever come to talk about their objections to the layout there. If you seriously intend to change the ABI, then someone ought to have done that by now. > I think it is not a good decision to hard code the '/lib64' directory > into nearly every binary on the system, because this directory will > likely become deprecated or may even be dropped at a later time. > I do not want to wait for other distributions to switch to a reasonable > standard. Debian should go ahead here and choose a reasonable standard > from the beginning (but of course, it is not up to me to decide that). Sorry, but in the real world that's not how ABI problems get solved - only how they get created. -- Daniel Jacobowitz
Results for 3.3.5 (Debian 1:3.3.5-2) testsuite on hppa-linux
LAST_UPDATED: Native configuration is hppa-linux (pampa) === gpc tests === Running target any === gpc Summary === # of tests3910 # of expected passes 3905 # of unsupported tests5 /build/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/xgpc version 20040516, based on gcc-3.3.5 (Debian 1:3.3.5-2) === g++ tests === Running target unix FAIL: g++.dg/compat/break/bitfield7 x_tst.o compile UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o link UNRESOLVED: g++.dg/compat/break/bitfield7 x_tst.o-y_tst.o execute XPASS: g++.dg/other/packed1.C execution test XPASS: g++.other/init5.C Execution test === g++ Summary === # of expected passes8177 # of unexpected failures1 # of unexpected successes 2 # of expected failures 97 # of unresolved testcases 2 # of untested testcases 23 # of unsupported tests 30 /build/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/testsuite/../g++ version 3.3.5 (Debian 1:3.3.5-2) === g77 tests === Running target unix === g77 Summary === # of expected passes1720 # of unsupported tests 8 /build/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/testsuite/../g77 version 3.3.5 (Debian 1:3.3.5-2) === gcc tests === Running target unix FAIL: gcc.dg/duff-2.c (test for excess errors) === gcc Summary === # of expected passes21167 # of unexpected failures1 # of expected failures 67 # of unsupported tests 198 /build/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/xgcc version 3.3.5 (Debian 1:3.3.5-2) === objc tests === Running target unix === objc Summary === # of expected passes1166 /build/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/xgcc version 3.3.5 (Debian 1:3.3.5-2) === treelang tests === Running target unix === treelang Summary === # of expected passes1 === libjava tests === Running target unix FAIL: calls run FAIL: cxxtest run FAIL: field run FAIL: final_method run FAIL: findclass run FAIL: invoke run FAIL: martin run FAIL: noclass run FAIL: overload run FAIL: register run FAIL: simple_int run FAIL: throwit run FAIL: virtual run FAIL: ArrayStore execution - source compiled test FAIL: ArrayStore execution - gij test FAIL: ArrayStore execution - bytecode->native test FAIL: ArrayStore -O execution - source compiled test FAIL: ArrayStore execution - gij test FAIL: ArrayStore -O execution - bytecode->native test FAIL: ArrayStore2 execution - source compiled test FAIL: ArrayStore2 execution - gij test FAIL: ArrayStore2 execution - bytecode->native test FAIL: ArrayStore2 -O execution - source compiled test FAIL: ArrayStore2 execution - gij test FAIL: ArrayStore2 -O execution - bytecode->native test FAIL: Array_1 execution - source compiled test FAIL: Array_1 execution - gij test FAIL: Array_1 execution - bytecode->native test FAIL: Array_1 -O execution - source compiled test FAIL: Array_1 execution - gij test FAIL: Array_1 -O execution - bytecode->native test FAIL: Array_2 execution - source compiled test FAIL: Array_2 execution - gij test FAIL: Array_2 execution - bytecode->native test FAIL: Array_2 -O execution - source compiled test FAIL: Array_2 execution - gij test FAIL: Array_2 -O execution - bytecode->native test FAIL: Array_3 execution - source compiled test FAIL: Array_3 execution - gij test FAIL: Array_3 execution - bytecode->native test FAIL: Array_3 -O execution - source compiled test FAIL: Array_3 execution - gij test FAIL: Array_3 -O execution - bytecode->native test FAIL: Class_1 execution - source compiled test FAIL: Class_1 execution - gij test FAIL: Class_1 execution - bytecode->native test FAIL: Class_1 -O execution - source compiled test FAIL: Class_1 execution - gij test FAIL: Class_1 -O execution - bytecode->native test FAIL: Divide_1 execution - source compiled test FAIL: Divide_1 execution - gij test FAIL: Divide_1 execution - bytecode->native test FAIL: Divide_1 -O execution - source compiled test FAIL: Divide_1 execution - gij test FAIL: Divide_1 -O execution - bytecode->native test FAIL: EvaluationOrder execution - source compiled test FAIL: EvaluationOrder execution - gij test FAIL: EvaluationOrder execution - bytecode->native test FAIL: EvaluationOrder -O execution - source compiled test FAIL: EvaluationOrder execution - gij test FAIL: EvaluationOrder -O execution - bytecode->native test FAIL: FileHandleGcTest execution - source compiled test FAIL: FileHandleGcTest execution - gij test FAIL: FileHandleGcTest execution - bytecode->native test FAIL: FileHandleGcTest -O execution - source compiled test FAIL: FileHandleGcTest execution - gij test FAIL: FileHandleGcTest -O execution - bytecode->native test FAIL: Final execution - source compiled test FAIL: Final execution - gij test FAIL: Final execution
Results for 3.3.5 (Debian 1:3.3.5-2) testsuite on i486-linux
LAST_UPDATED: Native configuration is i486-linux (cachaca) === gpc tests === Running target any === gpc Summary === # of tests3910 # of expected passes 3909 # of unsupported tests1 /home/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/xgpc version 20040516, based on gcc-3.3.5 (Debian 1:3.3.5-2) === g++ tests === Running target unix XPASS: g++.other/init5.C Execution test === g++ Summary === # of expected passes8256 # of unexpected successes 1 # of expected failures 97 # of untested testcases 9 # of unsupported tests 15 /home/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/testsuite/../g++ version 3.3.5 (Debian 1:3.3.5-2) === g77 tests === Running target unix === g77 Summary === # of expected passes1720 # of unsupported tests 8 /home/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/testsuite/../g77 version 3.3.5 (Debian 1:3.3.5-2) === gcc tests === Running target unix FAIL: gcc.dg/duff-2.c (test for excess errors) === gcc Summary === # of expected passes21452 # of unexpected failures1 # of expected failures 69 # of unsupported tests 101 /home/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/xgcc version 3.3.5 (Debian 1:3.3.5-2) === objc tests === Running target unix === objc Summary === # of expected passes1166 /home/packages/gcc/3.3/gcc-3.3-3.3.5/build/gcc/xgcc version 3.3.5 (Debian 1:3.3.5-2) === treelang tests === Running target unix === treelang Summary === # of expected passes1 === libjava tests === Running target unix FAIL: cxxtest output WARNING: program timed out. FAIL: SyncTest execution - gij test WARNING: program timed out. FAIL: SyncTest execution - gij test === libjava Summary === # of expected passes2986 # of unexpected failures3 # of expected failures 16 # of untested testcases 14 === libstdc++-v3 check-abi Summary === # of added symbols: 51 # of missing symbols:0 # of incompatible symbols: 0 using: /home/packages/gcc/3.3/gcc-3.3-3.3.5/src/libstdc++-v3/config/abi/i486-linux-gnu/baseline_symbols.txt === libstdc++-v3 tests === Running target unix XPASS: 22_locale/collate_byname.cc execution test XPASS: 22_locale/collate_members_char.cc execution test XPASS: 22_locale/collate_members_wchar_t.cc execution test XPASS: 22_locale/ctype_is_char.cc execution test XPASS: 22_locale/ctype_is_wchar_t.cc execution test XPASS: 22_locale/members.cc execution test XPASS: 22_locale/messages_byname.cc execution test XPASS: 22_locale/messages_members_char.cc execution test XPASS: 22_locale/money_get_members_char.cc execution test XPASS: 22_locale/money_get_members_wchar_t.cc execution test XPASS: 22_locale/money_put_members_char.cc execution test XPASS: 22_locale/money_put_members_wchar_t.cc execution test XPASS: 22_locale/moneypunct_byname.cc execution test XPASS: 22_locale/moneypunct_members_char.cc execution test XPASS: 22_locale/moneypunct_members_wchar_t.cc execution test XPASS: 22_locale/num_get_members_char.cc execution test XPASS: 22_locale/num_get_members_wchar_t.cc execution test XPASS: 22_locale/num_put_members_char.cc execution test XPASS: 22_locale/num_put_members_wchar_t.cc execution test XPASS: 22_locale/numpunct_byname.cc execution test XPASS: 22_locale/numpunct_members_char.cc execution test XPASS: 22_locale/numpunct_members_wchar_t.cc execution test XPASS: 22_locale/time_get_members_char.cc execution test XPASS: 22_locale/time_get_members_wchar_t.cc execution test XPASS: 22_locale/time_put_members_char.cc execution test XPASS: 22_locale/time_put_members_wchar_t.cc execution test === libstdc++-v3 Summary === # of expected passes453 # of unexpected successes 26 # of expected failures 2 Compiler version: 3.3.5 (Debian 1:3.3.5-2) Platform: i486-linux configure flags: --host=i486-linux -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib --enable-nls --without-included-gettext --enable-__cxa_atexit --enable-clocale=gnu --enable-debug --enable-java-gc=boehm --enable-java-awt=xlib --enable-objc-gc BOOT_CFLAGS=-g -O2 Build Dependencies: Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii binutils 2.15-4 The GNU assembler, linker and
Results for 3.3.5 (Debian 1:3.3.5-2) testsuite on ia64-linux
LAST_UPDATED: Native configuration is ia64-linux (caballero) === gpc tests === Running target any FAIL: arctan.pas FAIL: fjf512.pas FAIL: fjf762a.pas FAIL: math.pas === gpc Summary === # of tests3910 # of expected passes 3903 # of unexpected failures 4 # of unsupported tests3 /build/buildd/gcc-3.3-3.3.5/build/gcc/xgpc version 20040516, based on gcc-3.3.5 (Debian 1:3.3.5-2) === g++ tests === Running target unix XPASS: g++.other/init5.C Execution test === g++ Summary === # of expected passes7973 # of unexpected successes 1 # of expected failures 97 # of untested testcases 23 # of unsupported tests 28 /build/buildd/gcc-3.3-3.3.5/build/gcc/testsuite/../g++ version 3.3.5 (Debian 1:3.3.5-2) === g77 tests === Running target unix === g77 Summary === # of expected passes1720 # of unsupported tests 8 /build/buildd/gcc-3.3-3.3.5/build/gcc/testsuite/../g77 version 3.3.5 (Debian 1:3.3.5-2) === gcc tests === Running target unix XPASS: gcc.c-torture/execute/20020227-1.c execution, -O0 FAIL: gcc.c-torture/execute/20020227-1.c compilation, -O2 UNRESOLVED: gcc.c-torture/execute/20020227-1.c execution, -O2 FAIL: gcc.c-torture/execute/20020227-1.c compilation, -O3 -fomit-frame-pointer UNRESOLVED: gcc.c-torture/execute/20020227-1.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/20020227-1.c compilation, -O3 -g UNRESOLVED: gcc.c-torture/execute/20020227-1.c execution, -O3 -g FAIL: gcc.c-torture/execute/20020227-1.c compilation, -Os UNRESOLVED: gcc.c-torture/execute/20020227-1.c execution, -Os FAIL: gcc.dg/duff-2.c (test for excess errors) FAIL: gcc.dg/special/gcsec-1.c -ffunction-sections -fdata-sections -Wl,--gc-sections -static (test for excess errors) === gcc Summary === # of expected passes20866 # of unexpected failures6 # of unexpected successes 1 # of expected failures 78 # of unresolved testcases 4 # of unsupported tests 186 /build/buildd/gcc-3.3-3.3.5/build/gcc/xgcc version 3.3.5 (Debian 1:3.3.5-2) === objc tests === Running target unix === objc Summary === # of expected passes1166 /build/buildd/gcc-3.3-3.3.5/build/gcc/xgcc version 3.3.5 (Debian 1:3.3.5-2) === treelang tests === Running target unix === treelang Summary === # of expected passes1 === libjava tests === Running target unix === libjava Summary === # of expected passes2991 # of expected failures 16 # of untested testcases 12 === libstdc++-v3 check-abi Summary === # of added symbols: 78 # of missing symbols:0 # of incompatible symbols: 0 using: /build/buildd/gcc-3.3-3.3.5/src/libstdc++-v3/config/abi/ia64-linux-gnu/baseline_symbols.txt === libstdc++-v3 tests === Running target unix XPASS: 22_locale/collate_byname.cc execution test XPASS: 22_locale/collate_members_char.cc execution test XPASS: 22_locale/collate_members_wchar_t.cc execution test XPASS: 22_locale/ctype_is_char.cc execution test XPASS: 22_locale/ctype_is_wchar_t.cc execution test XPASS: 22_locale/members.cc execution test XPASS: 22_locale/messages_byname.cc execution test XPASS: 22_locale/messages_members_char.cc execution test XPASS: 22_locale/money_get_members_char.cc execution test XPASS: 22_locale/money_get_members_wchar_t.cc execution test XPASS: 22_locale/money_put_members_char.cc execution test XPASS: 22_locale/money_put_members_wchar_t.cc execution test XPASS: 22_locale/moneypunct_byname.cc execution test XPASS: 22_locale/moneypunct_members_char.cc execution test XPASS: 22_locale/moneypunct_members_wchar_t.cc execution test XPASS: 22_locale/num_get_members_char.cc execution test XPASS: 22_locale/num_get_members_wchar_t.cc execution test XPASS: 22_locale/num_put_members_char.cc execution test XPASS: 22_locale/numpunct_byname.cc execution test XPASS: 22_locale/numpunct_members_char.cc execution test XPASS: 22_locale/numpunct_members_wchar_t.cc execution test XPASS: 22_locale/time_get_members_char.cc execution test XPASS: 22_locale/time_get_members_wchar_t.cc execution test XPASS: 22_locale/time_put_members_char.cc execution test XPASS: 22_locale/time_put_members_wchar_t.cc execution test === libstdc++-v3 Summary === # of expected passes453 # of unexpected successes 25 # of expected failures 3 Compiler version: 3.3.5 (Debian 1:3.3.5-2) Platform: ia64-linux configure flags: --host=ia64-linux -v --enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib
Results for 3.3.5 (Debian 1:3.3.5-1) testsuite on m68k-linux
LAST_UPDATED: Native configuration is m68k-linux (crest) === gpc tests === Running target any FAIL: assumptions.pas FAIL: capexp.pas FAIL: cfor.pas FAIL: emil11a.pas FAIL: emil11b.pas FAIL: emil11c.pas FAIL: emil11d.pas FAIL: expotst.pas FAIL: fjf129.pas FAIL: fjf170.pas FAIL: fjf227a.pas FAIL: fjf227b.pas FAIL: fjf629g.pas FAIL: fjf74.pas FAIL: fnested.pas FAIL: funcs.pas FAIL: gmptest.pas FAIL: hugereal.pas FAIL: ian7.pas FAIL: kevin9.pas FAIL: knuth1.pas FAIL: knuth1a.pas FAIL: longr1.pas FAIL: longr2.pas FAIL: miklos5.pas FAIL: miklos7.pas FAIL: nmaze.pas FAIL: numericio.pas FAIL: permute.pas FAIL: piconst.pas FAIL: random.pas FAIL: real.pas FAIL: realout.pas FAIL: rick1.pas FAIL: robert1a.pas FAIL: robert1b.pas FAIL: scaltst.pas FAIL: schema1.pas FAIL: sven15.pas FAIL: sven9.pas FAIL: t01.pas FAIL: t03.pas FAIL: t05.pas FAIL: t06.pas FAIL: t07.pas FAIL: t08.pas FAIL: t10.pas FAIL: t12.pas FAIL: t17.pas FAIL: t18.pas FAIL: testio.pas FAIL: writeb.pas FAIL: writec.pas FAIL: writee.pas FAIL: writeg.pas FAIL: writereal.pas === gpc Summary === # of tests3910 # of expected passes 3851 # of unexpected failures 56 # of unsupported tests3 /home/doko/gcc/gcc-3.3-3.3.5/build/gcc/xgpc version 20040516, based on gcc-3.3.5 (Debian 1:3.3.5-1) === g++ tests === Running target unix FAIL: g++.dg/abi/bitfield4.C execution test FAIL: g++.dg/abi/empty6.C (test for warnings, line 6) FAIL: g++.eh/spec3.C Execution test FAIL: g++.eh/spec4.C Execution test XPASS: g++.other/init5.C Execution test === g++ Summary === # of expected passes8177 # of unexpected failures4 # of unexpected successes 1 # of expected failures 97 # of untested testcases 23 # of unsupported tests 30 /home/doko/gcc/gcc-3.3-3.3.5/build/gcc/testsuite/../g++ version 3.3.5 (Debian 1:3.3.5-1) === g77 tests === Running target unix === g77 Summary === # of expected passes1720 # of unsupported tests 8 /home/doko/gcc/gcc-3.3-3.3.5/build/gcc/testsuite/../g77 version 3.3.5 (Debian 1:3.3.5-1) === gcc tests === Running target unix WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O1 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O2 WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -fomit-frame-pointer WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -O3 -g WARNING: program timed out. FAIL: gcc.c-torture/compile/20001226-1.c, -Os FAIL: gcc.c-torture/execute/20020418-1.c execution, -O2 FAIL: gcc.c-torture/execute/20020418-1.c execution, -Os FAIL: gcc.c-torture/execute/930622-2.c execution, -O0 FAIL: gcc.c-torture/execute/930622-2.c execution, -O1 FAIL: gcc.c-torture/execute/930622-2.c execution, -O2 FAIL: gcc.c-torture/execute/930622-2.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/930622-2.c execution, -O3 -g FAIL: gcc.c-torture/execute/930622-2.c execution, -Os FAIL: gcc.c-torture/execute/conversion.c execution, -O0 FAIL: gcc.c-torture/execute/conversion.c execution, -O1 FAIL: gcc.c-torture/execute/conversion.c execution, -O2 FAIL: gcc.c-torture/execute/conversion.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/conversion.c execution, -O3 -g FAIL: gcc.c-torture/execute/conversion.c execution, -Os FAIL: gcc.c-torture/execute/loop-2f.c execution, -O0 FAIL: gcc.c-torture/execute/loop-2f.c execution, -O1 FAIL: gcc.c-torture/execute/loop-2f.c execution, -O2 FAIL: gcc.c-torture/execute/loop-2f.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/loop-2f.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/loop-2f.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: gcc.c-torture/execute/loop-2f.c execution, -O3 -g FAIL: gcc.c-torture/execute/loop-2f.c execution, -Os FAIL: gcc.c-torture/execute/loop-2g.c execution, -O0 FAIL: gcc.c-torture/execute/loop-2g.c execution, -O1 FAIL: gcc.c-torture/execute/loop-2g.c execution, -O2 FAIL: gcc.c-torture/execute/loop-2g.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/loop-2g.c execution, -O3 -fomit-frame-pointer -funroll-loops FAIL: gcc.c-torture/execute/loop-2g.c execution, -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions FAIL: gcc.c-torture/execute/loop-2g.c execution, -O3 -g FAIL: gcc.c-torture/execute/loop-2g.c execution, -Os FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O0 FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O1 FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O2 FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O3 -fomit-frame-pointer FAIL: gcc.c-torture/execute/string-opt-10.c execution, -O3 -g FAIL: gcc.c-torture/execute/string-opt-10.c execut
