[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2016-11-16 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42207 janus at gcc dot gnu.org changed: What|Removed |Added Target Milestone|--- |4.6.0

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-04 Thread janus at gcc dot gnu dot org
--- Comment #19 from janus at gcc dot gnu dot org 2010-08-04 07:31 --- (In reply to comment #16) Here is a better patch: This patch also fixes the error messages in comment #0 on darwin with -m32. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42207

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-04 Thread janus at gcc dot gnu dot org
--- Comment #20 from janus at gcc dot gnu dot org 2010-08-04 19:49 --- Subject: Bug 42207 Author: janus Date: Wed Aug 4 19:49:19 2010 New Revision: 162879 URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=162879 Log: 2010-08-04 Janus Weil ja...@gcc.gnu.org PR

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-04 Thread janus at gcc dot gnu dot org
--- Comment #21 from janus at gcc dot gnu dot org 2010-08-04 20:00 --- Fixed with r162879. Closing. -- janus at gcc dot gnu dot org changed: What|Removed |Added

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread burnus at gcc dot gnu dot org
--- Comment #8 from burnus at gcc dot gnu dot org 2010-08-03 10:03 --- If I run the code in comment 4 with an appended end (to make it a complete program), I (still) get link errors: /tmp/cc3J3Ygi.o: In function `__m_MOD_new_bar': aa3.f90:(.text+0x2c): undefined reference to

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread janus at gcc dot gnu dot org
--- Comment #9 from janus at gcc dot gnu dot org 2010-08-03 11:36 --- (In reply to comment #8) If I run the code in comment 4 with an appended end (to make it a complete program), I (still) get link errors: /tmp/cc3J3Ygi.o: In function `__m_MOD_new_bar': aa3.f90:(.text+0x2c):

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread dominiq at lps dot ens dot fr
--- Comment #10 from dominiq at lps dot ens dot fr 2010-08-03 11:49 --- Well, what is target dependent are the funny messages in comment #0, which are only seen on darwin with -m32. I think it is a bogus way to report the 'undefined reference'. --

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread burnus at gcc dot gnu dot org
--- Comment #11 from burnus at gcc dot gnu dot org 2010-08-03 11:51 --- (In reply to comment #9) Well, what is target dependent are the funny messages in comment #0, which are only seen on darwin with -m32. I have to admit that the -fdump-tree-original-all looks strange to me (third

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread janus at gcc dot gnu dot org
--- Comment #12 from janus at gcc dot gnu dot org 2010-08-03 12:59 --- (In reply to comment #8) If I run the code in comment 4 with an appended end (to make it a complete program), I (still) get link errors: /tmp/cc3J3Ygi.o: In function `__m_MOD_new_bar': aa3.f90:(.text+0x2c):

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread dominiq at lps dot ens dot fr
--- Comment #13 from dominiq at lps dot ens dot fr 2010-08-03 13:43 --- (In reply to comment #12) Disclaimer: I haven't checked this for regressions. And I'm not sure yet if it really is the proper fix for this issue. The patch fixes the tests in this pr, but not those in pr44065. So

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread mikael at gcc dot gnu dot org
--- Comment #14 from mikael at gcc dot gnu dot org 2010-08-03 14:31 --- (In reply to comment #12) This error can be fixed by: [...] You may need to change the recently added gfc_commit_symbols in gfc_find_derived_vtabs into a per symbol gfc_commit_symbol (symbol). Otherwise one

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread dominiq at lps dot ens dot fr
--- Comment #15 from dominiq at lps dot ens dot fr 2010-08-03 15:31 --- I don't know if this related to comment #14, but with the patch of comment #12 the errors for the test pr37425#0 has changed from pr37425.f90:7.13: PROCEDURE :: assign_t_from_int 1 Error:

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread janus at gcc dot gnu dot org
--- Comment #16 from janus at gcc dot gnu dot org 2010-08-03 16:31 --- (In reply to comment #15) I don't know if this related to comment #14, but with the patch of comment #12 the errors for the test pr37425#0 has changed from The patch in comment #12 is actually not the best thing

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread dominiq at lps dot ens dot fr
--- Comment #17 from dominiq at lps dot ens dot fr 2010-08-03 18:08 --- With the patch in comment #16 (and the patches for pr44065 and pr44857) gfortran.dg/typebound_operator_4.f03 fails: FAIL: gfortran.dg/typebound_operator_4.f03 -O (test for excess errors) the extra errors are:

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2010-08-03 Thread dominiq at lps dot ens dot fr
--- Comment #18 from dominiq at lps dot ens dot fr 2010-08-03 18:55 --- Two mistakes in comment #17: (1) The extra errors are due to the patch in comment #5 of pr44065. (2) There are only two extra errors at the beginning. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42207

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2009-11-29 Thread janus at gcc dot gnu dot org
--- Comment #4 from janus at gcc dot gnu dot org 2009-11-29 12:31 --- (In reply to comment #2) On darwin, the errors appear only in 32 bit mode. Yes, I can confirm this on x86_64-apple-darwin10.2.0. Also, I just ran the fortran testsuite for the fortran-dev branch on darwin, but saw

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2009-11-29 Thread dominiq at lps dot ens dot fr
--- Comment #5 from dominiq at lps dot ens dot fr 2009-11-29 16:21 --- (In reply to comment #3) So how do I switch to 64-bit mode? On x86_64-apple-darwin* it is the default, so I assume you are using i686-apple-darwin*. In this case you need a multlib build and you compile with -m64.

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2009-11-29 Thread damian at rouson dot net
--- Comment #6 from damian at rouson dot net 2009-11-30 00:51 --- (In reply to comment #5) (In reply to comment #3) So how do I switch to 64-bit mode? On x86_64-apple-darwin* it is the default, so I assume you are using i686-apple-darwin*. In this case you need a multlib build

[Bug fortran/42207] [OOP] Compile-time errors on typed allocation and pointer function result assignment

2009-11-29 Thread damian at rouson dot net
--- Comment #7 from damian at rouson dot net 2009-11-30 01:16 --- Janus, Although the new reduced case compiles fine in 64-bit mode, I run into linking problems as soon as I add program main; end program to the end of it: Undefined symbols: _vtab$bar.1550, referenced from: