[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Processed: [bts-link] source package gcc-3.4



Processing commands for control@bugs.debian.org:

> #
> # bts-link upstream status pull for source package gcc-3.4
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg00001.html
> #
> user bts-link-upstream@lists.alioth.debian.org
Setting user to bts-link-upstream@lists.alioth.debian.org (was bts-link-upstream@lists.alioth.debian.org).
> # remote status report for #217360
> #  * http://gcc.gnu.org/PR1027
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> forwarded 217360 http://gcc.gnu.org/PR1027
Bug#217360: [PR12867, fixed in 3.5] incorrect warning message (void format, should be void* format)
Forwarded-to-address changed from http://gcc.gnu.org/PR12867 to http://gcc.gnu.org/PR1027.
(By the way, this Bug is currently marked as done.)

> usertags 217360 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #238432
> #  * http://gcc.gnu.org/PR11801
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> forwarded 238432 http://gcc.gnu.org/PR11801
Bug#238432: [fixed in 4.0] gcj fails to wait for its child processes on exec()
Forwarded-to-address changed from http://gcc.gnu.org/PR14709 to http://gcc.gnu.org/PR11801.
(By the way, this Bug is currently marked as done.)

> usertags 238432 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #254659
> #  * http://gcc.gnu.org/PR16052
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> forwarded 254659 http://gcc.gnu.org/PR16052
Bug#254659: [fixed in 4.0] [PR 16066] i386 loop strength reduction bug
Forwarded-to-address changed from http://gcc.gnu.org/PR16066 to http://gcc.gnu.org/PR16052.
(By the way, this Bug is currently marked as done.)

> usertags 254659 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #285692
> #  * http://gcc.gnu.org/PR18384
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> forwarded 285692 http://gcc.gnu.org/PR18384
Bug#285692: [fixed in 3.4/4.0] [PR 19006] [3.3 / 3.4 / 4.0 regression] ICE in tree_low_cst, at tree.c:3255
Forwarded-to-address changed from http://gcc.gnu.org/PR19006 to http://gcc.gnu.org/PR18384.
(By the way, this Bug is currently marked as done.)

> usertags 285692 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #286715
> #  * http://gcc.gnu.org/PR9157
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> forwarded 286715 http://gcc.gnu.org/PR9157
Bug#286715: [fixed in 4.0] [PR 19711] gcj segfaults instead of reporting the ambiguous expression
Forwarded-to-address changed from http://gcc.gnu.org/PR19711 to http://gcc.gnu.org/PR9157.
(By the way, this Bug is currently marked as done.)

> usertags 286715 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #293466
> #  * http://gcc.gnu.org/PR22309
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> forwarded 293466 http://gcc.gnu.org/PR22309
Bug#293466: [PR 19265] [fixed in 4.0] g++-3.4: mt_allocator + threads + dlclose = crash
Forwarded-to-address changed from http://gcc.gnu.org/PR19265 to http://gcc.gnu.org/PR22309.
(By the way, this Bug is currently marked as done.)

> usertags 293466 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> # remote status report for #307993
> #  * http://gcc.gnu.org/PR16676
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> #  * upstream said bug is wontfix
> forwarded 307993 http://gcc.gnu.org/PR16676
Bug#307993: CE in gen_subprogram_die at dwarf2out.c:10913 building glibc 2.3.5 with nptl
Forwarded-to-address changed from http://gcc.gnu.org/PR21457 to http://gcc.gnu.org/PR16676.
(By the way, this Bug is currently marked as done.)

> tags 307993 + upstream wontfix
Bug#307993: CE in gen_subprogram_die at dwarf2out.c:10913 building glibc 2.3.5 with nptl
Tags were: fixed-upstream upstream
Tags added: upstream, wontfix

> usertags 307993 + status-RESOLVED resolution-WONTFIX
There were no usertags set.
Usertags are now: resolution-WONTFIX status-RESOLVED.
> # remote status report for #331265
> #  * http://gcc.gnu.org/PR21592
> #  * remote status changed: (?) -> RESOLVED
> #  * remote resolution changed: (?) -> RESOLVED
> #  * closed upstream
> forwarded 331265 http://gcc.gnu.org/PR21592
Bug#331265: [fixed in 4.0] ICE in resolve_overloaded_unification
Forwarded-to-address changed from http://gcc.gnu.org/PR24171 to http://gcc.gnu.org/PR21592.

> tags 331265 + fixed-upstream
Bug#331265: [fixed in 4.0] ICE in resolve_overloaded_unification
Tags were: wontfix upstream
Tags added: fixed-upstream

> usertags 331265 + status-RESOLVED resolution-FIXED
There were no usertags set.
Usertags are now: resolution-FIXED status-RESOLVED.
> thanks
Stopping processing here.

Please contact me if you need assistance.

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



Reply to: