[Bug fortran/39087] Performance using COMPLEX data type

2009-02-03 Thread m4341 at abc dot se
--- Comment #2 from m4341 at abc dot se 2009-02-03 15:50 --- Notice that the test cases have been executed on a Pentium III computer with dual 866MHz processors. The 'depth' variable in the example code has been set to produce comfortable execution times for the forementione

[Bug fortran/39087] Performance using COMPLEX data type

2009-02-03 Thread m4341 at abc dot se
--- Comment #1 from m4341 at abc dot se 2009-02-03 15:46 --- Created an attachment (id=17234) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=17234&action=view) Test cases for demonstrating performance impact. The attached file contains code that is in it's current sta

[Bug fortran/39087] New: Performance using COMPLEX data type

2009-02-03 Thread m4341 at abc dot se
type Product: gcc Version: 4.3.3 Status: UNCONFIRMED Severity: minor Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: m4341 at abc dot se http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39087

[Bug libgcj/24832] Modularization of Java libraries

2005-11-14 Thread m4341 at abc dot se
--- Comment #2 from m4341 at abc dot se 2005-11-14 19:18 --- Created an attachment (id=10237) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10237&action=view) Proposal for the initial split. This is the initial split I did, and I must admit that it isn't thoroughly t

[Bug libgcj/24834] PersistentByteMap close() method is not catching Exception

2005-11-14 Thread m4341 at abc dot se
--- Comment #2 from m4341 at abc dot se 2005-11-14 18:42 --- This was detected by opening the whole set of Java files in Eclipse (and not having any standard Java library at all selected). The close method stood out as an error. since it was declared to throw an exception in the classes

[Bug libgcj/24834] New: PersistentByteMap close() method is not catching Exception

2005-11-13 Thread m4341 at abc dot se
Exception Product: gcc Version: 4.0.2 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: m4341 at abc dot se http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24834

[Bug libgcj/24833] New: Variable declared as 'final' can be assigned in conflict with Java standard

2005-11-13 Thread m4341 at abc dot se
with Java standard Product: gcc Version: 4.0.2 Status: UNCONFIRMED Severity: trivial Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: m4341 at abc dot se http

[Bug java/20977] Invalid long to int promotion permitted in array initializer

2005-11-13 Thread m4341 at abc dot se
--- Comment #2 from m4341 at abc dot se 2005-11-13 11:32 --- This is actually in use in the class gnu.gcj.tools.gcj_dbtool.Main.java, line 382. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20977

[Bug libgcj/24832] New: Modularization of Java libraries

2005-11-13 Thread m4341 at abc dot se
mponent: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: m4341 at abc dot se http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24832