Processed: tagging bugs that are closed by packages in NEW as pending

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> # Sat Apr  5 08:03:17 UTC 2008
> # The following bugs are closed by packages in NEW
> # http://ftp-master.debian.org/new.html
> #
> # Source package in New: postgresql-pljava
> tags 474084 + pending
Bug#474084: postgresql-8.1-pljava-gcj: new version available
There were no tags set.
Tags added: pending

> # Source package in New: libnet-tftp-ruby
> tags 438065 + pending
Bug#438065: ITP: libnet-tftp-ruby -- This is a pure Ruby  implementation of 
TFTP.
There were no tags set.
Tags added: pending

> # Source package in New: libferret-ruby
> tags 439847 + pending
Bug#439847: ITP: libferret-ruby -- full-text search engine library for Ruby
There were no tags set.
Tags added: pending

> # Source package in New: libffi
> tags 474049 + pending
Bug#474049: Please support MIPS triarch.
Tags were: patch
Tags added: pending

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: gcc-4.3 is default now

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 413432 serious
Bug#413432: FTBFS with GCC 4.3: 'LONG_MIN' was not declared in this scope
Severity set to `serious' from `important'

> severity 417061 serious
Bug#417061: FTBFS with GCC 4.3: identifier 'static_assert' will become a 
keyword in C++0x
Severity set to `serious' from `important'

> severity 417062 serious
Bug#417062: FTBFS with GCC 4.3: first argument of 'int main...' should be...
Severity set to `serious' from `important'

> severity 417104 serious
Bug#417104: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417133 serious
Bug#417133: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417161 serious
Bug#417161: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417209 serious
Bug#417209: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417289 serious
Bug#417289: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417363 serious
Bug#417363: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417382 serious
Bug#417382: FTBFS with gcc-4.3
Severity set to `serious' from `important'

> severity 417437 serious
Bug#417437: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417489 serious
Bug#417489: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417713 serious
Bug#417713: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 417723 serious
Bug#417723: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 420920 serious
Bug#420920: libtorrent: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 425544 serious
Bug#425544: FTBFS with GCC 4.3: inf loop checking for mktime
Severity set to `serious' from `important'

> severity 441064 serious
Bug#441064: FTBFS with GCC 4.3: 'asm' operand has impossible constraints
Severity set to `serious' from `important'

> severity 441532 serious
Bug#441532: ftbfs with g++-4.3/gcc-snapshot
Severity set to `serious' from `important'

> severity 441594 serious
Bug#441594: ftbfs with g++-4.3/gcc-snapshot
Severity set to `serious' from `important'

> severity 452310 serious
Bug#452310: aspell: Fix possible FTBFS with gcc-4.3
Severity set to `serious' from `important'

> severity 454817 serious
Bug#454817: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 454830 serious
Bug#454830: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 454836 serious
Bug#454836: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 454841 serious
Bug#454841: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 454856 serious
Bug#454856: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 454867 serious
Bug#454867: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 454872 serious
Bug#454872: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 454879 serious
Bug#454879: FTBFS with GCC 4.3: duplicate function parameters
Severity set to `serious' from `important'

> severity 454880 serious
Bug#454880: FTBFS with GCC 4.3: duplicate function parameters
Severity set to `serious' from `important'

> severity 454889 serious
Bug#454889: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455129 serious
Bug#455129: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455174 serious
Bug#455174: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455285 serious
Bug#455285: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455286 serious
Bug#455286: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455287 serious
Bug#455287: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455332 serious
Bug#455332: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455336 serious
Bug#455336: FTBFS with GCC 4.3: ... has a previous declaration here
Severity set to `serious' from `important'

> severity 455354 serious
Bug#455354: FTBFS with GCC 4.3: anonymous variadic macros were introduced in C99
Severity set to `serious' from `important'

> severity 455377 serious
Bug#455377: FTBFS with GCC 4.3: missing #includes
Severity set to `serious' from `important'

> severity 455380 serious
Bug#455380: FTBFS with GCC 4.3: missing #includes
Severity set to `

Processed: Re: Bug#474428: setools - FTBFS: Error: symbol `fstatat64' is already defined

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 474428 gcc
Bug#474428: setools - FTBFS: Error: symbol `fstatat64' is already defined
Bug reassigned from package `setools' to `gcc'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Hmm. perhaps this is a setools issue after all.

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 474428 settols
Bug#474428: setools - FTBFS: Error: symbol `fstatat64' is already defined
Warning: Unknown package 'settols'
Bug reassigned from package `gcc' to `settols'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: erlang violates strict-aliasing rules

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 472554 erlang 1:12.b.1-dfsg-4
Bug#472554: erlang: FTBFS with gcc-4.3 [i386, amd64]: erlc segfaults
Bug reassigned from package `gcc-4.3' to `erlang'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[alpha, amd64, hppa, i386] GCC-4.3 as the default compilers for lenny?

[Riku Voipio]

Hi,

Having gcc-4.2 as default on i386 and amd64, while most other
architectures have gcc-4.3 means most maintainers never test their
packages with gcc-4.3. This is making life miserable for those ports
that actually use gcc-4.3:

1) people upload packages with known gcc-4.3 bugs and not bothering
to fix them.

2) people applying gcc 4.3 bugfixes without actually testing them with
gcc-4.3. Often these turn out to be incomplete fixes.

On Sun, Mar 23, 2008 at 08:30:54PM +0100, Pierre Habouzit wrote:
>   Sigh, could we avoid the same discussion over and over, people are not
> supposed (we never asked it in the past, and I see no valid reason to do
> so) to update to the last stable point release before upgrading to
> stable+1.

Dist-upgrade will not fail due to people still having this bug in their
kernels, so there is no need for users to upgrade kernel _before_
upgrading to lenny. After upgrade reboot to the new lenny kernel is
normal procedure.

>   THe _BEST_ example of that are buildd's that for now run etch (even
> some sarge not so long time ago) and have a sid chroot to build. Not
> keeping the CLD patch means that we break our own buildd infrastructure.
> Yay.

This is making a mountain of a molehill. We have one amd64 and one i386
buildd. Certainly installing a (security!) kernel update on two buildd's
is a better solution than having old version of gcc on the two most
used archs we have..


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [alpha, amd64, hppa, i386] GCC-4.3 as the default compilers for lenny?

[Aurelien Jarno]

Riku Voipio a écrit :
> Hi,
> 
> Having gcc-4.2 as default on i386 and amd64, while most other
> architectures have gcc-4.3 means most maintainers never test their
> packages with gcc-4.3. This is making life miserable for those ports
> that actually use gcc-4.3:
> 
> 1) people upload packages with known gcc-4.3 bugs and not bothering
> to fix them.
> 
> 2) people applying gcc 4.3 bugfixes without actually testing them with
> gcc-4.3. Often these turn out to be incomplete fixes.
> 
> On Sun, Mar 23, 2008 at 08:30:54PM +0100, Pierre Habouzit wrote:
>>   Sigh, could we avoid the same discussion over and over, people are not
>> supposed (we never asked it in the past, and I see no valid reason to do
>> so) to update to the last stable point release before upgrading to
>> stable+1.
> 
> Dist-upgrade will not fail due to people still having this bug in their
> kernels, so there is no need for users to upgrade kernel _before_
> upgrading to lenny. After upgrade reboot to the new lenny kernel is
> normal procedure.

It will fail one machine where SBCL installed, as it is called from the
postinst. For those machines, the kernel as to be fixed *before* the
upgrade. Alternatively GCC could keep the current patch.


-- 
  .''`.  Aurelien Jarno | GPG: 1024D/F1BCDB73
 : :' :  Debian developer   | Electrical Engineer
 `. `'   [EMAIL PROTECTED] | [EMAIL PROTECTED]
   `-people.debian.org/~aurel32 | www.aurel32.net


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

[Grant Grundler]

On Sat, Mar 29, 2008 at 06:24:12PM +, rubisher wrote:
...
>> I looked at gcc-43 build output to check warnings related to networking
>> as suggest by John David Anglin.
...
> That remember me that when I discover those new warnings with gcc-4.2 
> 
> "discards qualifiers from pointer target type", they disapeared with 
> gcc-4.3

I saw that but don't know what it's about.

> and btw this nic wasn't working anymore (no ping no ssh, ...) 
> even thought the kernel was booting. Unfortunately, I didn't have time to 
> investigate in more details (and it wasn't question to use gcc-4.3 as new 
> default), sorry. If you compare your kernel build output with gcc-4.2 and 
> 4.3 do you also notice this differences?

By "build output" do you mean the binary (e.g. dot-o files) or log of what
was compiled and which warnings were emitted?

thanks
grant


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: [alpha, hppa] GCC-4.3 as the default compilers for lenny?

[rubisher]

Grant Grundler wrote:

On Sat, Mar 29, 2008 at 06:24:12PM +, rubisher wrote:
...

I looked at gcc-43 build output to check warnings related to networking
as suggest by John David Anglin.

...
That remember me that when I discover those new warnings with gcc-4.2 

"discards qualifiers from pointer target type", they disapeared with 
gcc-4.3


I saw that but don't know what it's about.


The answer of Matthew seems to work ;-)

and btw this nic wasn't working anymore (no ping no ssh, ...) 
even thought the kernel was booting. Unfortunately, I didn't have time to 
investigate in more details (and it wasn't question to use gcc-4.3 as new 
default), sorry. If you compare your kernel build output with gcc-4.2 and 
4.3 do you also notice this differences?


By "build output" do you mean the binary (e.g. dot-o files) or log of what
was compiled and which warnings were emitted?

Well, my understanding was that you compared a log file of a build with gcc-4.2 with the log file of the build of same src 
with gcc-4.3. That's what I did in fact but I was so busy this week that I couldn't post the results. Sorry, I will be off 
next week too, so will try to do when I will be back next Apr 14 ;-)


hth,
r.


thanks
grant





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

[bts-link] source package gcc-defaults

[bts-link-upstream]

#
# bts-link upstream status pull for source package gcc-defaults
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user [EMAIL PROTECTED]

# remote status report for #173513
#  * http://gcc.gnu.org/PR9079
#  * remote status changed: NEW -> ASSIGNED
usertags 173513 - status-NEW
usertags 173513 + status-ASSIGNED

# remote status report for #414178
#  * http://gcc.gnu.org/PR27574
#  * remote status changed: NEW -> ASSIGNED
usertags 414178 - status-NEW
usertags 414178 + status-ASSIGNED

thanks

Results for 4.3.1 20080401 (prerelease) (Debian 4.3.0-3) testsuite on alpha-unknown-linux-gnu

[Matthias Klose]

LAST_UPDATED: 
Native configuration is alpha-unknown-linux-gnu

=== libffi tests ===


Running target unix

=== libffi Summary ===

# of expected passes1389
# of unsupported tests  10
=== libgomp tests ===


Running target unix
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer  (internal 
compiler error)
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer  (test for 
excess errors)
UNRESOLVED: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer  
compilation failed to produce executable
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer 
-funroll-loops  (internal compiler error)
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer 
-funroll-loops  (test for excess errors)
UNRESOLVED: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer 
-funroll-loops  compilation failed to produce executable
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  (internal compiler error)
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  (test for excess errors)
UNRESOLVED: libgomp.fortran/threadprivate3.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  compilation failed to produce executable
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -g  (internal compiler error)
FAIL: libgomp.fortran/threadprivate3.f90  -O3 -g  (test for excess errors)
UNRESOLVED: libgomp.fortran/threadprivate3.f90  -O3 -g  compilation failed to 
produce executable

=== libgomp Summary ===

# of expected passes1715
# of unexpected failures8
# of unresolved testcases   4
=== libstdc++ tests ===


Running target unix
FAIL: abi_check
XPASS: 26_numerics/headers/cmath/c99_classification_macros_c.cc (test for 
excess errors)

=== libstdc++ Summary ===

# of expected passes4934
# of unexpected failures1
# of unexpected successes   1
# of expected failures  59
# of unsupported tests  326
Target: alpha-linux-gnu
gcc version 4.3.1 20080401 (prerelease) (Debian 4.3.0-3) 

=== g++ tests ===


Running target unix
FAIL: g++.dg/ext/cleanup-10.C execution test
FAIL: g++.dg/ext/cleanup-11.C execution test
FAIL: g++.dg/ext/cleanup-8.C execution test
FAIL: g++.dg/ext/cleanup-9.C execution test
FAIL: g++.dg/torture/pr35526.C  -O1  (internal compiler error)
FAIL: g++.dg/torture/pr35526.C  -O1  (test for excess errors)
FAIL: g++.dg/torture/pr35526.C  -O2  (internal compiler error)
FAIL: g++.dg/torture/pr35526.C  -O2  (test for excess errors)
FAIL: g++.dg/torture/pr35526.C  -O3 -fomit-frame-pointer  (internal compiler 
error)
FAIL: g++.dg/torture/pr35526.C  -O3 -fomit-frame-pointer  (test for excess 
errors)
FAIL: g++.dg/torture/pr35526.C  -O3 -g  (internal compiler error)
FAIL: g++.dg/torture/pr35526.C  -O3 -g  (test for excess errors)
FAIL: g++.dg/torture/pr35526.C  -Os  (internal compiler error)
FAIL: g++.dg/torture/pr35526.C  -Os  (test for excess errors)

=== g++ Summary ===

# of expected passes17401
# of unexpected failures14
# of expected failures  82
# of unsupported tests  139
/build/buildd/gcc-4.3-4.3.0/build/gcc/testsuite/g++/../../g++  version 4.3.1 
20080401 (prerelease) (Debian 4.3.0-3) 

=== gcc tests ===


Running target unix
FAIL: tmpdir-gcc.dg-struct-layout-1/t003 c_compat_x_tst.o-c_compat_y_tst.o 
execute 
FAIL: tmpdir-gcc.dg-struct-layout-1/t025 c_compat_x_tst.o-c_compat_y_tst.o 
execute 
FAIL: gcc.dg/cleanup-10.c execution test
FAIL: gcc.dg/cleanup-11.c execution test
FAIL: gcc.dg/cleanup-8.c execution test
FAIL: gcc.dg/cleanup-9.c execution test
FAIL: gcc.dg/pr17024-1.c (internal compiler error)
FAIL: gcc.dg/pr17024-1.c (test for excess errors)
FAIL: gcc.dg/pr28796-2.c (internal compiler error)
FAIL: gcc.dg/pr28796-2.c (test for excess errors)
UNRESOLVED: gcc.dg/pr28796-2.c compilation failed to produce executable
FAIL: gcc.dg/pr33653.c scan-rtl-dump shorten "mem/v"
FAIL: gcc.dg/struct-ret-3.c execution test

=== gcc Summary ===

# of expected passes45663
# of unexpected failures12
# of expected failures  91
# of unresolved testcases   1
# of untested testcases 35
# of unsupported tests  330
/build/buildd/gcc-4.3-4.3.0/build/gcc/xgcc  version 4.3.1 20080401 (prerelease) 
(Debian 4.3.0-3) 

=== gfortran tests ===


Running target unix
FAIL: gfortran.dg/default_format_1.f90  -O0  execution test
FAIL: gfortran.dg/default_format_1.f90  -O1  execution test
FAIL: gfortran.dg/default_format_1.f90  -O2  execution test
FAIL: gfortran.dg/default_format_1.f90  -O3 -fomit-frame-pointer  execution test
FAIL: gfortran.dg/default_format_1.f90  -O3 -fomit-frame-pointer -funroll-loops 
 execution test
FAIL: gfortran.dg/defaul

Results for 4.3.1 20080401 (prerelease) (Debian 4.3.0-3) testsuite on arm-unknown-linux-gnueabi

[Matthias Klose]

LAST_UPDATED: 
Native configuration is arm-unknown-linux-gnueabi

=== libffi tests ===


Running target unix

=== libffi Summary ===

# of expected passes1389
# of unsupported tests  10
=== libgomp tests ===


Running target unix
FAIL: libgomp.fortran/character1.f90  -O0  execution test
FAIL: libgomp.fortran/nestedfn1.f90  -O0  execution test
FAIL: libgomp.fortran/nestedfn3.f90  -O0  execution test
FAIL: libgomp.fortran/reduction3.f90  -O0  execution test
FAIL: libgomp.fortran/reduction3.f90  -O1  execution test
FAIL: libgomp.fortran/reduction3.f90  -O2  execution test
FAIL: libgomp.fortran/reduction3.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/reduction3.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/reduction3.f90  -O3 -fomit-frame-pointer 
-funroll-all-loops -finline-functions  execution test
FAIL: libgomp.fortran/reduction3.f90  -O3 -g  execution test
FAIL: libgomp.fortran/reduction3.f90  -Os  execution test
FAIL: libgomp.fortran/retval2.f90  -O0  execution test
FAIL: libgomp.fortran/vla1.f90  -O1  execution test
FAIL: libgomp.fortran/vla1.f90  -O2  execution test
FAIL: libgomp.fortran/vla1.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/vla1.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/vla1.f90  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/vla1.f90  -O3 -g  execution test
FAIL: libgomp.fortran/vla1.f90  -Os  execution test
FAIL: libgomp.fortran/vla2.f90  -O1  execution test
FAIL: libgomp.fortran/vla2.f90  -O2  execution test
FAIL: libgomp.fortran/vla2.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/vla2.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/vla2.f90  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/vla2.f90  -O3 -g  execution test
FAIL: libgomp.fortran/vla2.f90  -Os  execution test
FAIL: libgomp.fortran/vla3.f90  -O1  execution test
FAIL: libgomp.fortran/vla3.f90  -O2  execution test
FAIL: libgomp.fortran/vla3.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/vla3.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/vla3.f90  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/vla3.f90  -O3 -g  execution test
FAIL: libgomp.fortran/vla3.f90  -Os  execution test
FAIL: libgomp.fortran/vla4.f90  -O1  execution test
FAIL: libgomp.fortran/vla4.f90  -O2  execution test
FAIL: libgomp.fortran/vla4.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/vla4.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/vla4.f90  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/vla4.f90  -O3 -g  execution test
FAIL: libgomp.fortran/vla4.f90  -Os  execution test
FAIL: libgomp.fortran/vla5.f90  -O1  execution test
FAIL: libgomp.fortran/vla5.f90  -O2  execution test
FAIL: libgomp.fortran/vla5.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/vla5.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/vla5.f90  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/vla5.f90  -O3 -g  execution test
FAIL: libgomp.fortran/vla5.f90  -Os  execution test
FAIL: libgomp.fortran/vla6.f90  -O1  execution test
FAIL: libgomp.fortran/vla6.f90  -O2  execution test
FAIL: libgomp.fortran/vla6.f90  -O3 -fomit-frame-pointer  execution test
FAIL: libgomp.fortran/vla6.f90  -O3 -fomit-frame-pointer -funroll-loops  
execution test
FAIL: libgomp.fortran/vla6.f90  -O3 -fomit-frame-pointer -funroll-all-loops 
-finline-functions  execution test
FAIL: libgomp.fortran/vla6.f90  -O3 -g  execution test
FAIL: libgomp.fortran/vla6.f90  -Os  execution test

=== libgomp Summary ===

# of expected passes1655
# of unexpected failures54
# of unsupported tests  7
=== libmudflap tests ===


Running target unix
FAIL: libmudflap.c++/pass41-frag.cxx execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-static) execution test
FAIL: libmudflap.c++/pass41-frag.cxx ( -O) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O2) execution test
FAIL: libmudflap.c++/pass41-frag.cxx (-O3) execution test

=== libmudflap Summary ===

# of expected passes1844
# of unexpected failures5
=== libstdc++ tests ===


Running target unix
FAIL: 20_util/make_signed/requirements/typedefs-2.cc (test for excess errors)
FAIL: 20_util/make_unsigned/requirements/typedefs-2.cc (test for excess errors)
XPASS: 26_numerics/headers/cmath/c99_classification_macros_c.cc (test for 
excess errors)
WARNING: program timed out.
FAIL: ext/pb_ds/regression

Results for 4.3.1 20080401 (prerelease) (Debian 4.3.0-3) testsuite on sparc-unknown-linux-gnu

[Matthias Klose]

LAST_UPDATED: 
Target: sparc-linux-gnu
gcc version 4.3.1 20080401 (prerelease) (Debian 4.3.0-3) 
Native configuration is sparc-unknown-linux-gnu

=== g++ tests ===


Running target unix
FAIL: g++.dg/opt/anchor1.C execution test

=== g++ Summary for unix ===

# of expected passes17455
# of unexpected failures1
# of expected failures  82
# of unsupported tests  134

Running target unix/-fstack-protector
FAIL: g++.dg/opt/anchor1.C execution test

=== g++ Summary for unix/-fstack-protector ===

# of expected passes17455
# of unexpected failures1
# of expected failures  82
# of unsupported tests  134

Running target unix/-m64
FAIL: tmpdir-g++.dg-struct-layout-1/t026 cp_compat_x_tst.o compile,  (internal 
compiler error)
FAIL: tmpdir-g++.dg-struct-layout-1/t026 cp_compat_y_tst.o compile,  (internal 
compiler error)
UNRESOLVED: tmpdir-g++.dg-struct-layout-1/t026 
cp_compat_x_tst.o-cp_compat_y_tst.o link 
UNRESOLVED: tmpdir-g++.dg-struct-layout-1/t026 
cp_compat_x_tst.o-cp_compat_y_tst.o execute 
FAIL: g++.dg/opt/anchor1.C execution test

=== g++ Summary for unix/-m64 ===

# of expected passes17419
# of unexpected failures3
# of expected failures  82
# of unresolved testcases   2
# of unsupported tests  136

=== g++ Summary ===

# of expected passes52329
# of unexpected failures5
# of expected failures  246
# of unresolved testcases   2
# of unsupported tests  404
/build/buildd/gcc-4.3-4.3.0/build/gcc/testsuite/g++/../../g++  version 4.3.1 
20080401 (prerelease) (Debian 4.3.0-3) 

=== gcc tests ===


Running target unix
FAIL: gcc.dg/struct-ret-3.c execution test
FAIL: gcc.dg/vect/pr33804.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/pr33804.c scan-tree-dump-times vect "vectorizing stmts using 
SLP" 1
FAIL: gcc.dg/vect/pr33953.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/pr33953.c scan-tree-dump-times vect "vectorizing stmts using 
SLP" 1
FAIL: gcc.dg/vect/vect-35.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-iv-6.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-multitypes-5.c scan-tree-dump-times vect "vectorized 1 
loops" 1
FAIL: gcc.dg/vect/vect-multitypes-6.c scan-tree-dump-times vect "vectorized 1 
loops" 1
FAIL: gcc.dg/vect/vect-outer-5.c scan-tree-dump-times vect "OUTER LOOP 
VECTORIZED" 1
FAIL: gcc.dg/vect/vect-outer-5.c scan-tree-dump-times vect "zero step in outer 
loop." 1
FAIL: gcc.dg/vect/vect-outer-6.c scan-tree-dump-times vect "OUTER LOOP 
VECTORIZED" 1
FAIL: gcc.dg/vect/vect-outer-6.c scan-tree-dump-times vect "zero step in outer 
loop." 1
FAIL: gcc.dg/vect/vect-vfa-slp.c scan-tree-dump-times vect "vectorized 1 loops" 
1
FAIL: gcc.dg/vect/slp-15.c scan-tree-dump-times vect "vectorizing stmts using 
SLP" 2
FAIL: gcc.dg/vect/slp-25.c scan-tree-dump-times vect "Alignment of access 
forced using peeling" 2
FAIL: gcc.dg/vect/slp-3.c scan-tree-dump-times vect "vectorized 3 loops" 1
FAIL: gcc.dg/vect/slp-3.c scan-tree-dump-times vect "vectorizing stmts using 
SLP" 3
FAIL: gcc.dg/vect/no-vfa-pr29145.c scan-tree-dump-times vect "vectorized 0 
loops" 2
FAIL: gcc.dg/vect/no-vfa-pr29145.c scan-tree-dump-times vect "vectorized 1 
loops" 1
FAIL: gcc.dg/vect/no-vfa-vect-depend-1.c scan-tree-dump-times vect "vectorized 
1 loops" 1
FAIL: gcc.target/sparc/pdist-3.c (internal compiler error)
FAIL: gcc.target/sparc/pdist-3.c (test for excess errors)
UNRESOLVED: gcc.target/sparc/pdist-3.c compilation failed to produce executable

=== gcc Summary for unix ===

# of expected passes46555
# of unexpected failures23
# of expected failures  189
# of unresolved testcases   1
# of untested testcases 35
# of unsupported tests  445

Running target unix/-fstack-protector
FAIL: gcc.c-torture/compile/limits-blockid.c  -O0  (internal compiler error)
FAIL: gcc.c-torture/compile/limits-blockid.c  -O0  (test for excess errors)
FAIL: gcc.dg/struct-ret-3.c execution test
FAIL: gcc.dg/vect/pr33804.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/pr33804.c scan-tree-dump-times vect "vectorizing stmts using 
SLP" 1
FAIL: gcc.dg/vect/pr33953.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/pr33953.c scan-tree-dump-times vect "vectorizing stmts using 
SLP" 1
FAIL: gcc.dg/vect/vect-35.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-iv-6.c scan-tree-dump-times vect "vectorized 1 loops" 1
FAIL: gcc.dg/vect/vect-multitypes-5.c scan-tree-dump-times vect "vectorized 1 
loops" 1
FAIL: gcc.dg/vect/vect-multitypes-6.c scan-tree-dump-times vect "vectorized 1 
loops" 1
FAIL: gcc.dg/vect/vect-outer-5.c scan-tree-dump-times vect "OUTER LOOP 
VECTORIZED" 1
FAIL: gcc.dg/vect/vect-outer-5.c