[Bug fortran/27121] New: Undefined symbols: ___dso_handle

2006-04-11 Thread dir at lanl dot gov
I just did a complete download and rebuild of gfortran. When I try to use it, I
get a linking error -

[dranta:~/tests] dir% rm print.o
[dranta:~/tests] dir% gfortran -c print.f
[dranta:~/tests] dir% nm print.o
 T _MAIN__
 U __gfortran_set_std
 U __gfortran_st_write
 U __gfortran_st_write_done
 U __gfortran_stop_numeric
 U __gfortran_transfer_real
 U dyld_stub_binding_helper
[dranta:~/tests] dir% gfortran -o print print.f
/usr/bin/ld: Undefined symbols:
___dso_handle
collect2: ld returned 1 exit status
[dranta:~/tests] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.5.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060411 (experimental)
[dranta:~/tests] dir%


-- 
   Summary: Undefined symbols: ___dso_handle
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.5.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27121



[Bug fortran/27183] New: gfortran - testsuite unexpected failure - assembler error message

2006-04-17 Thread dir at lanl dot gov
Running the testsuite gives an unexpected failure 
(error out of assembler with -O0) -



[pactech01:~/tests] dir% gfortran -w -O3 -c
~/gfortran/gcc/gcc/testsuite/gfortran.dg/assign_2.f90
[pactech01:~/tests] dir% gfortran -w -O2 -c
~/gfortran/gcc/gcc/testsuite/gfortran.dg/assign_2.f90
[pactech01:~/tests] dir% gfortran -w -O1 -c
~/gfortran/gcc/gcc/testsuite/gfortran.dg/assign_2.f90
[pactech01:~/tests] dir% gfortran -w -O0 -c
~/gfortran/gcc/gcc/testsuite/gfortran.dg/assign_2.f90
/var/tmp//cc5uT7yz.s:28:section difference relocatable subtraction expression,
"L2" minus "L001$pb" using a symbol at the end of section will not
produce an assembly time constant
/var/tmp//cc5uT7yz.s:28:use a symbol with a constant value created with an
assignment instead of the expression, L_const_sym = L2 - L001$pb
[pactech01:~/tests] dir% gfortran --v
Using built-in specs.
Target: i386-apple-darwin8.6.1
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060417 (experimental)
[pactech01:~/tests] dir% 




WARNING: Couldn't find the global config file.
Test Run By dir on Mon Apr 17 09:22:47 2006
Native configuration is i386-apple-darwin8.6.1

=== gfortran tests ===

Schedule of variations:
unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /Users/dir/gfortran/gcc/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
FAIL: gfortran.dg/assign_2.f90  -O0  (test for excess errors)
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp ...
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp ...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
...

=== gfortran Summary ===

# of expected passes12821
# of unexpected failures1
# of expected failures  7
# of unresolved testcases   1
# of unsupported tests  46
/Users/dir/gfortran/ibin/gcc/testsuite/gfortran/../../gfortran  version 4.2.0
20060417 (experimental)


-- 
   Summary: gfortran - testsuite unexpected failure - assembler
error message
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
    ReportedBy: dir at lanl dot gov
  GCC host triplet: i386-apple-darwin8.6.1


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27183



[Bug fortran/27561] New: i386-pc-mingw32 version incorrect error

2006-05-11 Thread dir at lanl dot gov
The i386-pc-mingw32 version errors incorrectly on this program fragment -

[EMAIL PROTECTED] /d/Docume~1/rantad/mydocu~1/tests
$ gfortran -c  eps.f90
 In file eps.f90:10

xmax1 = min ( xx, ONE / epsilon ( xx ) )
1
Error: Division by zero at (1)

[EMAIL PROTECTED] /d/Docume~1/rantad/mydocu~1/tests
$ cat eps.f90
  module test
  implicit none
  integer, parameter :: REAL8 = SELECTED_REAL_KIND(12)
  real(REAL8), parameter :: ONE  = 1.0_REAL8
  contains
  real(REAL8) function digamma (xx)
real(REAL8), intent(in) :: xx
real(REAL8) :: xmax1

xmax1 = min ( xx, ONE / epsilon ( xx ) )
digamma=xmax1;
  end function digamma
  end module test



[EMAIL PROTECTED] /d/Docume~1/rantad/mydocu~1/tests
$ gfortran --v
Using built-in specs.
Target: i386-pc-mingw32
Configured with: ../gcc/configure --prefix=/mingw --enable-languages=c,fortran
--with-gmp=/home/coudert/local --disable-nls --with-ld=/mingw/bin/ld
--with-as=/mingw/bin/as --disable-werror --enable-bootstrap
--enable-threads=win32 --with-win32-nlsapi=unicode --host=i386-pc-mingw32
Thread model: win32
gcc version 4.2.0 20060504 (experimental)


-- 
   Summary: i386-pc-mingw32 version incorrect error
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: i386-pc-mingw32


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27561



[Bug libfortran/27575] New: gfortran - does not generate error when trying to read too much data

2006-05-12 Thread dir at lanl dot gov
This program writes one word and then reads two words. g77 finds the error but
gfortran does not -

[dranta:~/tests/gfortran-D] dir% gfortran -o read01 read01.f
[dranta:~/tests/gfortran-D] dir% read01
[dranta:~/tests/gfortran-D] dir% cat read01.f
  program test
  integer i1,i2
  open(unit=11,form='unformatted')
  write(11)i1  
  close(11,status='keep')

   open(unit=11,form='unformatted')
   rewind 11
   read(11)i1,i2
   close(11,status='delete')
   stop
   end[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060511 (experimental)
[dranta:~/tests/gfortran-D] dir% g77 -o read01 read01.f
[dranta:~/tests/gfortran-D] dir% read01
do_us: off end of record
apparent state: unit 11 named fort.11
lately reading sequential unformatted external IO
Abort
[dranta:~/tests/gfortran-D] dir%


-- 
   Summary: gfortran - does not generate error when trying to read
too much data
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
GCC target triplet: powerpc-apple-darwin8.6.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27575



[Bug fortran/27642] New: gfortran - fails to build MacOSX - 10.4.6

2006-05-17 Thread dir at lanl dot gov
I updated the source tree this morning and the gfortran build now fails -

rm -rf libbackend.a
ar rc libbackend.a double-int.o tree-chrec.o tree-scalar-evolution.o
tree-data-ref.o tree-cfg.o tree-dfa.o tree-eh.o tree-ssa.o tree-optimize.o
tree-gimple.o gimplify.o tree-pretty-print.o tree-into-ssa.o tree-outof-ssa.o
tree-ssa-ccp.o tree-vn.o tree-ssa-uncprop.o tree-ssa-dce.o  tree-ssa-copy.o
tree-nrv.o tree-ssa-copyrename.o tree-ssa-pre.o tree-ssa-live.o
tree-ssa-operands.o tree-ssa-alias.o tree-ssa-phiopt.o tree-ssa-forwprop.o
tree-nested.o tree-ssa-dse.o tree-ssa-dom.o domwalk.o tree-tailcall.o
gimple-low.o tree-iterator.o omp-low.o tree-phinodes.o tree-ssanames.o
tree-sra.o tree-complex.o tree-vect-generic.o tree-ssa-loop.o
tree-ssa-loop-niter.o tree-ssa-loop-manip.o tree-ssa-threadupdate.o
tree-ssa-threadedge.o tree-vectorizer.o tree-vect-analyze.o
tree-vect-transform.o tree-vect-patterns.o tree-ssa-loop-prefetch.o
tree-ssa-loop-ivcanon.o tree-ssa-propagate.o tree-ssa-address.o
tree-ssa-math-opts.o tree-ssa-loop-ivopts.o tree-if-conv.o
tree-ssa-loop-unswitch.o alias.o bb-reorder.o bitmap.o builtins.o caller-save.o
calls.o cfg.o cfganal.o cfgbuild.o cfgcleanup.o cfglayout.o cfgloop.o
cfgloopanal.o cfgloopmanip.o loop-init.o loop-unswitch.o loop-unroll.o cfgrtl.o
combine.o conflict.o convert.o coverage.o cse.o cselib.o dbxout.o ddg.o
tree-ssa-loop-ch.o loop-invariant.o tree-ssa-loop-im.o debug.o df-core.o
df-problems.o df-scan.o dfp.o diagnostic.o dojump.o dominance.o loop-doloop.o
dwarf2asm.o dwarf2out.o emit-rtl.o except.o explow.o loop-iv.o expmed.o expr.o
final.o flow.o fold-const.o function.o gcse.o genrtl.o ggc-common.o global.o
graph.o gtype-desc.o haifa-sched.o hooks.o ifcvt.o insn-attrtab.o insn-emit.o
insn-modes.o insn-extract.o insn-opinit.o insn-output.o insn-peep.o
insn-recog.o integrate.o intl.o jump.o  langhooks.o lcm.o lists.o local-alloc.o
mode-switching.o modulo-sched.o optabs.o options.o opts.o opts-common.o
params.o postreload.o postreload-gcse.o predict.o insn-preds.o insn-automata.o
pointer-set.o print-rtl.o print-tree.o profile.o value-prof.o var-tracking.o
real.o recog.o reg-stack.o regclass.o regmove.o regrename.o reload.o reload1.o
reorg.o resource.o rtl.o rtlanal.o rtl-error.o sbitmap.o sched-deps.o
sched-ebb.o sched-rgn.o sched-vis.o sdbout.o see.o simplify-rtx.o sreal.o
stmt.o stor-layout.o stringpool.o struct-equiv.o targhooks.o timevar.o toplev.o
tracer.o tree.o tree-dump.o varasm.o varray.o vec.o version.o vmsdbgout.o
xcoffout.o alloc-pool.o et-forest.o cfghooks.o bt-load.o pretty-print.o
ggc-page.o web.o passes.o tree-profile.o rtlhooks.o cfgexpand.o lambda-mat.o
lambda-trans.o  lambda-code.o tree-loop-linear.o tree-ssa-sink.o tree-vrp.o
tree-stdarg.o tree-cfgcleanup.o tree-ssa-reassoc.o tree-ssa-structalias.o
tree-object-size.o rtl-factoring.o rs6000.o darwin.o host-darwin.o
host-ppc-darwin.o tree-inline.o cgraph.o cgraphunit.o tree-nomudflap.o ipa.o
ipa-inline.o ipa-utils.o ipa-reference.o ipa-pure-const.o ipa-type-escape.o
ipa-prop.o ipa-cp.o
mv tmp-libgcc.mk libgcc.mk
ranlib -c libbackend.a
gcc   -g -no-cpp-precomp -DHAVE_DESIGNATED_INITIALIZERS=0 -DIN_GCC   -W -Wall
-Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-Wmissing-format-attribute -fno-common   -DHAVE_CONFIG_H  -o cc1-dummy c-lang.o
stub-objc.o attribs.o c-errors.o c-lex.o c-pragma.o c-decl.o c-typeck.o
c-convert.o c-aux-info.o c-common.o c-opts.o c-format.o c-semantics.o
c-incpath.o cppdefault.o c-ppoutput.o c-cppbuiltin.o prefix.o c-objc-common.o
c-dump.o c-pch.o c-parser.o darwin-c.o rs6000-c.o c-gimplify.o tree-mudflap.o
c-pretty-print.o c-omp.o dummy-checksum.o \
  main.o tree-browser.o libbackend.a ../libcpp/libcpp.a
../libdecnumber/libdecnumber.a ../libcpp/libcpp.a ./../intl/libintl.a -liconv 
../libiberty/libiberty.a ../libdecnumber/libdecnumber.a
/usr/bin/ld: warning multiple definitions of symbol _locale_charset
./../intl/libintl.a(localcharset.o) definition of _locale_charset in section
(__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.1/../../../libiconv.dylib(localcharset.o)
definition of _locale_charset
/usr/bin/ld: Undefined symbols:
_TARGET_NO_FP_IN_TOC
collect2: ld returned 1 exit status
make[3]: *** [cc1-dummy] Error 1
rm fsf-funding.pod gcov.pod gfdl.pod cpp.pod gpl.pod gcc.pod
make[2]: *** [all-stage1-gcc] Error 2
make[1]: *** [stage1-bubble] Error 2
make: *** [all] Error 2


-- 
   Summary: gfortran - fails to build MacOSX - 10.4.6
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.6.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27642



[Bug target/27642] [4.2 regression] gfortran - fails to build MacOSX - 10.4.6

2006-05-17 Thread dir at lanl dot gov


--- Comment #2 from dir at lanl dot gov  2006-05-17 17:04 ---
no problem with 4.1.1 -

[dranta:~] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran4.1
--enable-languages=c,f95
Thread model: posix
gcc version 4.1.1 20060517 (prerelease)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27642



[Bug fortran/27683] New: Many new GFORTRAN testsuite failures

2006-05-19 Thread dir at lanl dot gov
st_14.f90 execution test
FAIL: gfortran.dg/namelist_21.f90 execution test
FAIL: gfortran.dg/namelist_21.f90 execution test
FAIL: gfortran.dg/namelist_21.f90 execution test
FAIL: gfortran.dg/namelist_21.f90 execution test
FAIL: gfortran.dg/namelist_21.f90 execution test
FAIL: gfortran.dg/namelist_21.f90 execution test
FAIL: gfortran.dg/namelist_21.f90 execution test
FAIL: gfortran.dg/namelist_22.f90 execution test
FAIL: gfortran.dg/namelist_22.f90 execution test
FAIL: gfortran.dg/namelist_22.f90 execution test
FAIL: gfortran.dg/namelist_22.f90 execution test
FAIL: gfortran.dg/namelist_22.f90 execution test
FAIL: gfortran.dg/namelist_22.f90 execution test
FAIL: gfortran.dg/namelist_22.f90 execution test
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/gomp/gomp.exp ...
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp ...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
...
FAIL: gfortran.fortran-torture/execute/adjustr.f90 execution,  -O1 
FAIL: gfortran.fortran-torture/execute/adjustr.f90 execution,  -O2 
FAIL: gfortran.fortran-torture/execute/adjustr.f90 execution,  -O3
-fomit-frame-pointer 
FAIL: gfortran.fortran-torture/execute/adjustr.f90 execution,  -O3
-fomit-frame-pointer -funroll-loops 
FAIL: gfortran.fortran-torture/execute/adjustr.f90 execution,  -O3
-fomit-frame-pointer -funroll-all-loops -finline-functions 
FAIL: gfortran.fortran-torture/execute/adjustr.f90 execution,  -O3 -g 
FAIL: gfortran.fortran-torture/execute/adjustr.f90 execution,  -Os 
FAIL: gfortran.fortran-torture/execute/write_logical.f90 execution,  -O1 
FAIL: gfortran.fortran-torture/execute/write_logical.f90 execution,  -O2 
FAIL: gfortran.fortran-torture/execute/write_logical.f90 execution,  -O3
-fomit-frame-pointer 
FAIL: gfortran.fortran-torture/execute/write_logical.f90 execution,  -O3
-fomit-frame-pointer -funroll-loops 
FAIL: gfortran.fortran-torture/execute/write_logical.f90 execution,  -O3
-fomit-frame-pointer -funroll-all-loops -finline-functions 
FAIL: gfortran.fortran-torture/execute/write_logical.f90 execution,  -O3 -g 
FAIL: gfortran.fortran-torture/execute/write_logical.f90 execution,  -Os 

=== gfortran Summary ===

# of expected passes12854
# of unexpected failures114
# of expected failures  7
# of unsupported tests  56
/Users/dir/gfortran/ibin/gcc/testsuite/gfortran/../../gfortran  version 4.2.0
20060519 (experimental)


-- 
   Summary: Many new GFORTRAN testsuite failures
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.6.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-22 Thread dir at lanl dot gov


--- Comment #2 from dir at lanl dot gov  2006-05-22 14:41 ---
 Hi Paul,

I down loaded a completely new tree this morning and did a new build with
about the same results -

Test Run By dir on Mon May 22 07:08:14 2006
Native configuration is powerpc-apple-darwin8.6.0

=== gfortran tests ===

Schedule of variations:
unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /Users/dir/gfortran/gcc/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
FAIL: gfortran.dg/char_result_5.f90 execution test
FAIL: gfortran.dg/char_result_5.f90 execution test
FAIL: gfortran.dg/char_result_5.f90 execution test
FAIL: gfortran.dg/char_result_5.f90 execution test
FAIL: gfortran.dg/char_result_5.f90 execution test
FAIL: gfortran.dg/char_result_5.f90 execution test
FAIL: gfortran.dg/char_result_5.f90 execution test
FAIL: gfortran.dg/char_result_6.f90 execution test
FAIL: gfortran.dg/char_result_6.f90 execution test
FAIL: gfortran.dg/char_result_6.f90 execution test
FAIL: gfortran.dg/char_result_6.f90 execution test
FAIL: gfortran.dg/char_result_6.f90 execution test
FAIL: gfortran.dg/char_result_6.f90 execution test
FAIL: gfortran.dg/char_result_6.f90 execution test
FAIL: gfortran.dg/eor_handling_1.f90 execution test
FAIL: gfortran.dg/eor_handling_1.f90 execution test
FAIL: gfortran.dg/eor_handling_1.f90 execution test
FAIL: gfortran.dg/eor_handling_1.f90 execution test
FAIL: gfortran.dg/eor_handling_1.f90 execution test
FAIL: gfortran.dg/eor_handling_1.f90 execution test
FAIL: gfortran.dg/eor_handling_1.f90 execution test
FAIL: gfortran.dg/fmt_read_bz_bn.f90 execution test
FAIL: gfortran.dg/fmt_read_bz_bn.f90 execution test
FAIL: gfortran.dg/fmt_read_bz_bn.f90 execution test
FAIL: gfortran.dg/fmt_read_bz_bn.f90 execution test
FAIL: gfortran.dg/fmt_read_bz_bn.f90 execution test
FAIL: gfortran.dg/fmt_read_bz_bn.f90 execution test
FAIL: gfortran.dg/fmt_read_bz_bn.f90 execution test
FAIL: gfortran.dg/fmt_white.f execution test
FAIL: gfortran.dg/fmt_white.f execution test
FAIL: gfortran.dg/fmt_white.f execution test
FAIL: gfortran.dg/fmt_white.f execution test
FAIL: gfortran.dg/fmt_white.f execution test
FAIL: gfortran.dg/fmt_white.f execution test
FAIL: gfortran.dg/fmt_white.f execution test
FAIL: gfortran.dg/fmt_zero_digits.f90 execution test
FAIL: gfortran.dg/fmt_zero_digits.f90 execution test
FAIL: gfortran.dg/fmt_zero_digits.f90 execution test
FAIL: gfortran.dg/fmt_zero_digits.f90 execution test
FAIL: gfortran.dg/fmt_zero_digits.f90 execution test
FAIL: gfortran.dg/fmt_zero_digits.f90 execution test
FAIL: gfortran.dg/fmt_zero_digits.f90 execution test
FAIL: gfortran.dg/inquire_6.f90 execution test
FAIL: gfortran.dg/inquire_6.f90 execution test
FAIL: gfortran.dg/inquire_6.f90 execution test
FAIL: gfortran.dg/inquire_6.f90 execution test
FAIL: gfortran.dg/inquire_6.f90 execution test
FAIL: gfortran.dg/inquire_6.f90 execution test
FAIL: gfortran.dg/inquire_6.f90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/large_real_kind_form_io_2.f90 execution test
FAIL: gfortran.dg/list_read_5.f90 execution test
FAIL: gfortran.dg/list_read_5.f90 execution test
FAIL: gfortran.dg/list_read_5.f90 execution test
FAIL: gfortran.dg/list_read_5.f90 execution test
FAIL: gfortran.dg/list_read_5.f90 execution test
FAIL: gfortran.dg/list_read_5.f90 execution test
FAIL: gfortran.dg/list_read_5.f90 execution test
FAIL: gfortran.dg/namelist_11.f execution test
FAIL: gfortran.dg/namelist_11.f execution test
FAIL: gfortran.dg/namelist_11.f execution test
FAIL: gfortran.dg/namelist_11.f execution test
FAIL: gfortran.dg/namelist_11.f execution test
FAIL: gfortran.dg/namelist_11.f execution test
FAIL: gfortran.dg/namelist_11.f execution test
FAIL: gfortran.dg/namelist_14.f90 execution test
FAIL: gfortran.dg/namelist_14.f90 execution test
FAIL: gfortran.dg/namelist_14.f90 execution test
FAIL: gfortran.dg/namelist_14.f90 execution test

[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-22 Thread dir at lanl dot gov


--- Comment #3 from dir at lanl dot gov  2006-05-22 14:58 ---
I grabbed one of the tests that failed and tried it with today's 4.2.0 version
and version 4.1.1 and it failed with the new and passed with the old -

[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
At line 9 of file write_logical.f90
Fortran runtime error: Missing initial left parenthesis in format

[dranta:~/tests/gfortran-D] dir% cat write_logical.f90
! PR 14334, L edit descriptor does not work
!
!  this test uses L1 and L4 to print TRUE and FALSE
   logical true,false
   character*10 b
   true = .TRUE.
   false = .FALSE.
   b = ''
   write (b, '(L1)') true
   if (b(1:1) .ne. 'T') call abort

   b = ''
   write (b, '(L1)') false
   if (b(1:1) .ne. 'F') call abort

   b = ''
   write(b, '(L4)') true
   if (b(1:4) .ne. '   T') call abort

   b = ''
   write(b, '(L4)') false
   if (b(1:4) .ne. '   F') call abort
   end
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060522 (experimental)
[dranta:~/tests/gfortran-D] dir% set path =(~/gfortran4.1/bin $path)
[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran4.1
--enable-languages=c,f95
Thread model: posix
gcc version 4.1.1 20060517 (prerelease)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-22 Thread dir at lanl dot gov


--- Comment #4 from dir at lanl dot gov  2006-05-22 20:51 ---
There is no problem on LINUX or the Intel Macintosh version - only having
trouble with the powerPC version.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-23 Thread dir at lanl dot gov


--- Comment #5 from dir at lanl dot gov  2006-05-23 19:16 ---
Has anybody else with a powerPC Macintosh tried the testsuite recently ?

I down loaded and rebuild 4.1.1 and 4.2.0 today. 4.1.1 is Ok. 4.2.0 has the
same errors.

The test problem in comment #3 works with -g, but when complied with -O1 the
address that should point to '(L1)' is pointing a null character before the '('
 when it gets to the runtime print routine and so it generates the error.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-24 Thread dir at lanl dot gov


--- Comment #8 from dir at lanl dot gov  2006-05-24 18:27 ---
 Hi Jerry,

 I tried rev 113947 and rev 113923 that I think are just before your
patches and gfortran still failed. I did a "svn update -r 113923 gcc" to create
the old version. I hope that is the correct way to do it.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-25 Thread dir at lanl dot gov


--- Comment #10 from dir at lanl dot gov  2006-05-25 13:36 ---
I restored and rebuilt the 20060508 version that I had archived and I still get
the error -


[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
At line 9 of file write_logical.f90
Fortran runtime error: Missing initial left parenthesis in format

[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060508 (experimental)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-25 Thread dir at lanl dot gov


--- Comment #12 from dir at lanl dot gov  2006-05-25 14:35 ---
I rebuild version 20060508 from the full source tree that I had saved and I
find the problem - I am beginning to wonder if the update to CCTOOLS or the
system is causing the problem - except for the fact that I can build the
current 4.1.1 and it works fine.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-25 Thread dir at lanl dot gov


--- Comment #14 from dir at lanl dot gov  2006-05-25 14:47 ---
The version from the wiki also fails -

[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
At line 9 of file write_logical.f90
Fortran runtime error: Missing initial left parenthesis in format

[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin7.9.0
Configured with: ../gcc/configure --prefix=/usr/local/gfortran
--enable-languages=c,fortran --with-gmp=/tmp/gfortran-20060512/gfortran_libs
--enable-bootstrap
Thread model: posix
gcc version 4.2.0 20060512 (experimental)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-25 Thread dir at lanl dot gov


--- Comment #15 from dir at lanl dot gov  2006-05-25 14:54 ---
At last one that works (I knew that I did the testsuite on this one) - version
20060405 -

[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060405 (experimental)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-25 Thread dir at lanl dot gov


--- Comment #16 from dir at lanl dot gov  2006-05-25 16:33 ---
Works at rev 112998 just before the updates for bug 27138 on April 17 -

[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060417 (experimental)
[dranta:~/tests/gfortran-D] dir% h


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-25 Thread dir at lanl dot gov


--- Comment #17 from dir at lanl dot gov  2006-05-25 20:53 ---
It runs after (bug fix 20257) rev 113373 and fails after (bug fix 27360) rev
113396. I think that narrows it down to one of two updates - if the problem was
caused by changes to gfortran.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug fortran/27683] Many new GFORTRAN testsuite failures

2006-05-26 Thread dir at lanl dot gov


--- Comment #21 from dir at lanl dot gov  2006-05-26 17:45 ---
It is rev 113395 that is causing the problem. I backed out that change and
built today's version of gfortran - it now correctly runs one of the tests that
has been failing - 

[dranta:~/tests/gfortran-D] dir% gfortran -O1 -o write_logical
write_logical.f90
[dranta:~/tests/gfortran-D] dir% write_logical
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.6.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060526 (experimental)
[dranta:~/tests/gfortran-D] dir% cat write_logical.f90
! PR 14334, L edit descriptor does not work
!
!  this test uses L1 and L4 to print TRUE and FALSE
   logical true,false
   character*10 b
   true = .TRUE.
   false = .FALSE.
   b = ''
   write (b, '(L1)') true
   if (b(1:1) .ne. 'T') call abort

   b = ''
   write (b, '(L1)') false
   if (b(1:1) .ne. 'F') call abort

   b = ''
   write(b, '(L4)') true
   if (b(1:4) .ne. '   T') call abort

   b = ''
   write(b, '(L4)') false
   if (b(1:4) .ne. '   F') call abort
   end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27683



[Bug target/27683] [4.2 Regression] Many new GFORTRAN testsuite failures

2006-05-26 Thread dir at lanl dot gov


--- Comment #23 from dir at lanl dot gov  2006-05-26 19:36 ---
Here is the good and the bad -

[dranta:~/tests/gfortran-D] dir% gfortran -O1 -save-temps -o write_logical2
write_logical2.f90
[dranta:~/tests/gfortran-D] dir% write_logical2
At line 9 of file write_logical2.f90
Fortran runtime error: Missing initial left parenthesis in format

[dranta:~/tests/gfortran-D] dir% cat write_logical2.f90
! PR 14334, L edit descriptor does not work
!
!  this test uses L1 and L4 to print TRUE and FALSE
   logical true,false
   character*10 b
   true = .TRUE.
   false = .FALSE.
   b = ''
   write (b, '(L1)') true
   if (b(1:1) .ne. 'T') call abort

   end
[dranta:~/tests/gfortran-D] dir% cat write_logical2.s
.machine ppc
.text
.align 2
.globl _MAIN__
_MAIN__:
mflr r0
stmw r28,-16(r1)
stw r0,8(r1)
stwu r1,-384(r1)
bcl 20,31,"L001$pb"
"L001$pb":
mflr r31
li r3,70
li r4,127
li r5,0
bl L__gfortran_set_std$stub
li r0,1
stw r0,56(r1)
addi r28,r1,60
addis r29,r31,ha16(LANCHOR0-"L001$pb")
la r29,lo16(LANCHOR0-"L001$pb")(r29)
li r3,10
mr r4,r28
li r5,0
mr r6,r29
bl L__gfortran_copy_string$stub
addis r2,r31,ha16(LC1-"L001$pb")
la r2,lo16(LC1-"L001$pb")(r2)
stw r2,80(r1)
li r0,9
stw r0,84(r1)
stw r28,132(r1)
li r0,10
stw r0,136(r1)
li r0,0
stw r0,112(r1)
stw r0,76(r1)
stw r29,116(r1)
li r0,4
stw r0,120(r1)
li r0,20480
stw r0,72(r1)
addi r29,r1,72
mr r3,r29
bl L__gfortran_st_write$stub
mr r3,r29
addi r4,r1,56
li r5,4
bl L__gfortran_transfer_logical$stub
mr r3,r29
bl L__gfortran_st_write_done$stub
lbz r0,60(r1)
cmpwi cr7,r0,84
beq+ cr7,L4
bl L__gfortran_abort$stub
L4:
addi r1,r1,384
lwz r0,8(r1)
mtlr r0
lmw r28,-16(r1)
blr
.const
.align 2
.setLANCHOR0, . + 0
LC0:
.space 1
LC2:
.ascii "(L1)"
.cstring
.align 2
LC1:
.ascii "write_logical2.f90\0"
.section __TEXT,__picsymbolstub1,symbol_stubs,pure_instructions,32
.align 5
L__gfortran_transfer_logical$stub:
.indirect_symbol __gfortran_transfer_logical
mflr r0
bcl 20,31,"L001$spb"
"L001$spb":
mflr r11
addis
r11,r11,ha16(L__gfortran_transfer_logical$lazy_ptr-"L001$spb")
mtlr r0
lwzu
r12,lo16(L__gfortran_transfer_logical$lazy_ptr-"L001$spb")(r11)
mtctr r12
bctr
.lazy_symbol_pointer
L__gfortran_transfer_logical$lazy_ptr:
.indirect_symbol __gfortran_transfer_logical
.long   dyld_stub_binding_helper
.section __TEXT,__picsymbolstub1,symbol_stubs,pure_instructions,32
.align 5
L__gfortran_st_write_done$stub:
.indirect_symbol __gfortran_st_write_done
mflr r0
bcl 20,31,"L002$spb"
"L002$spb":
mflr r11
addis
r11,r11,ha16(L__gfortran_st_write_done$lazy_ptr-"L002$spb")
mtlr r0
lwzu
r12,lo16(L__gfortran_st_write_done$lazy_ptr-"L002$spb")(r11)
mtctr r12
bctr
.lazy_symbol_pointer
L__gfortran_st_write_done$lazy_ptr:
.indirect_symbol __gfortran_st_write_done
.long   dyld_stub_binding_helper
.section __TEXT,__picsymbolstub1,symbol_stubs,pure_instructions,32
.align 5
L__gfortran_abort$stub:
.indirect_symbol __gfortran_abort
mflr r0
bcl 20,31,"L003$spb"
"L003$spb":
mflr r11
addis r11,r11,ha16(L__gfortran_abort$lazy_ptr-"L003$spb")
mtlr r0
lwzu r12,lo16(L__gfortran_abort$lazy_ptr-"L003$spb")(r11)
mtctr r12
bctr
.lazy_symbol_pointer
L__gfortran_abort$lazy_ptr:
.indirect_symbol __gfortran_abort
.long   dyld_stub_binding_helper
.section __TEXT,__picsymbolstub1,symbol_stubs,pure_instructions,32
.align 5
L__gfortran_set_std$stub:
.indirect_symbol __gfortran_set_std
mflr r0
bcl 20,31,"L004$spb"
"L004$spb":
mflr r11
addis r11,r11,ha16(L__gfortran_set_std$lazy_ptr-"L004$spb")
mtlr r0
lwzu r12,lo16(L__gfortran_set_std$lazy_ptr-"L004$spb")(r11)
mtctr r12
bctr
.lazy_symbol_pointer
L__gfortran_se

[Bug fortran/27561] [mingw32] floating-point extreme values are wrong

2006-05-30 Thread dir at lanl dot gov


--- Comment #5 from dir at lanl dot gov  2006-05-30 16:34 ---
It is strange - gfortran under cygwin does not seem to have the problem. I
wonder why GMP/MPFR is different under MSYS ? I also tried your test under MSYS
on my system and got the same answer (+one digit) that you got under linux -

$ gcc -o  mpfr  mpfr.c -lmpfr -lgmp

[EMAIL PROTECTED] /d/Docume~1/rantad/mydocu~1/tests
$ mpfr
2.000
1.192092895507812e-7

[EMAIL PROTECTED] /d/Docume~1/rantad/mydocu~1/tests
$ gcc --v
Reading specs from d:/MinGW/bin/../lib/gcc/mingw32/3.4.2/specs
Configured with: ../gcc/configure --with-gcc --with-gnu-ld --with-gnu-as
--host=mingw32 --target=mingw32 --prefix=/mingw --enable-threads --disable-nls
--enable-languages=c,c++,f77,ada,objc,java --disable-win32-registry
--disable-shared --enable-sjlj-exceptions --enable-libgcj --disable-java-awt
--without-x --enable-java-gc=boehm --disable-libgcj-debug --enable-interpreter
--enable-hash-synchronization --enable-libstdcxx-debug
Thread model: win32
gcc version 3.4.2 (mingw-special)

[EMAIL PROTECTED] /d/Docume~1/rantad/mydocu~1/tests


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27561



[Bug fortran/27561] [mingw32] floating-point extreme values are wrong

2006-05-30 Thread dir at lanl dot gov


--- Comment #6 from dir at lanl dot gov  2006-05-30 17:01 ---
I also forced it to use the gcc that came with gfortran getting the same
result. I built with mpfr-2.1.2 and gmp-4.1.4 a while ago when I unsucessfully
tried to build gfortran on my PC. I noticed your MSYS version is printing 16
places (on the 2) after the decimal point where mine is printing 15 and linux
is doing 14.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27561



[Bug fortran/28411] New: gfortran: Internal error: Illegal instruction

2006-07-17 Thread dir at lanl dot gov
I was trying to capture floating points exceptions on the Intel iMac - I am not
sure what options to use, but the gfortran crashes on the iMac and on Linux
with these options on this program -

[pactech01:~/sage/sage20060707] dir% gfortran -c -O2 -mfpmath=sse -msse -msse2
-ffpe-trap=invalid,zero,overflow -ftrapping-math -ftrapv -fmath-errno
module_utilities2.f90
gfortran: Internal error: Illegal instruction (program f951)
Please submit a full bug report.
See http://gcc.gnu.org/bugs.html> for instructions.
[pactech01:~/sage/sage20060707] dir% cat module_utilities2.f90
module utilities_module

  implicit none
  integer, parameter :: INT4  = SELECTED_INT_KIND(6)
  integer, parameter :: INT8  = SELECTED_INT_KIND(16)
  integer, parameter :: REAL4 = SELECTED_REAL_KIND(6)
  integer, parameter :: REAL8 = SELECTED_REAL_KIND(12)

  save
  private


!
==
contains
!
--
  subroutine test_check_sums



integer, parameter :: SIZE = 10



integer   :: array_i4(SIZE)
integer(INT8) :: array_i8(SIZE)
real(REAL8)   :: array_r8(SIZE)
real(REAL4)   :: array_r4(SIZE)
integer   :: n


  do n = 1,SIZE
array_i4(n) = int(-3*n, INT4)
array_i8(n) = int(-3*n, INT8)
array_r4(n) = real(-3*n, REAL4)
array_r8(n) = real(-3*n, REAL8)
  enddo ! n


  end subroutine test_check_sums
!
--
end module utilities_module
!
==
[pactech01:~/sage/sage20060707] dir% gfortran --v
Using built-in specs.
Target: i386-apple-darwin8.6.1
Configured with: ../gcc/configure --prefix=/usr/local/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060522 (experimental)
[pactech01:~/sage/sage20060707] dir%


-- 
   Summary: gfortran: Internal error: Illegal instruction
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28411



[Bug fortran/24710] New: gfortran - fails to build on Mac OSX -10.4.3

2005-11-07 Thread dir at lanl dot gov
_s.o
libgcc/ppc64/_fixsfdi_s.o libgcc/ppc64/_fixxfdi_s.o
libgcc/ppc64/_fixunsxfdi_s.o libgcc/ppc64/_floatdixf_s.o
libgcc/ppc64/_fixunsxfsi_s.o libgcc/ppc64/_fixtfdi_s.o
libgcc/ppc64/_fixunstfdi_s.o libgcc/ppc64/_floatditf_s.o
libgcc/ppc64/_clear_cache_s.o libgcc/ppc64/_enable_execute_stack_s.o
libgcc/ppc64/_trampoline_s.o libgcc/ppc64/__main_s.o libgcc/ppc64/_absvsi2_s.o
libgcc/ppc64/_absvdi2_s.o libgcc/ppc64/_addvsi3_s.o libgcc/ppc64/_addvdi3_s.o
libgcc/ppc64/_subvsi3_s.o libgcc/ppc64/_subvdi3_s.o libgcc/ppc64/_mulvsi3_s.o
libgcc/ppc64/_mulvdi3_s.o libgcc/ppc64/_negvsi2_s.o libgcc/ppc64/_negvdi2_s.o
libgcc/ppc64/_ctors_s.o libgcc/ppc64/_ffssi2_s.o libgcc/ppc64/_ffsdi2_s.o
libgcc/ppc64/_clz_s.o libgcc/ppc64/_clzsi2_s.o libgcc/ppc64/_clzdi2_s.o
libgcc/ppc64/_ctzsi2_s.o libgcc/ppc64/_ctzdi2_s.o
libgcc/ppc64/_popcount_tab_s.o libgcc/ppc64/_popcountsi2_s.o
libgcc/ppc64/_popcountdi2_s.o libgcc/ppc64/_paritysi2_s.o
libgcc/ppc64/_paritydi2_s.o libgcc/ppc64/_powisf2_s.o libgcc/ppc64/_powidf2_s.o
libgcc/ppc64/_powixf2_s.o libgcc/ppc64/_powitf2_s.o libgcc/ppc64/_mulsc3_s.o
libgcc/ppc64/_muldc3_s.o libgcc/ppc64/_mulxc3_s.o libgcc/ppc64/_multc3_s.o
libgcc/ppc64/_divsc3_s.o libgcc/ppc64/_divdc3_s.o libgcc/ppc64/_divxc3_s.o
libgcc/ppc64/_divtc3_s.o libgcc/ppc64/_divdi3_s.o libgcc/ppc64/_moddi3_s.o
libgcc/ppc64/_udivdi3_s.o libgcc/ppc64/_umoddi3_s.o
libgcc/ppc64/_udiv_w_sdiv_s.o libgcc/ppc64/_udivmoddi4_s.o
libgcc/ppc64/darwin-tramp_s.o libgcc/ppc64/darwin-ldouble_s.o
libgcc/ppc64/unwind-dw2_s.o libgcc/ppc64/unwind-dw2-fde-darwin_s.o
libgcc/ppc64/unwind-sjlj_s.o libgcc/ppc64/unwind-c_s.o
libgcc/ppc64/darwin-fallback_s.o -lc && if [ -f libgcc_s`if test ppc64 != . ;
then echo _ppc64 ; fi`.1.dylib ]; then mv -f libgcc_s`if test ppc64 != . ; then
echo _ppc64 ; fi`.1.dylib libgcc_s`if test ppc64 != . ; then echo _ppc64 ;
fi`.1.dylib.backup; else true; fi && mv libgcc_s`if test ppc64 != . ; then echo
_ppc64 ; fi`.1.dylib.tmp libgcc_s`if test ppc64 != . ; then echo _ppc64 ;
fi`.1.dylib
# When builting multilibbed target libraries, all the required
# libraries are expected to exist in the multilib directory.
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.2.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.2.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.2.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.2.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.2.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.2.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d'` ; \
for mlib in $MLIBS ; do \
  rm -f ${mlib}/libgcc_s.10.4.dylib || exit 1 ; \
  ln -s ../libgcc_s.10.4.dylib ${mlib}/libgcc_s.10.4.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.2.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.2.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.2.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.2.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.2.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.2.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.4.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.4.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
Could Not Open (-o) To Read
make[2]: *** [libgcc_s.10.4.dylib] Error 1
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2


-- 
   Summary: gfortran - fails to build on Mac OSX -10.4.3
   Product: gcc
   Version: 4.1.0
Status: UNCONFIRMED
  Severity: normal
      Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-07 Thread dir at lanl dot gov


--- Comment #2 from dir at lanl dot gov  2005-11-07 16:11 ---
It failed under 10.4.2 from a completely new down load - then I upgraded to
10.4.3 to see if that would help.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-07 Thread dir at lanl dot gov


--- Comment #3 from dir at lanl dot gov  2005-11-07 16:47 ---
Here is another try from another complete download under 10.4.3 -


# When builting multilibbed target libraries, all the required
# When builting multilibbed target libraries, all the required
# libraries are expected to exist in the multilib directory.
# libraries are expected to exist in the multilib directory.
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d'` ; \
for mlib in $MLIBS ; do \
  rm -f ${mlib}/libgcc_s.10.4.dylib || exit 1 ; \
  ln -s ../libgcc_s.10.4.dylib ${mlib}/libgcc_s.10.4.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d'` ; \
for mlib in $MLIBS ; do \
  rm -f ${mlib}/libgcc_s.10.5.dylib || exit 1 ; \
  ln -s ../libgcc_s.10.5.dylib ${mlib}/libgcc_s.10.5.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.4.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.4.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.5.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.5.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
Could Not Open (-o) To Read
Could Not Open (-o) To Read
make[2]: *** [libgcc_s.10.5.dylib] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** [libgcc_s.10.4.dylib] Error 1
rm cpp.pod gfortran.pod fsf-funding.pod gpl.pod gcc.pod gcov.pod gfdl.pod
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-07 Thread dir at lanl dot gov


--- Comment #5 from dir at lanl dot gov  2005-11-07 19:17 ---
I do the get with -

[dranta:~/utlib] dir% cat gfortranGet
cvs -d :ext:[EMAIL PROTECTED]:/cvsroot/gcc co gcc

I do the configure with -

[dranta:~/utlib] dir% cat gfortranConfig
configure --prefix=/Users/dir/gfortran --enable-languages=c,f95


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-07 Thread dir at lanl dot gov


--- Comment #6 from dir at lanl dot gov  2005-11-07 19:19 ---
I have a dual 2.5 GHZ PowerPC G5


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-07 Thread dir at lanl dot gov


--- Comment #8 from dir at lanl dot gov  2005-11-07 21:14 ---
If -

cvs -d :ext:[EMAIL PROTECTED]:/cvsroot/gcc co gcc

is now wrong, what is the correct CVS command to use ?


Changing the directory make no difference, I have done exactly the same thing
for the last year or so and I had trouble building gfortran on the macintosh
only one other time -

configure --prefix=/Users/dir/bin --enable-languages=c,f95
make -j 4
...
...



for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.4.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.4.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.5.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.5.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
Could Not Open (-o) To Read
make[2]: *** [libgcc_s.10.4.dylib] Error 1
make[2]: *** Waiting for unfinished jobs
Could Not Open (-o) To Read
make[2]: *** [libgcc_s.10.5.dylib] Error 1
rm cpp.pod gfortran.pod fsf-funding.pod gpl.pod gcc.pod gcov.pod gfdl.pod
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-08 Thread dir at lanl dot gov


--- Comment #10 from dir at lanl dot gov  2005-11-08 14:18 ---
The make bootstrap ends with -

make bootstrap
...
...
checking for .preinit_array/.init_array/.fini_array support... no
checking if mkdir takes one argument... no
Using `../.././gcc/config/rs6000/rs6000.c' for machine-specific logic.
Using `../.././gcc/config/rs6000/rs6000.md' as machine description file.
Using the following target machine macro files:
../.././gcc/config/rs6000/rs6000.h
../.././gcc/config/darwin.h
../.././gcc/config/rs6000/darwin.h
../.././gcc/config/rs6000/darwin8.h
Using host-darwin.o host-ppc-darwin.o for host machine hooks.
checking whether NLS is requested... yes
checking for catalogs to be installed...  be ca da de el es fr ja nl rw sv tr
zh_CN
checking what assembler to use... /usr/bin/as
checking what linker to use... /usr/bin/ld
checking what nm to use... /usr/bin/nm
checking what objdump to use... /Users/dir/bin/bin/objdump
checking assembler for .balign and .p2align... no
checking assembler for .p2align with maximum skip... yes
checking assembler for working .subsection -1... no
checking assembler for .weak... no
checking assembler for .nsubspa comdat... no
checking assembler for .hidden... no
checking linker for .hidden support... no
checking assembler for .sleb128 and .uleb128... no
checking assembler for eh_frame optimization... no
checking assembler for section merging support... no
checking assembler for section merging support... (cached) no
checking assembler for COMDAT group support... no
checking assembler for COMDAT group support... no
checking assembler for thread-local storage support... no
checking linker -Bstatic/-Bdynamic option... no
checking assembler for .machine directive support... yes
checking assembler for mfcr field support... yes
checking assembler for popcntb support... no
checking assembler for rel16 relocs... no
checking assembler for dwarf2 debug_line support... no
checking assembler for buggy dwarf2 .file directive... no
checking assembler for --gdwarf2 option... no
checking assembler for --gstabs option... yes
checking linker read-only and read-write section mixing... unknown
checking linker PT_GNU_EH_FRAME support... no
checking linker position independent executable support... no
checking linker --as-needed support... no
checking linker --sysroot support... no
Using ggc-page for garbage collection.
checking whether to enable maintainer-specific portions of Makefiles... no
Links are now set up to build a native compiler for powerpc-apple-darwin8.3.0.
updating cache ./config.cache
configure: creating ./config.status
config.status: creating Makefile
config.status: creating gccbug
config.status: creating mklibgcc
config.status: creating libada-mk
config.status: creating auto-host.h
config.status: executing default commands
Bootstrapping the compiler
make[1]: *** No rule to make target `bootstrap'.  Stop.
make: *** [bootstrap] Error 2


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-08 Thread dir at lanl dot gov


--- Comment #11 from dir at lanl dot gov  2005-11-08 15:15 ---
Down loading gfortran using svn took 40 percent longer and gave the same
results on the build -

By the way the GNU Fortran Page -

http://gcc.gnu.org/fortran/

still says to use anonymous CVS






MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d'` ; \
for mlib in $MLIBS ; do \
  rm -f ${mlib}/libgcc_s.10.4.dylib || exit 1 ; \
  ln -s ../libgcc_s.10.4.dylib ${mlib}/libgcc_s.10.4.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.4.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.4.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.5.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.5.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
Could Not Open (-o) To Read
Could Not Open (-o) To Read
make[2]: *** [libgcc_s.10.5.dylib] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** [libgcc_s.10.4.dylib] Error 1
rm cpp.pod gfortran.pod fsf-funding.pod gpl.pod gcc.pod gcov.pod gfdl.pod
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-08 Thread dir at lanl dot gov


--- Comment #13 from dir at lanl dot gov  2005-11-08 18:14 ---

Here is what I do -

12  9:21mkdir gfortran
13  9:21cd gfortran
14  9:25svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
15  9:56cd gcc
16  9:56configure --prefix=/Users/dir/bin --enable-languages=c,f95
17  9:57make -j 4


MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d'` ; \
for mlib in $MLIBS ; do \
  rm -f ${mlib}/libgcc_s.10.5.dylib || exit 1 ; \
  ln -s ../libgcc_s.10.5.dylib ${mlib}/libgcc_s.10.5.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.4.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.4.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.5.dylib_T${mlib} \
-s ../.././gcc/config/rs6000/darwin-libgcc.10.5.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
Could Not Open (-o) To Read
make[2]: Could Not Open (-o) To Read
*** [libgcc_s.10.4.dylib] Error 1
make[2]: *** Waiting for unfinished jobs
make[2]: *** [libgcc_s.10.5.dylib] Error 1
rm cpp.pod gfortran.pod fsf-funding.pod gpl.pod gcc.pod gcov.pod gfdl.pod
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-08 Thread dir at lanl dot gov


--- Comment #15 from dir at lanl dot gov  2005-11-08 21:46 ---

The problem is still there -



34  13:14   svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
35  13:29   cd gcc
36  13:30   mkdir objdir
37  13:30   cd objdir
38  13:30   ../configure --prefix=/Users/dir/bin --enable-languages=c,f95
39  13:30   make -j 4

for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.5.dylib_T${mlib} \
-s ../../gcc/config/rs6000/darwin-libgcc.10.5.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
MLIBS=`/Users/dir/gfortran/gcc/objdir/./gcc/xgcc
-B/Users/dir/gfortran/gcc/objdir/./gcc/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/bin/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/bin/powerpc-apple-darwin8.3.0/sys-include --print-multi-lib \
| sed -e 's/;.*$//' -e '/^\.$/d' -e 's/^/_/'` ; \
for mlib in '' $MLIBS ; do \
  strip -o libgcc_s.10.4.dylib_T${mlib} \
-s ../../gcc/config/rs6000/darwin-libgcc.10.4.ver -c -u \
libgcc_s${mlib}.1.dylib || exit 1 ; \
done
Could Not Open (-o) To Read
make[2]: *** [libgcc_s.10.5.dylib] Error 1Could Not Open (-o) To Read

make[2]: *** Waiting for unfinished jobs
make[2]: *** [libgcc_s.10.4.dylib] Error 1
rm cpp.pod gcov.pod gfortran.pod gpl.pod fsf-funding.pod gcc.pod gfdl.pod
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2
[dranta:~/gfortran/gcc/objdir] dir% 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-09 Thread dir at lanl dot gov


--- Comment #18 from dir at lanl dot gov  2005-11-09 15:13 ---
That was it - my system had two versions of strip. 

Thanks,
Dale


The final library build has some warning messages, but they do not seem to hurt
anything -

ranlib -c .libs/libgfortranbegin.a
creating libgfortranbegin.la
(cd .libs && rm -f libgfortranbegin.la && ln -s ../libgfortranbegin.la
libgfortranbegin.la)
/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include  -m64 -dynamiclib
-flat_namespace -undefined suppress -o .libs/libgfortran.0.0.0.dylib 
.libs/compile_options.o .libs/environ.o .libs/error.o .libs/fpu.o .libs/main.o
.libs/memory.o .libs/pause.o .libs/stop.o .libs/string.o .libs/select.o
.libs/all_l4.o .libs/all_l8.o .libs/all_l16.o .libs/any_l4.o .libs/any_l8.o
.libs/any_l16.o .libs/count_4_l4.o .libs/count_8_l4.o .libs/count_16_l4.o
.libs/count_4_l8.o .libs/count_8_l8.o .libs/count_16_l8.o .libs/count_4_l16.o
.libs/count_8_l16.o .libs/count_16_l16.o .libs/maxloc0_4_i4.o
.libs/maxloc0_8_i4.o .libs/maxloc0_16_i4.o .libs/maxloc0_4_i8.o
.libs/maxloc0_8_i8.o .libs/maxloc0_16_i8.o .libs/maxloc0_4_i16.o
.libs/maxloc0_8_i16.o .libs/maxloc0_16_i16.o .libs/maxloc0_4_r4.o
.libs/maxloc0_8_r4.o .libs/maxloc0_16_r4.o .libs/maxloc0_4_r8.o
.libs/maxloc0_8_r8.o .libs/maxloc0_16_r8.o .libs/maxloc0_4_r10.o
.libs/maxloc0_8_r10.o .libs/maxloc0_16_r10.o .libs/maxloc0_4_r16.o
.libs/maxloc0_8_r16.o .libs/maxloc0_16_r16.o .libs/maxloc1_4_i4.o
.libs/maxloc1_8_i4.o .libs/maxloc1_16_i4.o .libs/maxloc1_4_i8.o
.libs/maxloc1_8_i8.o .libs/maxloc1_16_i8.o .libs/maxloc1_4_i16.o
.libs/maxloc1_8_i16.o .libs/maxloc1_16_i16.o .libs/maxloc1_4_r4.o
.libs/maxloc1_8_r4.o .libs/maxloc1_16_r4.o .libs/maxloc1_4_r8.o
.libs/maxloc1_8_r8.o .libs/maxloc1_16_r8.o .libs/maxloc1_4_r10.o
.libs/maxloc1_8_r10.o .libs/maxloc1_16_r10.o .libs/maxloc1_4_r16.o
.libs/maxloc1_8_r16.o .libs/maxloc1_16_r16.o .libs/maxval_i4.o
.libs/maxval_i8.o .libs/maxval_i16.o .libs/maxval_r4.o .libs/maxval_r8.o
.libs/maxval_r10.o .libs/maxval_r16.o .libs/minloc0_4_i4.o .libs/minloc0_8_i4.o
.libs/minloc0_16_i4.o .libs/minloc0_4_i8.o .libs/minloc0_8_i8.o
.libs/minloc0_16_i8.o .libs/minloc0_4_i16.o .libs/minloc0_8_i16.o
.libs/minloc0_16_i16.o .libs/minloc0_4_r4.o .libs/minloc0_8_r4.o
.libs/minloc0_16_r4.o .libs/minloc0_4_r8.o .libs/minloc0_8_r8.o
.libs/minloc0_16_r8.o .libs/minloc0_4_r10.o .libs/minloc0_8_r10.o
.libs/minloc0_16_r10.o .libs/minloc0_4_r16.o .libs/minloc0_8_r16.o
.libs/minloc0_16_r16.o .libs/minloc1_4_i4.o .libs/minloc1_8_i4.o
.libs/minloc1_16_i4.o .libs/minloc1_4_i8.o .libs/minloc1_8_i8.o
.libs/minloc1_16_i8.o .libs/minloc1_4_i16.o .libs/minloc1_8_i16.o
.libs/minloc1_16_i16.o .libs/minloc1_4_r4.o .libs/minloc1_8_r4.o
.libs/minloc1_16_r4.o .libs/minloc1_4_r8.o .libs/minloc1_8_r8.o
.libs/minloc1_16_r8.o .libs/minloc1_4_r10.o .libs/minloc1_8_r10.o
.libs/minloc1_16_r10.o .libs/minloc1_4_r16.o .libs/minloc1_8_r16.o
.libs/minloc1_16_r16.o .libs/minval_i4.o .libs/minval_i8.o .libs/minval_i16.o
.libs/minval_r4.o .libs/minval_r8.o .libs/minval_r10.o .libs/minval_r16.o
.libs/product_i4.o .libs/product_i8.o .libs/product_i16.o .libs/product_r4.o
.libs/product_r8.o .libs/product_r10.o .libs/product_r16.o .libs/product_c4.o
.libs/product_c8.o .libs/product_c10.o .libs/product_c16.o .libs/sum_i4.o
.libs/sum_i8.o .libs/sum_i16.o .libs/sum_r4.o .libs/sum_r8.o .libs/sum_r10.o
.libs/sum_r16.o .libs/sum_c4.o .libs/sum_c8.o .libs/sum_c10.o .libs/sum_c16.o
.libs/dotprod_i4.o .libs/dotprod_i8.o .libs/dotprod_i16.o .libs/dotprod_r4.o
.libs/dotprod_r8.o .libs/dotprod_r10.o .libs/dotprod_r16.o .libs/dotprod_l4.o
.libs/dotprod_l8.o .libs/dotprod_l16.o .libs/dotprod_c4.o .libs/dotprod_c8.o
.libs/dotprod_c10.o .libs/dotprod_c16.o .libs/matmul_i4.o .libs/matmul_i8.o
.libs/matmul_i16.o .libs/matmul_r4.o .libs/matmul_r8.o .libs/matmul_r10.o
.libs/matmul_r16.o .libs/matmul_c4.o .libs/matmul_c8.o .libs/matmul_c10.o
.libs/matmul_c16.o .libs/matmul_l4.o .libs/matmul_l8.o .libs/matmul_l16.o
.libs/transpose_i4.o .libs/transpose_i8.o .libs/transpose_i16.o
.libs/transpose_c4.o .libs/transpose_c8.o .libs/transpose_c10.o
.libs/transpose_c16.o .libs/shape_i4.o .libs/shape_i8.o .libs/shape_i16.o
.libs/eoshift1_4.o .libs/eoshift1_8.o .libs/eoshift1_16.o .libs/eoshift3_4.o
.libs/eoshift3_8.o .libs/eoshift3_16.o .libs/cshift1_4.o .libs/cshift1_8.o
.libs/cshift1_16.o .libs/reshape_i4.o .libs/reshape_i8.o .libs/reshape_i16.o
.libs/reshape_c4.o .libs/reshape_c8.o .libs/reshape_c10.o .libs/reshape_c16.o
.libs/in_pack_i4.o .libs/in_pack_i8.o .libs/in_pack_i16.o .libs/in_pack_c4.o
.libs/in_pack_c8.o .libs/in_pack_c10.o .libs/in_pack_c16.o .libs/in_unpack_i4.o
.libs/in_unpack_i8.o .libs/in_unpack_i16.o .libs/in_u

[Bug bootstrap/24710] gfortran - fails to build on Mac OSX -10.4.3

2005-11-09 Thread dir at lanl dot gov


--- Comment #20 from dir at lanl dot gov  2005-11-09 15:29 ---
It was in /usr/local/bin along with a 100 or so other programs - I suppose that
one of them installed it .


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24710



[Bug fortran/24988] New: gfortran build fails with - Undefined symbols

2005-11-22 Thread dir at lanl dot gov
: ld returned 1 exit status
make[2]: *** [cc1-dummy] Error 1
make[2]: *** Waiting for unfinished jobs
/usr/bin/ld: warning multiple definitions of symbol _locale_charset
./../intl/libintl.a(localcharset.o) definition of _locale_charset in section
(__TEXT,__text)
/usr/lib/gcc/powerpc-apple-darwin8/4.0.0/../../../libiconv.dylib(localcharset.o)
definition of _locale_charset
rm cpp.pod gfortran.pod fsf-funding.pod gpl.pod gcc.pod gcov.pod gfdl.pod
make[1]: *** [all-gcc] Error 2
make: *** [all] Error 2


-- 
   Summary: gfortran build fails with - Undefined symbols
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24988



[Bug libfortran/24991] New: gfortran build fails with - error:gthr-default.h: No such file or directory

2005-11-22 Thread dir at lanl dot gov
With a new download of gfortran, the build now fails while building libgfortran
with -

make  all-am
/bin/sh ./libtool --mode=compile
/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include -DHAVE_CONFIG_H -I.
-I../.././libgfortran -I.  -iquote../.././libgfortran/io
-I../.././libgfortran/../gcc -I../.././libgfortran/../gcc/config -I../../gcc
-D_GNU_SOURCE  -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wextra -Wwrite-strings -O2 -g -O2  -c -o environ.lo
`test -f 'runtime/environ.c' || echo '../.././libgfortran/'`runtime/environ.c
/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/xgcc
-B/Users/dir/gfortran/gcc/host-powerpc-apple-darwin8.3.0/gcc/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/bin/
-B/Users/dir/gfortran/powerpc-apple-darwin8.3.0/lib/ -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/include -isystem
/Users/dir/gfortran/powerpc-apple-darwin8.3.0/sys-include -DHAVE_CONFIG_H -I.
-I../.././libgfortran -I. -iquote../.././libgfortran/io
-I../.././libgfortran/../gcc -I../.././libgfortran/../gcc/config -I../../gcc
-D_GNU_SOURCE -std=gnu99 -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wextra -Wwrite-strings -O2 -g -O2 -c
../.././libgfortran/runtime/environ.c  -fno-common -DPIC -o .libs/environ.o
In file included from ../.././libgfortran/runtime/../io/io.h:39,
 from ../.././libgfortran/runtime/environ.c:37:
../.././libgfortran/../gcc/gthr.h:114:26: error: gthr-default.h: No such file
or directory
In file included from ../.././libgfortran/runtime/environ.c:37:
../.././libgfortran/runtime/../io/io.h:465: error: expected
specifier-qualifier-list before '__gthread_mutex_t'
../.././libgfortran/runtime/../io/io.h:660: error: expected '=', ',', ';',
'asm' or '__attribute__' before 'unit_lock'
../.././libgfortran/runtime/../io/io.h:661: error: 'unit_lock' undeclared here
(not in a function)
../.././libgfortran/runtime/../io/io.h:661: warning: type defaults to 'int' in
declaration of 'unit_lock'
../.././libgfortran/runtime/../io/io.h: In function 'inc_waiting_locked':
../.././libgfortran/runtime/../io/io.h:836: error: 'gfc_unit' has no member
named 'waiting'
../.././libgfortran/runtime/../io/io.h:836: error: incompatible type for
argument 1 of '__sync_fetch_and_add'
../.././libgfortran/runtime/../io/io.h: In function 'predec_waiting_locked':
../.././libgfortran/runtime/../io/io.h:846: error: 'gfc_unit' has no member
named 'waiting'
../.././libgfortran/runtime/../io/io.h:846: error: incompatible type for
argument 1 of '__sync_add_and_fetch'
../.././libgfortran/runtime/../io/io.h: In function 'dec_waiting_unlocked':
../.././libgfortran/runtime/../io/io.h:856: error: 'gfc_unit' has no member
named 'waiting'
../.././libgfortran/runtime/../io/io.h:856: error: incompatible type for
argument 1 of '__sync_fetch_and_add'
make[3]: *** [environ.lo] Error 1
make[2]: *** [all] Error 2
make[1]: *** [all-target-libgfortran] Error 2
make: *** [all] Error 2


-- 
   Summary: gfortran build fails with - error:gthr-default.h: No
such file or directory
       Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991



[Bug libfortran/24991] [4.1/4.2 Regression] gfortran build fails with - error:gthr-default.h: No such file or directory

2005-11-23 Thread dir at lanl dot gov


--- Comment #2 from dir at lanl dot gov  2005-11-23 14:09 ---
I applied the patch to what I had yesterday and did a make and install. I build
a program with it but the program would not run. I got -

[dranta:~/sage/ibar/ibarOne] dir% rage2005GF.x ibarOne.input
dyld: lazy symbol binding failed: Symbol not found: ___gthrw_pthread_mutex_lock
  Referenced from: /Users/dir/gfortran/lib/libgfortran.1.dylib
  Expected in: flat namespace

dyld: Symbol not found: ___gthrw_pthread_mutex_lock
  Referenced from: /Users/dir/gfortran/lib/libgfortran.1.dylib
  Expected in: flat namespace

Trace/BPT trap
[dranta:~/sage/ibar/ibarOne] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ./configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20051122 (experimental)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991



[Bug libfortran/24991] [4.1/4.2 Regression] gfortran build fails with - error:gthr-default.h: No such file or directory

2005-11-23 Thread dir at lanl dot gov


--- Comment #5 from dir at lanl dot gov  2005-11-23 17:47 ---
Nothing called gthrw_pthread_mutex_lock (Darwin only has pthread_mutex_lock)is
in any of the libraries as a terminator. If I run gcc directly, I do not know
how to get all the flags set correctly to get a meaningful preprocessed output
from environ.c - is there some macro that will pick up all the required
parameters for this configuration ? When I touched environ.c and did another
make - I found some warning messages in the output about the thread routines. 

can't find atom for N_GSYM stabs
compile_options:G(0,5)=(0,6)=s8warn_std:(0,4),0,32;allow_std:(0,4),32,32;; in
.libs/compile_options.o
can't find atom for N_GSYM stabs
options:G(0,25)=(0,26)=s80stdin_unit:(0,8),0,32;stdout_unit:(0,8),32,32;stderr_unit:(0,8),64,32;optional_plus:(0,8),96,32;allocate_init_flag:(0,8),128,32;allocate_init_value:(0,8),160,32;locus:(0,8),192,32;separator_len:(0,8),224,32;separator:(0,5),256,64;mem_check:(0,8),320,32;use_stderr:(0,8),352,32;all_unbuffered:(0,8),384,32;default_recl:(0,8),416,32;fpu_round:(0,8),448,32;fpu_precision:(0,8),480,32;fpe:(0,8),512,32;sighup:(0,8),544,32;sigint:(0,8),576,32;;
in .libs/environ.o
can't find atom for N_GSYM stabs l8_to_l4_offset:G(0,2) in .libs/main.o
ld: warning weak symbol references not set in output with
MACOSX_DEPLOYMENT_TARGET environment variable set to: 10.1
ld: warning weak referenced symbols:
_pthread_cancel
_pthread_mutex_lock
_pthread_mutex_trylock
_pthread_mutex_unlock
can't find atom for N_GSYM stabs max_offset:G(0,30) in .libs/unit.o
can't find atom for N_GSYM stabs unit_root:G(0,1) in .libs/unit.o
can't find atom for N_GSYM stabs unit_lock:G(0,35) in .libs/unit.o


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991



[Bug libfortran/24991] [4.1/4.2 Regression] gfortran build fails with - error:gthr-default.h: No such file or directory

2005-11-23 Thread dir at lanl dot gov


--- Comment #7 from dir at lanl dot gov  2005-11-23 19:45 ---
I did a complete rebuild with the same results  -

mkdir gfortran
cd gfortran
svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
cd gcc
patch -p0 < /Users/dir/Desktop/gcc41-pr24991.patch
configure --prefix=/Users/dir/gfortran --enable-languages=c,f95
make -j 4
make install




[dranta:~/sage/ibar/ibarOne] dir% rage2005GF.x ibarOne.input
dyld: lazy symbol binding failed: Symbol not found: ___gthrw_pthread_mutex_lock
  Referenced from: /Users/dir/gfortran/lib/libgfortran.1.dylib
  Expected in: flat namespace

dyld: Symbol not found: ___gthrw_pthread_mutex_lock
  Referenced from: /Users/dir/gfortran/lib/libgfortran.1.dylib
  Expected in: flat namespace

Trace/BPT trap

I built a new version last week and it works fine -

[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ./configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.1.0 20051114 (experimental)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991



[Bug libfortran/24991] [4.1/4.2 Regression] gfortran build fails with - error:gthr-default.h: No such file or directory

2005-11-23 Thread dir at lanl dot gov


--- Comment #9 from dir at lanl dot gov  2005-11-23 21:18 ---
Created an attachment (id=10329)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10329&action=view)
The preprocessed output for environ.c

The preprocessed output for environ.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991



[Bug libfortran/24991] [4.1/4.2 Regression] gfortran build fails with - error:gthr-default.h: No such file or directory

2005-11-23 Thread dir at lanl dot gov


--- Comment #11 from dir at lanl dot gov  2005-11-23 22:09 ---
Created an attachment (id=10330)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10330&action=view)
nm of  the gfortran libraries

References to the "gthrw" routines seem to be everywhere.
(I am out of here till next Monday)


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991



[Bug libfortran/24991] [4.1/4.2 Regression] gfortran build fails with - error:gthr-default.h: No such file or directory

2005-11-28 Thread dir at lanl dot gov


--- Comment #36 from dir at lanl dot gov  2005-11-28 15:53 ---
With patches "gcc41-pr24991.patch" (I also need this to build on LINUX) and
"gcc-weakref-darwin.patch" (the patch gcc/ChangeLog  failed, but that did not
matter) installed and a fresh down load of gfortran, gfortran builds and I have
used the newly created gfortran to compile and run three of my programs -

   Thanks All.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24991



[Bug libfortran/25139] New: Fortran runtime error: Invalid argument

2005-11-28 Thread dir at lanl dot gov
I have been getting this error on one of my programs that does extremely
complex I/O operations for a few months now, but I have been unable to isolate
it. I finally got the same error message from a program that generates random
I/O patterns. About half of the FORTRANS that I run this program with fail, but
I found four including Lahey Fortran and Compaq Fortran that have no complain.
testio.f is the original program. testio2.f is a program made from the output
of testio.f that duplicates the I/O sequence that failed.

[dranta:~/tests/gfortran-D] dir% gfortran -o testio testio.f
[dranta:~/tests/gfortran-D] dir% testio > out
At line 37 of file testio.f
Fortran runtime error: Invalid argument
[dranta:~/tests/gfortran-D] dir% cat testio.f
  program test
  dimension ia(100)
  i=rand(500)
  do 10 i=1,100
  call doio(ia,100)
   10 continue
  stop
  end
  subroutine doio(ia,n)
  dimension ia(n)
  i=1
   10 continue
  ia(i)=1+3*rand(0)+.5
  if(i.gt.1)then
  if(ia(i-1).eq.4.and.ia(i).eq.3)goto 10
  endif
  i=i+1
  if(i.le.n)goto 10
  write(6,1000)ia
  call dowrite(ia,n)
  return
 1000 format(20i4)
  end
  subroutine dowrite(ia,n)
  dimension ia(n)
  dimension data(500)
  nend=1000
  open(unit=11,status='scratch',form='unformatted')
  do 100 i=1,n
  goto (10,20,30,40),ia(i)
  10  continue
  write(6,*)'  rewind 11'
  rewind 11
  goto 100
  20  continue
  write(6,*)'  backspace 11'
  backspace 11
  goto 100
  30  continue
  write(6,*)'  read(11,end=',nend,')data'
  write(6,1000)nend
  nend=nend+1 
  read(11,end=50)data
  goto 100
  40  continue
  write(6,*)'  write(11)data'
  write(11)data
  goto 100
  50  continue
  write(6,*)'  backspace 11'
  backspace 11
  goto 100
 100  continue
  close(11)
  return
1000  format(' ',i4,'  continue')
  end
[dranta:~/tests/gfortran-D] dir% gfortran -o testio2 testio2.f
[dranta:~/tests/gfortran-D] dir% testio2
At line 72 of file testio2.f
Fortran runtime error: Invalid argument
[dranta:~/tests/gfortran-D] dir% cat testio2.f
  program test
  dimension data(100)
   read(11,end=1000 )data
 1000  continue
   backspace 11
   backspace 11
   backspace 11
   read(11,end=1001 )data
 1001  continue
   backspace 11
   rewind 11
   backspace 11
   backspace 11
   backspace 11
   rewind 11
   write(11)data
   backspace 11
   backspace 11
   backspace 11
   backspace 11
   backspace 11
   backspace 11
   rewind 11
   backspace 11
   write(11)data
   write(11)data
   write(11)data
   backspace 11
   read(11,end=1002 )data
 1002  continue
   backspace 11
   rewind 11
   backspace 11
   read(11,end=1003 )data
 1003  continue
   write(11)data
   write(11)data
   write(11)data
   rewind 11
   read(11,end=1004 )data
 1004  continue
   rewind 11
   rewind 11
   read(11,end=1005 )data
 1005  continue
   backspace 11
   write(11)data
   backspace 11
   rewind 11
   backspace 11
   rewind 11
   read(11,end=1006 )data
 1006  continue
   rewind 11
   write(11)data
   backspace 11
   read(11,end=1007 )data
 1007  continue
   read(11,end=1008 )data
 1008  continue
   backspace 11
   read(11,end=1009 )data
 1009  continue
   backspace 11
   write(11)data
   backspace 11
   read(11,end=1010 )data
 1010  continue
   read(11,end=1011 )data
 1011  continue
   backspace 11
   backspace 11
  stop
  end


-- 
   Summary: Fortran runtime error: Invalid argument
   Product: gcc
   Version: unknown
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
         Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25271] New: gfortran fails to pad lines in format statements to 72 characters.

2005-12-05 Thread dir at lanl dot gov
g77 prints correctly, but gfortran fails to correctly pad lines in format
statements to 72 characters. The lines in the file are terminated with a line
feed after the last printable character. If the lines are padded with blanks
out beyond 72 characters gfortran then prints correctly. This was fixed before
-


[dranta:~/tests/gfortran-D] dir% g77 -o write07 write07.f
[dranta:~/tests/gfortran-D] dir% write07
1
  f o l l o w i n gi sac a r di m a g el i s t i n
go ft h ei n p u td a t a 

  c o l u m nn u m
b e r
card1 2 3 4
5 6 7 8
   number 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
   -- 

0  ** e n do fi n p u tl i
s t i n g **
[dranta:~/tests/gfortran-D] dir% gfortran -o write07 write07.f
[dranta:~/tests/gfortran-D] dir% write07
1
  f o l l o w i n gi sac a r di m a g el i s t i n
go ft h ei n p u td a t a 

  c o l u m nn u m
b e r
card1 2   3 4 5
6 7 8 /   number 
12345678901234567890123456789012345678901234567890123456789012345678901234567890
   -- 

0  ** e n do fi n p u tl i
s t in g ,**
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ./configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20051205 (experimental)
[dranta:~/tests/gfortran-D] dir% cat write07.f
  program main
  write(6,2000)
  write(6,2030)

 2000 format(1h1/10x,111hf o l l o w i n gi sac a r di m
 1 a g el i s t i n go ft h ei n p u td a t a //
 t58x,26hc o l u m nn u m b e r,/20x,4hcard,16x,71h1 2
 x   3 4 5 6 7 8 /
 y19x,6hnumber, 6x,80h1234567890123456789012345678901234567890123456
 z7890123456789012345678901234567890 /,19x,6(1h-),6x,80(1h-))

 2030 format(1h0,10x,34(1h*),44h e n do fi n p u tl i s t i
 1n g ,34(1h*))
c
  end


-- 
   Summary: gfortran fails to pad lines in format statements to 72
characters.
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271



[Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.

2005-12-05 Thread dir at lanl dot gov


--- Comment #1 from dir at lanl dot gov  2005-12-05 21:16 ---
Created an attachment (id=10411)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=10411&action=view)
problem file

This is the original problem file.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271



[Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.

2005-12-06 Thread dir at lanl dot gov


--- Comment #3 from dir at lanl dot gov  2005-12-06 13:47 ---
If you look at the output from format 2030, you will see that that comma at the
end of the "44h e n d..." statement is printed, but the comma is the 45th
character after the 44h . Like wise the '/' after the 8 is printed inspite of
being the 73 character after the start of the 71h format.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271



[Bug libfortran/25271] gfortran fails to pad lines in format statements to 72 characters.

2005-12-08 Thread dir at lanl dot gov


--- Comment #5 from dir at lanl dot gov  2005-12-08 14:16 ---
Your are likely correct - it probability is not in the standard, but for the
first 15 years of FORTRAN, keypunches and card readers were the only way to
create and submit a program and they always pad to 80 characters - by
definition a line of FORTRAN was 80 character - since a card reader was the
only way to get a program to the computer. If the modern text editors, that
mostly truncate as they please had been around - the padding requirement would
have been in the standard. Actually, I am surprized that FORTRAN 77 did not add
that requirement to the standard.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25271



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-12 Thread dir at lanl dot gov


--- Comment #7 from dir at lanl dot gov  2005-12-12 16:37 ---
This patch works for the reduced test case, but the original test case still
fails for me -


[dranta:~/tests/gfortran-D] dir% gfortran -o write08 write08.f
[dranta:~/tests/gfortran-D] dir% write08
[dranta:~/tests/gfortran-D] dir% cat write08.f
  integer :: i = 1
  open(11,status="replace",form="unformatted")
  write(11) dat
  read(11,end=1008) i
1008  continue
  backspace 11
  backspace 11
  backspace 11
  end

[dranta:~/tests/gfortran-D] dir% gfortran -o testio2 testio2.f
[dranta:~/tests/gfortran-D] dir% testio2
At line 72 of file testio2.f
Fortran runtime error: Invalid argument
[dranta:~/tests/gfortran-D] dir% cat testio2.f
  program test
  dimension data(100)
   read(11,end=1000 )data
 1000  continue
   backspace 11
   backspace 11
   backspace 11
   read(11,end=1001 )data
 1001  continue
   backspace 11
   rewind 11
   backspace 11
   backspace 11
   backspace 11
   rewind 11
   write(11)data
   backspace 11
   backspace 11
   backspace 11
   backspace 11
   backspace 11
   backspace 11
   rewind 11
   backspace 11
   write(11)data
   write(11)data
   write(11)data
   backspace 11
   read(11,end=1002 )data
 1002  continue
   backspace 11
   rewind 11
   backspace 11
   read(11,end=1003 )data
 1003  continue
   write(11)data
   write(11)data
   write(11)data
   rewind 11
   read(11,end=1004 )data
 1004  continue
   rewind 11
   rewind 11
   read(11,end=1005 )data
 1005  continue
   backspace 11
   write(11)data
   backspace 11
   rewind 11
   backspace 11
   rewind 11
   read(11,end=1006 )data
 1006  continue
   rewind 11
   write(11)data
   backspace 11
   read(11,end=1007 )data
 1007  continue
   read(11,end=1008 )data
 1008  continue
   backspace 11
   read(11,end=1009 )data
 1009  continue
   backspace 11
   write(11)data
   backspace 11
   read(11,end=1010 )data
 1010  continue
   read(11,end=1011 )data
 1011  continue
   backspace 11
   backspace 11
  stop
  end
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ./configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20051212 (experimental)
[dranta:~/tests/gfortran-D] dir% 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-12 Thread dir at lanl dot gov


--- Comment #8 from dir at lanl dot gov  2005-12-12 16:50 ---
Looking into unformatted_backspace, there does not seem to be anything there to
prevent "u->last_record" from going negative - may be that is problem.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-13 Thread dir at lanl dot gov


--- Comment #9 from dir at lanl dot gov  2005-12-13 14:39 ---
I generated random I/O sequences doing 100,000 tests at each I/O operation
count staring at five here is the shortest one to fail (somewhere in the
eights) -

[dranta:~/tests/gfortran-D] dir% gfortran -o write10 write10.f
[dranta:~/tests/gfortran-D] dir% write10
At line 18 of file write10.f
Fortran runtime error: Invalid argument
[dranta:~/tests/gfortran-D] dir% cat write10.f
  integer :: i = 1
  dimension data(500)
  do 10 i=1,500
  data(i)=i
   10 continue
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   write(11)data
   rewind 11
   write(11)data
   backspace 11
   read(11,end=1000 )data
 1000  continue
   read(11,end=1001 )data
 1001  continue
   backspace 11
   backspace 11
   backspace 11
  close(11)
  end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-13 Thread dir at lanl dot gov


--- Comment #10 from dir at lanl dot gov  2005-12-13 15:21 ---
Removing the constraint of no read after write gives a slightly shorter one -

[dranta:~/tests/gfortran-D] dir%  gfortran -o write11 write11.f
[dranta:~/tests/gfortran-D] dir% write11
At line 14 of file write11.f
Fortran runtime error: Invalid argument
[dranta:~/tests/gfortran-D] dir% cat write11.f
  integer :: i = 1
  dimension data(5)
  do 10 i=1,5
  data(i)=i
   10 continue
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   read(11,end=1000 )data
 1000  continue
   backspace 11
   rewind 11
   read(11,end=1001 )data
 1001  continue
   read(11,end=1002 )data
 1002  continue
  close(11)
  end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-16 Thread dir at lanl dot gov


--- Comment #11 from dir at lanl dot gov  2005-12-16 20:35 ---
When the array of size 2045 or larger the error goes away -

[dranta:~/tests/gfortran-D] dir% gfortran -o write11 write11.f
[dranta:~/tests/gfortran-D] dir% write11
At line 14 of file write11.f
Fortran runtime error: Invalid argument
[dranta:~/tests/gfortran-D] dir% cat write11.f
  integer :: i = 1
  dimension data(2044)
  do 10 i=1,5
  data(i)=i
   10 continue
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   read(11,end=1000 )data
 1000  continue
c  backspace 11
   rewind 11
   read(11,end=1001 )data
 1001  continue
   read(11,end=1002 )data
 1002  continue
  close(11)
  end

[dranta:~/tests/gfortran-D] dir% gfortran -o write11 write11.f
[dranta:~/tests/gfortran-D] dir% write11
[dranta:~/tests/gfortran-D] dir% cat write11.f
  integer :: i = 1
  dimension data(2045)
  do 10 i=1,5
  data(i)=i
   10 continue
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   read(11,end=1000 )data
 1000  continue
c  backspace 11
   rewind 11
   read(11,end=1001 )data
 1001  continue
   read(11,end=1002 )data
 1002  continue
  close(11)
  end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-21 Thread dir at lanl dot gov


--- Comment #14 from dir at lanl dot gov  2005-12-21 19:36 ---
After tracing the errors for a while, it became clean that "active" pointer
into the read/write buffer was not being correctly updated. Adding one line (
s->active=0; ) to the bottom of routine "fd_truncate" in file "unix.c" fixes
these errors. All the examples here run OK with this patch and I built 16 of my
programs and ran their many test problems with no errors. I tried to run the
fortran testsuite with "make check-gfortran", but check-gfortran is not in the
makefile. It would be nice if just fortran testsuite could be run.



*** unix.c  Wed Dec 21 08:11:12 2005
--- unixoriginal.c  Wed Dec 21 08:10:27 2005
***
*** 601,608 
  }

s->physical_offset = s->file_length = s->logical_offset;
-   
-   s->active=0;

return SUCCESS;
  }
--- 601,606 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-21 Thread dir at lanl dot gov


--- Comment #16 from dir at lanl dot gov  2005-12-21 21:43 ---
I down loaded gfortran and built it on the Macintosh with -

svn -q checkout svn://gcc.gnu.org/svn/gcc/trunk gcc
cd gcc
configure --prefix=/Users/dir/gfortran --enable-languages=c,f95
make -j 4
make install

When, I try the "check-gfortran" in the directory 'gcc' where I did the
configure,make -j 4,make install, I get -

[dranta:~/gfortran/gcc] dir% make check-gfortran
make: *** No rule to make target `check-gfortran'.  Stop.

When I move to the directory 'gcc' below that, I get -

[dranta:~/gfortran/gcc] dir% cd gcc
[dranta:~/gfortran/gcc/gcc] dir% make check-gfortran
make: *** No rule to make target `check-gfortran'.  Stop.
[dranta:~/gfortran/gcc/gcc] dir% 

Is there another directory called gcc or does it need to be build some other
way ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread dir at lanl dot gov


--- Comment #20 from dir at lanl dot gov  2005-12-22 14:00 ---
Thanks FX - You gave me the first good explaination of how it should be done.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread dir at lanl dot gov


--- Comment #21 from dir at lanl dot gov  2005-12-22 14:18 ---
The second example in comment 3 should fail as it does - since it does try read
beyond the end of file. As far as I can tell, the FX patch does not fix any of
the test cases on the Macintosh and I think that it actually is incorrect. It
should actually read -

   new = file_position (u->s) - m - 2*sizeof (gfc_offset);

as "2*sizeof (gfc_offset)" is the size of the green words before and after the
data and m is the size of the data. (m+2*sizeof (gfc_offset)) is the total size
of the binary record that is being skipped backwards over.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread dir at lanl dot gov


--- Comment #23 from dir at lanl dot gov  2005-12-22 16:01 ---
What is happening here is actually quite simple. The program reads the green
word for the previous record from the file from location "file_position (u->s)
- length)", that word gives the length of the previous record in bytes. It then
pulls that number out of the buffer and puts it into correct integer form for
the current machine, that is the number 'm'. The length of a binary record is
always the length of the two green words plus the length of the data or (m +
2*sizeof (gfc_offset)). The position before the currect record is then
file_position (u->s) - m - 2*sizeof (gfc_offset).
I did not change the current coding and it works for all of my tests. Any
time that p is not NULL, length returns the number of bytes read, which should
be sizeof (gfc_offset). If length is not equal to sizeof (gfc_offset), there is
an error in the file data - so may be that should be put in as an error test.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread dir at lanl dot gov


--- Comment #24 from dir at lanl dot gov  2005-12-22 16:32 ---
Also, I just noticed that, if length != sizeof (gfc_offset) then 'm' has not
been correctly read - so the routine should quit. Using a bad number to
calculate 'new' will not likely useful.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread dir at lanl dot gov


--- Comment #26 from dir at lanl dot gov  2005-12-22 19:23 ---
I ran the "check-gfortran" tests before and after putting in the two changes
that I suggested on the Macintosh and the results were identical and my real
programs now run Ok with the changes, but someone is currectly making changes
to the fortran io routines and some of the tests given here are failing in new
ways -

Test Run By dir on Thu Dec 22 09:47:44 2005
Native configuration is powerpc-apple-darwin8.3.0

=== gfortran tests ===

Schedule of variations:
unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /Users/dir/gfortran/gcc/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp ...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
...

=== gfortran Summary ===

# of expected passes10985
# of unexpected failures8
# of expected failures  7
# of unsupported tests  42


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-22 Thread dir at lanl dot gov


--- Comment #27 from dir at lanl dot gov  2005-12-22 21:14 ---
In the second example in comment #3, the first read reads the end of file and
the end=1008 works correctly. On the second read, the end of file has been
passed so that the end=1011 does not and should not catch it - it is an error
condition and a correct error message is printed.  If err=1011 was used, then
the error message should not be printed and the programs should jump to 1011
with out comment.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug fortran/25538] New: internal compiler error: in build_function_decl, at fortran/trans-decl.c:1130

2005-12-22 Thread dir at lanl dot gov
I thought that I saw this before, but I could not find it with a search. Here
is an ICE on a bad program -

[dranta:~/tests/gfortran-D] dir% gfortran -c rspace.F
rspace.F:1: internal compiler error: in build_function_decl, at
fortran/trans-decl.c:1130
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
[dranta:~/tests/gfortran-D] dir% cat rspace.F
  subroutine link2(namef)
c
  entry link2(nameg)
  return
c
  end


-- 
   Summary: internal compiler error: in build_function_decl, at
fortran/trans-decl.c:1130
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25538



[Bug fortran/25539] New: internal compiler error: in build_function_decl, at fortran/trans-decl.c:1130

2005-12-22 Thread dir at lanl dot gov
I thought that I saw this before, but I could not find it with a search. Here
is an ICE on a bad program -

[dranta:~/tests/gfortran-D] dir% gfortran -c rspace.F
rspace.F:1: internal compiler error: in build_function_decl, at
fortran/trans-decl.c:1130
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
[dranta:~/tests/gfortran-D] dir% cat rspace.F
  subroutine link2(namef)
c
  entry link2(nameg)
  return
c
  end


-- 
   Summary: internal compiler error: in build_function_decl, at
fortran/trans-decl.c:1130
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25539



[Bug fortran/25539] internal compiler error: in build_function_decl, at fortran/trans-decl.c:1130

2005-12-22 Thread dir at lanl dot gov


--- Comment #1 from dir at lanl dot gov  2005-12-22 21:59 ---
I don't know why this showed up twice


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25539



[Bug libfortran/25139] [4.1/4.2 regression] "Invalid argument" error on I/O

2005-12-23 Thread dir at lanl dot gov


--- Comment #31 from dir at lanl dot gov  2005-12-23 15:14 ---
  Hi Jerry,

  Would you go ahead and commit this ? A test case something like that in
Comment #9 shows the problem before and the fix after or may be you have a
better one from NIST. The change suggest in comment #14 fixes the problem that
started all of this for me. There are other bugs, that I have hit looking into
this, but I think that they should be in seperate bug reports.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25139



[Bug libfortran/25550] New: file data corrupted after reading end of file

2005-12-23 Thread dir at lanl dot gov
After the end of file is read, the file data is corrupted -

[dranta:~/tests/gfortran-D] dir% gfortran -o write17 write17.f
[dranta:~/tests/gfortran-D] dir% write17
   538976288
Abort
[dranta:~/tests/gfortran-D] dir% cat write17.f
  integer data
  data=-1
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   read(11,end=1000 )data
 1000  continue
   rewind 11
   read(11,end=1001 )data
 1001  continue
   if(data.ne.-1)then
  write(6,*)data
  call abort
   endif
   close(11)
   end


-- 
   Summary: file data corrupted after reading end of file
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25550



[Bug libfortran/25577] New: gfortran routine mvbits returns wrong answer.

2005-12-27 Thread dir at lanl dot gov
gfortran routine mvbits returns wrong answer (Absoft shows the correct answer)
-

[dranta:~/tests/gfortran-D] dir% gfortran -o sage02 sage02.f90
[dranta:~/tests/gfortran-D] dir% sage02
   0
  1F   0
[dranta:~/tests/gfortran-D] dir% f90 -o sage02 sage02.f90
[dranta:~/tests/gfortran-D] dir% sage02
   0
001f   0
[dranta:~/tests/gfortran-D] dir% cat sage02.f90
implicit none
integer, parameter :: INT8  = SELECTED_INT_KIND(16)
integer(INT8) :: ieee64_int, cray64_int
data cray64_int / 0_INT8/
data ieee64_int /-1_INT8/
write(6,'(2z20)')ieee64_int,cray64_int
call mvbits(cray64_int, 0,43,ieee64_int,5) ! copy and shift the
mantissa
write(6,'(2z20)')ieee64_int,cray64_int
   stop
end


-- 
   Summary: gfortran routine mvbits returns wrong answer.
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25577



[Bug fortran/25578] New: gfortran version 4.2.0 20051227 - 144 new testsuite failures since 2005121

2005-12-27 Thread dir at lanl dot gov
-torture/execute/power.f90 execution,  -O1 
FAIL: gfortran.fortran-torture/execute/power.f90 execution,  -O2 
FAIL: gfortran.fortran-torture/execute/power.f90 execution,  -O3
-fomit-frame-pointer 
FAIL: gfortran.fortran-torture/execute/power.f90 execution,  -O3
-fomit-frame-pointer -funroll-loops 
FAIL: gfortran.fortran-torture/execute/power.f90 execution,  -O3
-fomit-frame-pointer -funroll-all-loops -finline-functions 
FAIL: gfortran.fortran-torture/execute/power.f90 execution,  -O3 -g 
FAIL: gfortran.fortran-torture/execute/power.f90 execution,  -Os 

=== gfortran Summary ===

# of expected passes10856
# of unexpected failures152
# of expected failures  7
# of unsupported tests  42
/Users/dir/gfortran/ibin/stage3-gcc/testsuite/../gfortran  version 4.2.0
20051227 (experimental)


-- 
   Summary: gfortran  version 4.2.0 20051227 - 144 new testsuite
failures since 2005121
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25578



[Bug rtl-optimization/25578] [4.2 Regression] gfortran version 4.2.0 20051227 - 144 new testsuite failures since 2005121

2005-12-27 Thread dir at lanl dot gov


--- Comment #3 from dir at lanl dot gov  2005-12-27 21:46 ---
This was after a complete new download and rebuild.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25578



[Bug libfortran/25577] gfortran routine mvbits returns wrong answer.

2005-12-29 Thread dir at lanl dot gov


--- Comment #1 from dir at lanl dot gov  2005-12-29 15:34 ---
Here is another test example that more clearly shows the problem (The f90
output is correct) -

[dranta:~/tests/gfortran-D] dir% f90 -o sage03 sage03.f90
[dranta:~/tests/gfortran-D] dir% sage03
1
2fffdfffd
3fff9fff9
4fff1fff1
5ffe1ffe1
6ffc1ffc1
7ff81ff81
8ff01ff01
9fe01fe01
   10fc01fc01
   11f801f801
   12f001f001
   13e001e001
   14c001c001
   1580018001
   1600010001
   17fffe0001fffe0001
   18fffc0001fffc0001
   19fff80001fff80001
   20fff1fff1
   21ffe1ffe1
   22ffc1ffc1
   23ff81ff81
   24ff01ff01
   25fe01fe01
   26fc01fc01
   27f801f801
   28f001f001
   29e001e001
   30c001c001
   3180018001
   3200010001
   33fffe0001fffe0001
   34fffc0001fffc0001
   35fff80001fff80001
   36fff1fff1
   37ffe1ffe1
   38ffc1ffc1
   39ff81ff81
   40ff01ff01
   41fe01fe01
   42fc01fc01
   43f801f801
   44f001f001
   45e001e001
   46c001c001
   4780018001
   4800010001
   49fffe0001fffe0001
   50fffc0001fffc0001
   51fff80001fff80001
   52fff1fff1
   53ffe1ffe1
   54ffc1ffc1
   55ff81ff81
   56ff01ff01
   57fe01fe01
   58fc01fc01
   59f801f801
   60f001f001
   61e001e001
   62c001c001
   6380018001
   64   1   1
[dranta:~/tests/gfortran-D] dir% gfortran -o sage03 sage03.f90
[dranta:~/tests/gfortran-D] dir% sage03
1
2FFFDFFFD
3FFF9FFF9
4FFF1FFF1
5FFE1FFE1
6FFC1FFC1
7FF81FF81
8FF01FF01
9FE01FE01
   10FC01FC01
   11F801F801
   12F001F001
   13E001E001
   14C001C001
   1580018001
   1600010001
   17FFFE0001FFFE0001
   18FFFC0001FFFC0001
   19FFF80001FFF80001
   20FFF1FFF1
   21FFE1FFE1
   22FFC1FFC1
   23FF81FF81
   24FF01FF01
   25FE01FE01
   26FC01FC01
   27F801F801
   28F001F001
   29E001E001
   30C001C001
   3180018001
   32   10001
Abort
[dranta:~/tests/gfortran-D] dir% cat sage03.f90
implicit none
integer*8 cray64_int,ieee64_int,ia,itwo
integer ibits,n
itwo=2
ibits=bit_size(cray64_int)
do n=1

[Bug libfortran/25598] New: gfortran - Fortran runtime error: Invalid argument

2005-12-29 Thread dir at lanl dot gov
gfortran is giving an error on this program, while g77 is happy with it -


[dranta:~/tests/gfortran-D] dir% g77 -o write18 write18.f
[dranta:~/tests/gfortran-D] dir% write18
[dranta:~/tests/gfortran-D] dir% gfortran -o write18 write18.f
[dranta:~/tests/gfortran-D] dir% write18
At line 9 of file write18.f
Fortran runtime error: Invalid argument
[dranta:~/tests/gfortran-D] dir% cat write18.f
  integer data
  data=-1
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   read(11,end=1000 )data
 1000  continue
   backspace 11
   backspace 11
   read(11,end=1001 )data
 1001  continue
   if(data.ne.-1)then
  write(6,*)data
  call abort
   endif
   close(11)
   end

[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20051229 (experimental)
[dranta:~/tests/gfortran-D] dir%


-- 
   Summary: gfortran - Fortran runtime error: Invalid argument
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.3.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25598



[Bug libfortran/25577] gfortran routine mvbits returns wrong answer.

2006-01-04 Thread dir at lanl dot gov


--- Comment #2 from dir at lanl dot gov  2006-01-04 19:51 ---
It also fails on 4.1-

[dranta:~/tests/gfortran-D] dir% gfortran -o sage03 sage03.f90
[dranta:~/tests/gfortran-D] dir% sage03
1
2FFFDFFFD
3FFF9FFF9
4FFF1FFF1
5FFE1FFE1
6FFC1FFC1
7FF81FF81
8FF01FF01
9FE01FE01
   10FC01FC01
   11F801F801
   12F001F001
   13E001E001
   14C001C001
   1580018001
   1600010001
   17FFFE0001FFFE0001
   18FFFC0001FFFC0001
   19FFF80001FFF80001
   20FFF1FFF1
   21FFE1FFE1
   22FFC1FFC1
   23FF81FF81
   24FF01FF01
   25FE01FE01
   26FC01FC01
   27F801F801
   28F001F001
   29E001E001
   30C001C001
   3180018001
   32   10001
Abort
[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.1.0 20060104 (prerelease)
[dranta:~/tests/gfortran-D] dir% cat sage03.f90
implicit none
integer*8 cray64_int,ieee64_int,ia,itwo
integer ibits,n
itwo=2
ibits=bit_size(cray64_int)
do n=1,ibits
  ieee64_int=-1
  cray64_int=1
  call mvbits(cray64_int, 0,n,ieee64_int,0)
  ia=-1
  ia=ia-itwo**n+2
  write(6,'(i5,2z20)')n,ieee64_int,ia
  if(ia.ne.ieee64_int)call abort
enddo
stop
end


-- 

dir at lanl dot gov changed:

   What|Removed |Added

  Known to fail||4.1.0 4.2.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25577




[Bug libfortran/25697] New: libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-06 Thread dir at lanl dot gov
On the Macintosh this program gives a "Segmentation fault" on Linux it gives
"Fortran runtime error: Bad address"

dranta:~/tests/gfortran-D] dir% gfortran -o write19 write19.f
[dranta:~/tests/gfortran-D] dir% write19
Segmentation fault
[dranta:~/tests/gfortran-D] dir% cat write19.f
  integer data(500)
  do i = 1,500
data(i)=-1
  enddo
  open(unit=11,status='scratch',form='unformatted')
   read(11,end=1000 )data
 1000  continue
   backspace 11
   write(11)data
   read(11,end=1001 )data
 1001  continue
   backspace 11
   backspace 11
   write(11)data
   rewind 11
   backspace 11
   read(11,end=1002 )data
 1002  continue
   read(11,end=1003 )data
 1003  continue
   close(11)
   end

dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.3.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060106 (experimental)
[dranta:~/tests/gfortran-D] dir%


-- 
   Summary: libfortran - Segmentation fault/ Bad Address on
unformatted read
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libfortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697




[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-06 Thread dir at lanl dot gov


--- Comment #1 from dir at lanl dot gov  2006-01-06 20:11 ---
Here is a shorter one that also crashes on the Macintosh -

[dranta:~/tests/gfortran-D] dir% gfortran -o write20 write20.f
[dranta:~/tests/gfortran-D] dir% write20
Segmentation fault
[dranta:~/tests/gfortran-D] dir% cat write20.f
  integer data(500)
  do i = 1,500
data(i)=-1
  enddo
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   read(11,end=1000 )data
 1000  continue
   backspace 11
   backspace 11
   write(11)data
   rewind 11
   read(11,end=1001 )data
 1001  continue
   read(11,end=1002 )data
 1002  continue
   close(11)
   end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697




[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-08 Thread dir at lanl dot gov


--- Comment #4 from dir at lanl dot gov  2006-01-09 01:52 ---
Having a read immediately follow a write - seems to cause the errors.  I have
run several million I/O tests where the only legal thing not permitted is a
read immediately after a write -  without getting a single error.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697




[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-09 Thread dir at lanl dot gov


--- Comment #6 from dir at lanl dot gov  2006-01-09 18:18 ---
  Hurray - Let there be an end to I/O problems.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697




[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-11 Thread dir at lanl dot gov


--- Comment #8 from dir at lanl dot gov  2006-01-11 15:34 ---
That fixed all the posted examples and it passed the 1048576 tests of all
combinations of read,write,backspace, and rewind taken 10 at a time writing a
single word, but when I increased the write size to 500 words it failed. The
strange thing with this example is that if one of the five writes is removed it
no longer fails (buffer flush problem ?) -

[dranta:~/tests/gfortran-D] dir% gfortran -o write21 write21.f
[dranta:~/tests/gfortran-D] dir% write21
Segmentation fault
[dranta:~/tests/gfortran-D] dir% cat write21.f
  integer data(500)
  do i = 1,500
data(i)=-1
  enddo
  open(unit=11,status='scratch',form='unformatted')
   write(11)data
   write(11)data
   write(11)data
   write(11)data
   write(11)data
   read(11,end=1000 )data
   call abort()
 1000  continue
   backspace 11
   backspace 11
   read(11,end=1001 )data
 1001  continue
   read(11,end=1002 )data
   call abort()
 1002  continue
   close(11)
   end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697




[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-11 Thread dir at lanl dot gov


--- Comment #9 from dir at lanl dot gov  2006-01-11 16:02 ---
With a larger amount of data it only takes one write -


[dranta:~/tests/gfortran-D] dir% gfortran -o write22 write22.f
[dranta:~/tests/gfortran-D] dir% write22
Bus error
[dranta:~/tests/gfortran-D] dir% cat write22.f
  integer data(1)
  do i = 1,1
data(i)=-1
  enddo
  open(unit=11,status='scratch',form='unformatted')
   data(1)=1
   data(1)=-1
   write(11)data
   read(11,end=1000 )data
   call abort()
 1000  continue
   backspace 11
   backspace 11
   read(11,end=1001 )data
if(data(1).ne.   1.or.data(1).ne.  -1)then
call abort()
endif
 1001  continue
   read(11,end=1002 )data
   call abort()
 1002  continue
   close(11)
   end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697




[Bug libfortran/25697] libfortran - Segmentation fault/ Bad Address on unformatted read

2006-01-11 Thread dir at lanl dot gov


--- Comment #10 from dir at lanl dot gov  2006-01-11 16:50 ---
My thought on a possible fix is that the I/O buffers should be dumped before
the read whenever a read immediately follows a write, but I have no idea how
you would detect the situation. 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25697




[Bug fortran/25753] New: gfortran - fails to build on Mac OSX -10.4.3

2006-01-11 Thread dir at lanl dot gov
A fresh down load of everything this morning gets a error trying to build -

gcc -c   -g -no-cpp-precomp -DHAVE_DESIGNATED_INITIALIZERS=0 -DIN_GCC   -W
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wold-style-definition
-Wmissing-format-attribute -fno-common   -DHAVE_CONFIG_H -I. -I.
-I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I./../intl
-I../../gcc/gcc/../libcpp/include  -I../../gcc/gcc/../libdecnumber
-I../libdecnumber../../gcc/gcc/debug.c -o debug.o
gcc -c   -g -no-cpp-precomp -DHAVE_DESIGNATED_INITIALIZERS=0 -DIN_GCC   -W
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wold-style-definition
-Wmissing-format-attribute -fno-common   -DHAVE_CONFIG_H -I. -I.
-I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I./../intl
-I../../gcc/gcc/../libcpp/include  -I../../gcc/gcc/../libdecnumber
-I../libdecnumber../../gcc/gcc/df-core.c -o df-core.o
gcc -c   -g -no-cpp-precomp -DHAVE_DESIGNATED_INITIALIZERS=0 -DIN_GCC   -W
-Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic
-Wno-long-long -Wno-variadic-macros -Wold-style-definition
-Wmissing-format-attribute -fno-common   -DHAVE_CONFIG_H -I. -I.
-I../../gcc/gcc -I../../gcc/gcc/. -I../../gcc/gcc/../include -I./../intl
-I../../gcc/gcc/../libcpp/include  -I../../gcc/gcc/../libdecnumber
-I../libdecnumber../../gcc/gcc/df-problems.c -o df-problems.o
make[3]: *** No rule to make target `odf.c', needed by `odf.o'.  Stop.
make[2]: *** [all-stage1-gcc] Error 2
make[1]: *** [stage1-bubble] Error 2
make: *** [all] Error 2


-- 
   Summary: gfortran - fails to build on Mac OSX -10.4.3
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25753



[Bug fortran/25785] New: gfortran - incorrectly issues an error on tests for optional arguments

2006-01-13 Thread dir at lanl dot gov
gfortran has started erroring on some "present" statements (Absoft and others
have no problem with this program and older version of gfortran were also happy
with it) -


[dranta:~/tests/gfortran-D] dir% f90 -c present01.f90
[dranta:~/tests/gfortran-D] dir% gfortran -c present01.f90
 In file present01.f90:3

if (present(data_c1)) then
   1
Error: The upper bound in the last dimension must appear in the reference to
the assumed size array 'data_c1' at (1).
[dranta:~/tests/gfortran-D] dir% cat present01.f90
  subroutine my_sio_file_write_common(data_c1)
character,   intent(in), optional :: data_c1(*)
if (present(data_c1)) then
endif
  end subroutine my_sio_file_write_common


[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.4.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060113 (experimental)


-- 
   Summary: gfortran - incorrectly issues an error on tests for
optional arguments
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dir at lanl dot gov


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25785



[Bug fortran/25785] gfortran - incorrectly issues an error on tests for optional arguments with assumed length

2006-01-13 Thread dir at lanl dot gov


--- Comment #2 from dir at lanl dot gov  2006-01-13 18:06 ---
It also fails with a "double precision" argument -

[dranta:~/tests/gfortran-D] dir% gfortran -c present02.f90
 In file present02.f90:3

if (present(data_c1)) then
   1
Error: The upper bound in the last dimension must appear in the reference to
the assumed size array 'data_c1' at (1).
[dranta:~/tests/gfortran-D] dir% cat present02.f90
  subroutine my_sio_file_write_common(data_c1)
double precision,   intent(in), optional :: data_c1(*)
if (present(data_c1)) then
endif
  end subroutine my_sio_file_write_common


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25785



[Bug libfortran/25577] gfortran routine mvbits returns wrong answer.

2006-01-17 Thread dir at lanl dot gov


--- Comment #4 from dir at lanl dot gov  2006-01-17 15:30 ---
Opps, I think that the change suggested in Comment #1 actually does fix the
problem on the LINUX version. 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25577



[Bug fortran/25785] gfortran - incorrectly issues an error on tests for optional arguments with assumed length

2006-01-17 Thread dir at lanl dot gov


--- Comment #5 from dir at lanl dot gov  2006-01-17 20:07 ---
This bug has now migrated into the 4.1 tree. Sometime after the 20060104
version Would it not be easier to elminate the offending updates rather than
debug them ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25785



[Bug fortran/25785] [4.1/4.2 Regression] gfortran - incorrectly issues an error on tests for optional arguments with assumed length

2006-01-18 Thread dir at lanl dot gov


--- Comment #9 from dir at lanl dot gov  2006-01-18 14:20 ---
Paul,

I am sorry that I upset you. It was completely unintentional.

Dale.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25785



[Bug fortran/25850] New: gfortran - 8 testsuite failures on darwin

2006-01-18 Thread dir at lanl dot gov
I cannot find were anyone else has submitted this as a bug -


Test Run By dir on Wed Jan 18 13:21:27 2006
Native configuration is powerpc-apple-darwin8.4.0

=== gfortran tests ===

Schedule of variations:
unix

Running target unix
Using /usr/local/share/dejagnu/baseboards/unix.exp as board description file
for target.
Using /usr/local/share/dejagnu/config/unix.exp as generic interface file for
target.
Using /Users/dir/gfortran/gcc/gcc/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
FAIL: gfortran.dg/large_real_kind_2.F90 execution test
Running /Users/dir/gfortran/gcc/gcc/testsuite/gfortran.dg/vect/vect.exp ...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp
...
Running
/Users/dir/gfortran/gcc/gcc/testsuite/gfortran.fortran-torture/execute/execute.exp
...

=== gfortran Summary ===

# of expected passes11299
# of unexpected failures8
# of expected failures  7
# of unsupported tests  42
/Users/dir/gfortran/ibin/gcc/testsuite/gfortran/../../gfortran  version 4.2.0
20060118 (experimental)

make: [check-gfortran] Error 1 (ignored)
[dranta:~/gfortran/ibin/gcc] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.4.0
Configured with: ../gcc/configure --prefix=/Users/dir/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060118 (experimental)


-- 
   Summary: gfortran - 8 testsuite failures on darwin
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.4.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25850



[Bug fortran/29142] New: gfortran - incorrectly flags error on allocatable variable in TYPE declaration

2006-09-19 Thread dir at lanl dot gov
The other compilers are happy with this TYPE declaration - so I guess that it
is ok -

[dranta:~/tests/gfortran-D] dir% g95 -c struct02.f90
[dranta:~/tests/gfortran-D] dir% f90 -c struct02.f90
[dranta:~/tests/gfortran-D] dir% xlf95 -qsuffix=f=f90 -c struct02.f90
** plot_hdf   === End of Compilation 1 ===
1501-510  Compilation successful for file struct02.f90.
[dranta:~/tests/gfortran-D] dir% gfortran -c struct02.f90
 In file struct02.f90:5

   real,dimension(:),   allocatable ::  data
  1
Error: Attribute at (1) is not allowed in a TYPE definition
 In file struct02.f90:6

 end type SDS2Dout
 1
Error: Derived type definition at (1) has no components
[dranta:~/tests/gfortran-D] dir% cat struct02.f90
  module plot_hdf
  implicit none
  save
type, public ::   SDS2Dout
   real,dimension(:),   allocatable ::  data
end type SDS2Dout
  end module plot_hdf

[dranta:~/tests/gfortran-D] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.7.0
Configured with: ../gcc/configure --prefix=/usr/local/gfortran
--enable-languages=c,f95
Thread model: posix
gcc version 4.2.0 20060919 (experimental)


-- 
   Summary: gfortran - incorrectly flags error on allocatable
variable in TYPE declaration
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: Darwin 8.7.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29142



[Bug java/29460] New: configure: error: libXtst not found, required by java.awt.Robot

2006-10-13 Thread dir at lanl dot gov
I am trying to build java with gtk support. I configured with -

 ../gcc/configure --prefix=/usr/local/java --enable-languages=c,c++,java
--enable-java-awt=gtk --enable-gtk-cairo --x-includes=/usr/x11R6/include
--x-libraries=/usr/x11R6/lib

And I get this output -

checking for pkg-config... /usr/local/bin/pkg-config
checking for gtk+-2.0 >= 2.4... yes
checking GTK_CFLAGS... -I/usr/local/include/gtk-2.0
-I/usr/local/lib/gtk-2.0/include -I/usr/local/include/atk-1.0
-I/usr/local/include/cairo -I/usr/local/include/pango-1.0
-I/usr/local/include/glib-2.0 -I/usr/local/lib/glib-2.0/include  
checking GTK_LIBS... -L/usr/local/lib -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
-lgdk_pixbuf-2.0 -lm -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0
-lgmodule-2.0 -lglib-2.0 -lintl -liconv  
checking for glib-2.0 >= 2.4 gthread-2.0 >= 2.4... yes
checking GLIB_CFLAGS... -D_REENTRANT -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include  
checking GLIB_LIBS... -L/usr/local/lib -lgthread-2.0 -lglib-2.0 -lintl -liconv  
checking for libart-2.0 >= 2.1... yes
checking LIBART_CFLAGS... -I/usr/local/include/libart-2.0  
checking LIBART_LIBS... -L/usr/local/lib -lart_lgpl_2  
checking for XTestQueryExtension in -lXtst... no
configure: error: libXtst not found, required by java.awt.Robot
make[1]: *** [configure-target-libjava] Error 1
make: *** [all] Error 2
[dranta:~/gfortran/ibin] dir% ls /usr/X11R6/lib/libXtst.*
/usr/X11R6/lib/libXtst.6.1.dylib/usr/X11R6/lib/libXtst.a
/usr/X11R6/lib/libXtst.6.dylib  /usr/X11R6/lib/libXtst.dylib


Since libXtst is where it is supposed to be, it not clear what the problem is.


-- 
   Summary: configure: error: libXtst not found, required by
java.awt.Robot
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: java
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.7.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29460



[Bug libgcj/29460] configure: error: libXtst not found, required by java.awt.Robot

2006-10-16 Thread dir at lanl dot gov


--- Comment #3 from dir at lanl dot gov  2006-10-16 12:39 ---
Created an attachment (id=12442)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12442&action=view)
config.log file from gfortran/ibin/powerpc-apple-darwin8.7.0/libjava


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29460



[Bug libgcj/29460] configure: error: libXtst not found, required by java.awt.Robot

2006-10-16 Thread dir at lanl dot gov


--- Comment #4 from dir at lanl dot gov  2006-10-16 12:42 ---
Created an attachment (id=12443)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12443&action=view)
config.log file from /Users/dir/gfortran/ibin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29460



[Bug libgcj/25026] -libXtst not detected [--enable-java-awt=gtk]

2006-10-16 Thread dir at lanl dot gov


--- Comment #5 from dir at lanl dot gov  2006-10-16 15:53 ---
powerpc-apple-darwin8.7.0 does not come with 64 bit libraries for x-windows -
is there some way to turn of the 64 bit branch of the build ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25026



[Bug libgcj/25026] -libXtst not detected [--enable-java-awt=gtk]

2006-10-16 Thread dir at lanl dot gov


--- Comment #7 from dir at lanl dot gov  2006-10-16 18:53 ---
I tried installing the patch (the two patch files in comment #6 were identical)
into 4.2 , but it failed -

[dranta:~/gfortran/gcc/libjava] dir% patch -p2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25026



[Bug libgcj/25026] -libXtst not detected [--enable-java-awt=gtk]

2006-10-16 Thread dir at lanl dot gov


--- Comment #10 from dir at lanl dot gov  2006-10-16 19:57 ---
What does --disable-multilib do ?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25026



[Bug libgcj/25026] -libXtst not detected [--enable-java-awt=gtk]

2006-10-16 Thread dir at lanl dot gov


--- Comment #16 from dir at lanl dot gov  2006-10-16 20:18 ---
The patch from comment #8 partly fails on a 4.2 tree created this afternoon -

[dranta:~/gfortran/gcc/libjava] dir% patch -p2 < gcc42-java-nomulti.patch
patching file Makefile.in
Hunk #1 FAILED at 9006.
1 out of 1 hunk FAILED -- saving rejects to file Makefile.in.rej
patching file configure
Hunk #1 succeeded at 4892 (offset 309 lines).
patching file configure.ac
Hunk #1 succeeded at 209 (offset 36 lines).
[dranta:~/gfortran/gcc/libjava] dir% 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25026



[Bug libgcj/29491] New: java.lang.InternalError: Pango: pango_color_parse: assertion `spec != NULL' failed

2006-10-17 Thread dir at lanl dot gov
I finally got java to build with gtk support, but every program that I try to
run fails like this simple example from a java book (pango is finding a null
pointer) -

[dranta:java/CHAPCODE/Ch12] dir% gcj -bind_at_load --main=Application -o
Application Application.java
[dranta:java/CHAPCODE/Ch12] dir% Application

(.:18349): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL'
failed
java.lang.InternalError: Pango: pango_color_parse: assertion `spec != NULL'
failed
   <>
-:2: Invalid color constant '(null)'
-:2: error: invalid string constant "#eee1b3", expected valid string constant

Gtk-ERROR **: file gtkcontainer.c: line 2000 (_gtk_container_focus_sort):
should not be reached
aborting...
java.lang.InternalError: Gtk: file gtkcontainer.c: line 2000
(_gtk_container_focus_sort): should not be reached
   <>
Abort
[dranta:java/CHAPCODE/Ch12] dir% cat Application.java
import java.awt.Frame;
import java.awt.Color;
import java.awt.event.WindowEvent;
import java.awt.event.WindowAdapter;
public class Application {
  public static void main (String args[]) {
Frame myWindow = new Frame ("Window !");
myWindow.setBackground(Color.blue);
myWindow.setSize(300,300);
myWindow.setVisible(true);
myWindow.addWindowListener (new WindowAdapter() {
  public void windowClosing (WindowEvent e) {
System.exit(0);
  }
});
  }
}
[dranta:java/CHAPCODE/Ch12] dir% gcj --v
Using built-in specs.
Reading specs from
/usr/local/java/lib/gcc/powerpc-apple-darwin8.7.0/4.2.0/../../../libgcj.spec
rename spec startfile to startfileorig
rename spec lib to liborig
Target: powerpc-apple-darwin8.7.0
Configured with: ../gcc/configure --prefix=/usr/local/java
--enable-languages=c,c++,java --enable-java-awt=gtk --enable-gtk-cairo
--disable-multilib --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
Thread model: posix
gcc version 4.2.0 20061016 (experimental)


-- 
   Summary: java.lang.InternalError: Pango: pango_color_parse:
assertion `spec != NULL' failed
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libgcj
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.6.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29491



[Bug libgcj/29492] New: java.lang.InternalError: Pango: pango_color_parse: assertion `spec != NULL' failed

2006-10-17 Thread dir at lanl dot gov
I finally got java to build with gtk support, but every program that I try to
run fails like this simple example from a java book (pango is finding a null
pointer) -

[dranta:java/CHAPCODE/Ch12] dir% gcj -bind_at_load --main=Application -o
Application Application.java
[dranta:java/CHAPCODE/Ch12] dir% Application

(.:18349): Pango-CRITICAL **: pango_color_parse: assertion `spec != NULL'
failed
java.lang.InternalError: Pango: pango_color_parse: assertion `spec != NULL'
failed
   <>
-:2: Invalid color constant '(null)'
-:2: error: invalid string constant "#eee1b3", expected valid string constant

Gtk-ERROR **: file gtkcontainer.c: line 2000 (_gtk_container_focus_sort):
should not be reached
aborting...
java.lang.InternalError: Gtk: file gtkcontainer.c: line 2000
(_gtk_container_focus_sort): should not be reached
   <>
Abort
[dranta:java/CHAPCODE/Ch12] dir% cat Application.java
import java.awt.Frame;
import java.awt.Color;
import java.awt.event.WindowEvent;
import java.awt.event.WindowAdapter;
public class Application {
  public static void main (String args[]) {
Frame myWindow = new Frame ("Window !");
myWindow.setBackground(Color.blue);
myWindow.setSize(300,300);
myWindow.setVisible(true);
myWindow.addWindowListener (new WindowAdapter() {
  public void windowClosing (WindowEvent e) {
System.exit(0);
  }
});
  }
}
[dranta:java/CHAPCODE/Ch12] dir% gcj --v
Using built-in specs.
Reading specs from
/usr/local/java/lib/gcc/powerpc-apple-darwin8.7.0/4.2.0/../../../libgcj.spec
rename spec startfile to startfileorig
rename spec lib to liborig
Target: powerpc-apple-darwin8.7.0
Configured with: ../gcc/configure --prefix=/usr/local/java
--enable-languages=c,c++,java --enable-java-awt=gtk --enable-gtk-cairo
--disable-multilib --x-includes=/usr/X11R6/include --x-libraries=/usr/X11R6/lib
Thread model: posix
gcc version 4.2.0 20061016 (experimental)


-- 
   Summary: java.lang.InternalError: Pango: pango_color_parse:
assertion `spec != NULL' failed
   Product: gcc
   Version: 4.2.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: libgcj
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: powerpc-apple-darwin8.6.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29492



[Bug libgcj/29491] java.lang.InternalError: Pango: pango_color_parse: assertion `spec != NULL' failed

2006-10-18 Thread dir at lanl dot gov


--- Comment #2 from dir at lanl dot gov  2006-10-18 14:37 ---
This turned out to be a gtk bug - a rebuild of glib-2.12.4 followed by a
rebuild of gtk+-2.10.6 fixed the problem.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29491



[Bug libfortran/30617] recursive I/O hangs under OSX 10.3

2007-01-29 Thread dir at lanl dot gov


--- Comment #8 from dir at lanl dot gov  2007-01-29 13:45 ---
It hangs on a Intel iMac -

[pactech01:~/tests] dir% gfortran -o recursiveio recursiveio.f90
[pactech01:~/tests] dir% recursiveio
 test
   1.00


^C
[pactech01:~/tests] dir% cat recursiveio.f90
  external fun
  real fun
  real a
  a = fun()
  print *, a
  print *, fun()
  end
  real function fun()
  print *, 'test'
  fun = 1.0
  end
[dranta:~] dir% 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30617



[Bug fortran/31563] New: An Error is incorrectly generated for hex and octal data

2007-04-13 Thread dir at lanl dot gov
When trying to build a program with gfortran, these errors were generated.
Absoft f90 and g95 are happy with the program -

[dranta:~/junk] dir% gfortran -o mask mask.f90
mask.f90:3.30:

  data msk4/o'377'/
 1
Error: Arithmetic overflow converting INTEGER(8) to INTEGER(4) at (1)
mask.f90:2.27:

  data msk1/x'8000'/
  1
Error: Arithmetic overflow converting INTEGER(8) to INTEGER(4) at (1)
mask.f90:4.11:

  msk1=x'8000'
  1
Error: Arithmetic overflow converting INTEGER(8) to INTEGER(4) at (1)
mask.f90:5.11:

  msk4=o'377'
  1
Error: Arithmetic overflow converting INTEGER(8) to INTEGER(4) at (1)
[dranta:~/junk] dir% g95 -o mask mask.f90
[dranta:~/junk] dir% f90 -o mask mask.f90
[dranta:~/junk] dir% gfortran --v
Using built-in specs.
Target: powerpc-apple-darwin8.9.0
Configured with: ../gcc/configure --disable-multilib
--prefix=/usr/local/gfortran --enable-languages=c,fortran
Thread model: posix
gcc version 4.3.0 20070412 (experimental)
[dranta:~/junk] dir% cat  mask.f90
  INTEGER *4 msk1, msk4
  data msk1/x'8000'/
  data msk4/o'377'/
  msk1=x'8000'
  msk4=o'377'
  end


-- 
   Summary: An Error is incorrectly generated for hex and octal data
   Product: gcc
   Version: 4.3.0
Status: UNCONFIRMED
  Severity: normal
  Priority: P3
 Component: fortran
    AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: dir at lanl dot gov
  GCC host triplet: Darwin 8.9.0


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31563



[Bug fortran/31563] Arithmetic overflow and BOZ

2007-04-13 Thread dir at lanl dot gov


--- Comment #3 from dir at lanl dot gov  2007-04-13 15:28 ---
I do not see why you say the numbers over flow - g95 gives exactly the correct
answer when I print them out


[dranta:~/junk] dir% g95 -o mask mask.f90
[dranta:~/junk] dir% mask
8000
FF00
[dranta:~/junk] dir% cat mask.f90
  INTEGER *4 msk1, msk4
  data msk1/x'8000'/
  data msk4/o'377'/
  msk1=x'8000'
  msk4=o'377'
  PRINT '(Z8)', msk1
  PRINT '(Z8)', msk4
  end


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31563



  1   2   3   >