[Bug fortran/31964] New: ishftc fails with certain thrid argument

fails with certain thrid argument Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: trumsko at yahoo dot com GCC build

[Bug c++/31378] "too few template-parameter-lists" when initializing static template member

--- Comment #2 from trumsko at yahoo dot com 2007-03-27 20:56 --- Finally I managed to compile the 4.1.2 version of gcc and the error does not occur any more. -- trumsko at yahoo dot com changed: What|Removed |Added

[Bug c++/31378] New: "too few template-parameter-lists" when initializing static template member

When compiling the following program the g++ 4.1.0 gives the error message: "testtemplstatic.cpp:22: error: too few template-parameter-lists". Which I interprete as a complaint, that a "template<>" is missing. If I uncomment the "template<>" in line 21 g++ prints the error message: "testtemplstatic

[Bug fortran/30224] segmentation falut when compiling certain code

--- Comment #1 from trumsko at yahoo dot com 2006-12-15 18:04 --- Created an attachment (id=12815) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12815&action=view) full 'real life' code producing segfault unpack and execute gfortran -c kinds.f90 constants.f

[Bug fortran/30224] New: segmentation falut when compiling certain code

s. -- Summary: segmentation falut when compiling certain code Product: gcc Version: 4.3.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: trumsko at yahoo dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30224

[Bug fortran/30084] segmentation falut when compiling certain code

--- Comment #1 from trumsko at yahoo dot com 2006-12-06 14:36 --- Created an attachment (id=12754) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12754&action=view) source files to crash gfortran unpack and execute gfortran -c kinds.f90 vamp_bundle.f90 to reproduce segme

[Bug fortran/30084] New: segmentation falut when compiling certain code

3.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: trumsko at yahoo dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30084

[Bug fortran/30034] New: pure subroutine requires intent for procedure argument

gcc Version: 4.3.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: trumsko at yahoo dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30034

[Bug libstdc++/26907] Two times filebuf::sungetc() at beginning of file gives undefined result

--- Comment #2 from trumsko at yahoo dot com 2006-03-28 20:58 --- o.k. I read the comments to libstdc++/9439 and browsed through section 27.5.2 of the ISO standtard again. Unfortunatly I didn't find the proof, that the example program realy behaves contrary to the standard, as I

[Bug libstdc++/26907] New: Two times filebuf::sungetc() at beginning of file gives undefined result

If I use filebuf::sungetc() at the beginning of a file, the result of the next sbumc() call is not allways the first character in the file: #include #include using namespace std; int main() { ifstream infile("test.dat"); filebuf* inbuf=infile.rdbuf(); int res; //at beginning of file r