This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/44232] function result with pointer to strided component of argument
- From: "fxcoudert at gcc dot gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 6 Aug 2010 09:05:09 -0000
- Subject: [Bug fortran/44232] function result with pointer to strided component of argument
- References: <bug-44232-19220@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #12 from fxcoudert at gcc dot gnu dot org 2010-08-06 09:05 -------
(In reply to comment #8)
> Hmm. I've now built gfortran 4.5.1 20100521 (from the branch) and still have
> the same internal compiler error.
I have gcc 4.5.1 20100506 on x86_64-apple-darwin10.3.0, and it compiles fine.
The Fortran patches between my version and yours are:
------------------
Revision 159556
2010-05-19 Tobias Burnus <burnus@net-b.de>
PR fortran/43591
* expr.c (gfc_is_constant_expr, gfc_traverse_expr): Handle
proc-pointers and type-bound procedures.
(gfc_specification_expr): Check proc-pointers for pureness.
Revision 159417
2010-05-14 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/44135
* fortran/interface.c (get_sym_storage_size): Use signed instead of
unsigned mpz_get_?i routines.
Revision 159363
PR fortran/44036
* openmp.c (resolve_omp_clauses): Allow procedure pointers in clause
variable lists.
* trans-openmp.c (gfc_omp_privatize_by_reference): Don't privatize
by reference dummy procedures or non-dummy procedure pointers.
(gfc_omp_predetermined_sharing): Return
OMP_CLAUSE_DEFAULT_FIRSTPRIVATE for dummy procedures.
Revision 159306
2010-05-12 Daniel Franke <franke.daniel@gmail.com>
PR fortran/40728
* intrinc.c (gfc_is_intrinsic): Do not prematurely mark symbol
as external.
Revision 159101
2010-05-06 Tobias Burnus <burnus@net-b.de>
PR fortran/43985
* trans-types.c (gfc_sym_type): Mark Cray pointees as
GFC_POINTER_TYPE_P.
------------------
None of these look like they could be "it". It could be something outside the
Fortran front-end, or a 32/64-bit issue (but then, we'd probably see it on
32-bit linux too).
If you have time, can you:
1. Using "gfortran -v", isolate the invocation of the compiler itself, f951
2. Copy-paste this command-line and run it under gdb: "gdb -args [command
line here]"
3. When it aborts, backtrace (command "bt") and copy-paste the output of gdb.
This will give information on where to look.
--
fxcoudert at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44232