Bug#433636: gij-4.1 broken, gij-4.2 OK
Hi, Sorry for the delay. When I compile with gcj 4.1 and then run with gij-4.1, I get the error. If I run the same class file with gij-4.2, everything's OK. It looks like the issue is (or was) in the classpath libs, in java/util/Calendar.java. The gcj4.2-src source package has some extra statements in the setTimeZone method compared to gcj-src that (to me) seem to make the difference. Cheers Jan-Pascal
gcc allows negatively sized arrays.
>Submitter-Id: net
>Originator:Steven Young
>Organization: n/a
>Confidential: no
>Synopsis: gcc allows negatively-sized arrays
>Severity: non-critical
>Priority: low
>Category: c
>Class: accepts-illegal
>Release: gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4)
>Environment:
System: Linux pc1 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686
GNU/Linux
Architecture: i686
host: i486-pc-linux-gnu
build: i486-pc-linux-gnu
target: i486-pc-linux-gnu
configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--program-suffix=-4.1 --enable-__cxa_atexit --enable-clocale=gnu
--enable-libstdcxx-debug --enable-mpfr --enable-checking=release i486-linux-gnu
>Description:
By using an integer variable as the size of an array to be
initialized on the stack, you can trick gcc into accepting
and trying to create a negatively-sized array. The assembly
it generates in such a case seems to indicate it really thinks
it has a negatively-sized array.
>How-To-Repeat:
#include
int main(int argc, char **argv) {
int x = -2;
int y[x];
printf("%d\n", sizeof(y));
}
This will output -8.
>Fix:
I don't know.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package gcc-4.2
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.2 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #431608 > # * http://gcc.gnu.org/PR30052 > # * remote status changed: (?) -> REOPENED > forwarded 431608 http://gcc.gnu.org/PR32900, merged-upstream: > http://gcc.gnu.org/PR30052 Bug#431608: [PR32900] Abysmal performance compiling python-qt3 Forwarded-to-address changed from http://gcc.gnu.org/PR32900 to http://gcc.gnu.org/PR32900, merged-upstream: http://gcc.gnu.org/PR30052. > usertags 431608 + status-REOPENED Bug#431608: [PR32900] Abysmal performance compiling python-qt3 There were no usertags set. Usertags are now: status-REOPENED. > 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: [bts-link] source package gcc-4.0
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.0 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #342126 > # * http://gcc.gnu.org/PR28318 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> INVALID > # * closed upstream > tags 342126 + fixed-upstream Bug#342126: [PR28318] Function names starting with $ make assembler barf Tags were: upstream Tags added: fixed-upstream > usertags 342126 + status-RESOLVED resolution-INVALID Bug#342126: [PR28318] Function names starting with $ make assembler barf There were no usertags set. Usertags are now: resolution-INVALID status-RESOLVED. > # remote status report for #352790 > # * http://gcc.gnu.org/PR28315 > # * remote status changed: (?) -> UNCONFIRMED > usertags 352790 + status-UNCONFIRMED Bug#352790: [PR28315] gcc doesn't use locale for default input charset There were no usertags set. Usertags are now: status-UNCONFIRMED. > 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: [bts-link] source package gcj-4.1
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcj-4.1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #423160 > # * http://gcc.gnu.org/PR32862 > # * remote status changed: ASSIGNED -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 423160 + fixed-upstream Bug#423160: gij-4.1: bug in EnumMap implementation Tags were: upstream Tags added: fixed-upstream > usertags 423160 - status-ASSIGNED Bug#423160: gij-4.1: bug in EnumMap implementation Usertags were: status-ASSIGNED. Usertags are now: . > usertags 423160 + status-RESOLVED resolution-FIXED Bug#423160: gij-4.1: bug in EnumMap implementation There were no usertags set. Usertags are now: resolution-FIXED status-RESOLVED. > # remote status report for #40 > # * http://gcc.gnu.org/PR21821 > # * remote status changed: NEW -> RESOLVED > # * remote resolution changed: (?) -> FIXED > # * closed upstream > tags 40 + fixed-upstream Bug#40: gcj-4.1: FTBFS on GNU/Hurd Tags were: patch Tags added: fixed-upstream > usertags 40 - status-NEW Bug#40: gcj-4.1: FTBFS on GNU/Hurd Usertags were: status-NEW. Usertags are now: . > usertags 40 + status-RESOLVED resolution-FIXED Bug#40: gcj-4.1: FTBFS on GNU/Hurd 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) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: [bts-link] source package gcc-4.1
Processing commands for [EMAIL PROTECTED]: > # > # bts-link upstream status pull for source package gcc-4.1 > # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html > # > user [EMAIL PROTECTED] Setting user to [EMAIL PROTECTED] (was [EMAIL PROTECTED]). > # remote status report for #386174 > # * http://gcc.gnu.org/PR19430 > # * remote status changed: (?) -> NEW > forwarded 386174 http://gcc.gnu.org/PR29227, merged-upstream: > http://gcc.gnu.org/PR19430 Bug#386174: [PR29227] gcc sometimes doesn't recognize uninitialized variables Forwarded-to-address changed from http://gcc.gnu.org/PR29227 to http://gcc.gnu.org/PR29227, merged-upstream: http://gcc.gnu.org/PR19430. > usertags 386174 + status-NEW Bug#386174: [PR29227] gcc sometimes doesn't recognize uninitialized variables There were no usertags set. Usertags are now: status-NEW. > # remote status report for #387222 > # * http://gcc.gnu.org/PR27096 > # * remote status changed: (?) -> RESOLVED > # * remote resolution changed: (?) -> FIXED > forwarded 387222 http://gcc.gnu.org/PR29228, merged-upstream: > http://gcc.gnu.org/PR27096 Bug#387222: [PR29228, fixed in 4.2] ICE in gfc_trans_deferred_array, at fortran/trans-array.c:4514 Forwarded-to-address changed from http://gcc.gnu.org/PR29228 to http://gcc.gnu.org/PR29228, merged-upstream: http://gcc.gnu.org/PR27096. > usertags 387222 + status-RESOLVED resolution-FIXED Bug#387222: [PR29228, fixed in 4.2] ICE in gfc_trans_deferred_array, at fortran/trans-array.c:4514 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) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[bts-link] source package gcc-4.2
# # bts-link upstream status pull for source package gcc-4.2 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #431608 # * http://gcc.gnu.org/PR30052 # * remote status changed: (?) -> REOPENED forwarded 431608 http://gcc.gnu.org/PR32900, merged-upstream: http://gcc.gnu.org/PR30052 usertags 431608 + status-REOPENED thanks
[bts-link] source package gcc-defaults
# # 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 #395057 # * http://gcc.gnu.org/PR29609 # * remote status changed: (?) -> NEW usertags 395057 + status-NEW thanks
[bts-link] source package gcc-4.0
# # bts-link upstream status pull for source package gcc-4.0 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #342126 # * http://gcc.gnu.org/PR28318 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> INVALID # * closed upstream tags 342126 + fixed-upstream usertags 342126 + status-RESOLVED resolution-INVALID # remote status report for #352790 # * http://gcc.gnu.org/PR28315 # * remote status changed: (?) -> UNCONFIRMED usertags 352790 + status-UNCONFIRMED thanks
[bts-link] source package gcj-4.1
# # bts-link upstream status pull for source package gcj-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #423160 # * http://gcc.gnu.org/PR32862 # * remote status changed: ASSIGNED -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 423160 + fixed-upstream usertags 423160 - status-ASSIGNED usertags 423160 + status-RESOLVED resolution-FIXED # remote status report for #40 # * http://gcc.gnu.org/PR21821 # * remote status changed: NEW -> RESOLVED # * remote resolution changed: (?) -> FIXED # * closed upstream tags 40 + fixed-upstream usertags 40 - status-NEW usertags 40 + status-RESOLVED resolution-FIXED thanks
[bts-link] source package gcc-4.1
# # bts-link upstream status pull for source package gcc-4.1 # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user [EMAIL PROTECTED] # remote status report for #386174 # * http://gcc.gnu.org/PR19430 # * remote status changed: (?) -> NEW forwarded 386174 http://gcc.gnu.org/PR29227, merged-upstream: http://gcc.gnu.org/PR19430 usertags 386174 + status-NEW # remote status report for #387222 # * http://gcc.gnu.org/PR27096 # * remote status changed: (?) -> RESOLVED # * remote resolution changed: (?) -> FIXED forwarded 387222 http://gcc.gnu.org/PR29228, merged-upstream: http://gcc.gnu.org/PR27096 usertags 387222 + status-RESOLVED resolution-FIXED thanks
gcc-3.4 3.4.6ds1-6 MIGRATED to testing
FYI: The status of the gcc-3.4 source package in Debian's testing distribution has changed. Previous version: 3.4.6ds1-5 Current version: 3.4.6ds1-6 -- This email is automatically generated; [EMAIL PROTECTED] is responsible. See http://people.debian.org/~henning/trille/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: gcc allows negatively sized arrays.
On Wed, 08 Aug 2007 12:46:50 -0400, Steven Young wrote: >>Fix: > I don't know. comp.gcc.bugs indicates undefined C99 behavior doesn't need a fix. =) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: retitle gcj report
Processing commands for [EMAIL PROTECTED]: > retitle 433636 [fixed in 4.2] java.util.Calendar.setTimeZone fails to set > ZONE_OFFSET Bug#433636: gcj-4.1: java.util.Calendar.setTimeZone fails to set ZONE_OFFSET Changed Bug title to `[fixed in 4.2] java.util.Calendar.setTimeZone fails to set ZONE_OFFSET' from `gcj-4.1: java.util.Calendar.setTimeZone fails to set ZONE_OFFSET'. > tag 433636 + upstream fixed-upstream Bug#433636: [fixed in 4.2] java.util.Calendar.setTimeZone fails to set ZONE_OFFSET Tags were: moreinfo Tags added: upstream, fixed-upstream > 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]
