--- Comment #15 from wirawan0 at gmail dot com 2010-03-28 23:01 ---
Yes, just close it. I'm waiting the gentoo folks to find out which patch was
causing this error. It was so slow there...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43146
--- Comment #12 from wirawan0 at gmail dot com 2010-02-26 18:50 ---
I'm positive that the libraries used for compilation and running are the same.
The package was built on my own computer. I'm posting this bug at gentoo
bugzilla (http://bugs.gentoo.org/show_bug.cgi?id=30683
--- Comment #10 from wirawan0 at gmail dot com 2010-02-26 16:08 ---
Created an attachment (id=19970)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=19970&action=view)
valgrind --leak-check=full output
I attach this as a more verbose report. Not sure if it is of
--- Comment #9 from wirawan0 at gmail dot com 2010-02-26 16:06 ---
Here's a brief run with valgrind 3.5.0: I had to recompile glibc (2.10.1) with
"splitdebug" feature in Gentoo OS for it to work.
~/toys/gfortran/ch10 $ valgrind
/usr/libexec/gcc/x86_64-pc-linux-gnu/4.4
--- Comment #7 from wirawan0 at gmail dot com 2010-02-23 18:38 ---
There are no changes if I compiled with *.f90 instead of *.F90 extension.
Wirawan
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43146
--- Comment #5 from wirawan0 at gmail dot com 2010-02-23 17:49 ---
Here's the dump content. Indeed it misses the "\n" stuff.
~/toys/gfortran/ch10 $ cat testme5.F90.003t.original
testme3 ()
{
static integer(kind=4) options.0[8] = {68, 255, 0, 0, 0, 1, 0, 1};
_gfort
--- Comment #3 from wirawan0 at gmail dot com 2010-02-23 15:52 ---
Here's my activity log. It's using gcc 4.4.3 that I just compiled yesterday.
It's still yielding char(0) instead of char(10). Weird.
~/toys/gfortran/ch10 $ cat testme5.F90
module blahblah
character(le
nstant declared in a module does not
transfer correctly
Product: gcc
Version: 4.4.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
Re
--- Comment #4 from wirawan0 at gmail dot com 2009-07-23 16:03 ---
Sorry for my confusion. It turned out that the option -Wno-unused-parameter (no
s) did work on 4.3.2. Marking this bug as invalid.
--
wirawan0 at gmail dot com changed:
What|Removed
--- Comment #2 from wirawan0 at gmail dot com 2009-07-21 19:34 ---
Just to clarify: you might misunderstand this. In Fortran, -Wunused-parameters
is used to issue a warning whenever a constant (which in Fortran called
"PARAMETER") is declared but not used. It has nothing
recognize -Wno-unused-parameters
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: wirawan0 at gmail dot com
GCC build
--- Comment #3 from wirawan0 at gmail dot com 2008-07-02 14:43 ---
This problem also occurs with gfortran 4.3.1.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36632
--- Comment #1 from wirawan0 at gmail dot com 2008-06-25 19:25 ---
Created an attachment (id=15813)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15813&action=view)
Fortran95 source code
No postprocessing needed. To reproduce the error, use:
gfortran -c -fopenmp cr
Version: 4.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: wirawan0 at gmail dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36632
--- Comment #3 from wirawan0 at gmail dot com 2008-01-29 15:00 ---
Created an attachment (id=15047)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=15047&action=view)
Sample code to cause compilation error.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35008
--- Comment #2 from wirawan0 at gmail dot com 2008-01-29 14:59 ---
The whole snippet must be included the (un)desirable error to show up. Let me
give an attachment to make it clear.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35008
Version: 4.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: wirawan0 at gmail dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC targ
Version: 4.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: wirawan0 at gmail dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC targ
--- Comment #3 from wirawan0 at gmail dot com 2007-08-01 20:02 ---
Created an attachment (id=14007)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14007&action=view)
Magically successful testcase!
And by the way, if BOTH b and a are part of higher-dimensional arrays (see
t
--- Comment #1 from wirawan0 at gmail dot com 2007-08-01 20:00 ---
Created an attachment (id=14006)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14006&action=view)
Failing testcase with higher-dimensional b array
I found that the result of conjg(transpose(a)) is also wro
gcc dot gnu dot org
ReportedBy: wirawan0 at gmail dot com
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32962
21 matches
Mail list logo
