[Bug fortran/34975] [4.3 Regression] Bogus error with USEing modules

2008-01-26 Thread paulthomas2 at wanadoo dot fr
--- Comment #5 from paulthomas2 at wanadoo dot fr 2008-01-27 07:09 --- Subject: Re: [4.3 Regression] Bogus error with USEing modules burnus at gcc dot gnu dot org wrote: --- Comment #4 from burnus at gcc dot gnu dot org 2008-01-27 00:14 --- If the ONLY's i test.f90

[Bug fortran/34545] ICE when compiling Fortran 95 code

2008-01-06 Thread paulthomas2 at wanadoo dot fr
--- Comment #16 from paulthomas2 at wanadoo dot fr 2008-01-06 20:39 --- Subject: Re: ICE when compiling Fortran 95 code Tobias, Nothing - I have just updated to FC8 and blew all my nice set-up to pieces. This is the first time that Fedora has let me down. I will be operational

[Bug fortran/33897] Incorrect host association in module

2007-10-27 Thread paulthomas2 at wanadoo dot fr
--- Comment #12 from paulthomas2 at wanadoo dot fr 2007-10-27 15:47 --- Subject: Re: Incorrect host association in module burnus at gcc dot gnu dot org wrote: --- Comment #11 from burnus at gcc dot gnu dot org 2007-10-27 13:31 --- To recap (correct me, if I'm wrong

[Bug fortran/31711] rhs array is changed while assiging to same lhs array

2007-04-26 Thread paulthomas2 at wanadoo dot fr
--- Comment #7 from paulthomas2 at wanadoo dot fr 2007-04-26 23:04 --- Subject: Re: rhs array is changed while assiging to same lhs array Thomas, It's some trivial failure of the logic in gfc_dep_resolver. I took a quick look but did not see it because I am totally exhausted

[Bug fortran/31538] result_in_spec_1.f90: Invalid write

2007-04-11 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2007-04-11 21:05 --- Subject: Re: result_in_spec_1.f90: Invalid write Tobias, however, test(1) returns an array of the size (2*1+1)+1 = 4. Thanks for spotting that one. I'm just in the process of committing the fix as 'obvious

[Bug fortran/30531] allocatable component and intent(out) yield ICE in fold_convert

2007-03-08 Thread paulthomas2 at wanadoo dot fr
--- Comment #9 from paulthomas2 at wanadoo dot fr 2007-03-08 18:12 --- Subject: Re: allocatable component and intent(out) yield ICE in fold_convert Daniel, --- Comment #8 from dfranke at gcc dot gnu dot org 2007-03-08 16:36 --- Paul, could you have a look at PR31086? I

[Bug fortran/30887] %VAL only accepts default-kind integer/real/complex

2007-02-20 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2007-02-21 05:16 --- Subject: Re: %VAL only accepts default-kind integer/real/complex Tobias, --- Comment #1 from burnus at gcc dot gnu dot org 2007-02-20 17:32 --- Paul, do you remember why you have added the following

[Bug fortran/30779] incomplete file triggers ICE

2007-02-14 Thread paulthomas2 at wanadoo dot fr
--- Comment #6 from paulthomas2 at wanadoo dot fr 2007-02-14 20:54 --- Subject: Re: incomplete file triggers ICE jvdelisle at gcc dot gnu dot org wrote: --- Comment #5 from jvdelisle at gcc dot gnu dot org 2007-02-14 20:31 --- The patch is straight forward. Need to check

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2007-02-12 Thread paulthomas2 at wanadoo dot fr
--- Comment #58 from paulthomas2 at wanadoo dot fr 2007-02-12 22:55 --- Subject: Re: [meta-bugs] ICEs with CP2K jv244 at cam dot ac dot uk wrote: --- Comment #57 from jv244 at cam dot ac dot uk 2007-02-12 19:18 --- Yes, that's the one: http://gcc.gnu.org/ml/fortran

[Bug fortran/30660] [4.2 and 4.1 only] Allocatable components of a derived type require the SAVE attribute.

2007-02-05 Thread paulthomas2 at wanadoo dot fr
--- Comment #6 from paulthomas2 at wanadoo dot fr 2007-02-05 09:37 --- Subject: Re: [4.2 and 4.1 only] Allocatable components of a derived type require the SAVE attribute. toon, 1 Error: Object 'g_dest' at (1) must have the SAVE attribute for default

[Bug fortran/30625] Array pointers to components of derived type arrays do not work

2007-02-02 Thread paulthomas2 at wanadoo dot fr
--- Comment #5 from paulthomas2 at wanadoo dot fr 2007-02-02 19:20 --- Subject: Re: Array pointers to components of derived type arrays do not work dfranke at gcc dot gnu dot org wrote: --- Comment #4 from dfranke at gcc dot gnu dot org 2007-02-01 11:28 --- As I came

[Bug fortran/30399] testsuite failures in actual_array_constructor_2.f90 and actual_array_substr_2.f90

2007-01-11 Thread paulthomas2 at wanadoo dot fr
--- Comment #21 from paulthomas2 at wanadoo dot fr 2007-01-11 19:28 --- Subject: Re: testsuite failures in actual_array_constructor_2.f90 and actual_array_substr_2.f90 Kaveh, Paul - I understand that you may not have time to actually fix the bug. However something seems to have

[Bug fortran/30399] testsuite failures in actual_array_constructor_2.f90 and actual_array_substr_2.f90

2007-01-10 Thread paulthomas2 at wanadoo dot fr
--- Comment #14 from paulthomas2 at wanadoo dot fr 2007-01-10 22:09 --- Subject: Re: testsuite failures in actual_array_constructor_2.f90 and actual_array_substr_2.f90 Kaveh --- Comment #13 from ghazi at gcc dot gnu dot org 2007-01-10 21:45 --- Paul - The bug

[Bug fortran/25818] Problem with handling optional and entry master arguments

2006-12-07 Thread paulthomas2 at wanadoo dot fr
--- Comment #18 from paulthomas2 at wanadoo dot fr 2006-12-07 17:33 --- Subject: Re: Problem with handling optional and entry master arguments elizabeth, We are talking about the same machine and the same operating system. All the x86_64 binaries are from http

[Bug fortran/30068] Ambigous interfaces not detected

2006-12-07 Thread paulthomas2 at wanadoo dot fr
--- Comment #10 from paulthomas2 at wanadoo dot fr 2006-12-07 23:34 --- Subject: Re: Ambigous interfaces not detected burnus, I'm quite sure I wouldn't have understood the Although not referenced correctly without the deep look at the standard. And if it is indeed referenced

[Bug fortran/30068] Ambigous interfaces not detected

2006-12-06 Thread paulthomas2 at wanadoo dot fr
--- Comment #7 from paulthomas2 at wanadoo dot fr 2006-12-06 23:08 --- Subject: Re: Ambigous interfaces not detected Tobias, c) Gfortran is a bit inconsequent with regards to , only: use mod1 use mod2,only: foo compiles without an error/warning whereas for use mod1,only

[Bug fortran/29916] [4.1 and 4.2 only] Dimension of a function result as host association does not work

2006-12-04 Thread paulthomas2 at wanadoo dot fr
--- Comment #8 from paulthomas2 at wanadoo dot fr 2006-12-04 18:38 --- Subject: Re: [4.1 and 4.2 only] Dimension of a function result as host association does not work Tobias, t you saw the submission email (autoattached to this PR and thus also in your mailbox). As I said

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-12-03 Thread paulthomas2 at wanadoo dot fr
--- Comment #18 from paulthomas2 at wanadoo dot fr 2006-12-03 17:42 --- Subject: Re: [meta-bugs] ICEs with CP2K Tobias, The patch looks good -- and the test cases as well. Great! Just for completeness, the relevant part of the standard is: C1209 (R1206) A procedure-name shall

[Bug fortran/29975] [meta-bugs] ICEs with CP2K

2006-12-03 Thread paulthomas2 at wanadoo dot fr
--- Comment #19 from paulthomas2 at wanadoo dot fr 2006-12-03 19:41 --- Subject: Re: [meta-bugs] ICEs with CP2K Tobias, Note that this does not fix everything as gfortran rejects also interface_y.f90 if I comment the call bl_copy(1.0, chr); if I understand the standard correctly

[Bug fortran/25818] Problem with handling optional and entry master arguments

2006-12-02 Thread paulthomas2 at wanadoo dot fr
--- Comment #16 from paulthomas2 at wanadoo dot fr 2006-12-02 17:56 --- Subject: Re: Problem with handling optional and entry master arguments elizabeth dot l dot yip at boeing dot com wrote: It worked using gfortran on my OS X system. ~/src/C_C++ $ gfortran -v Using built

[Bug fortran/29976] [4.2/4.3 regression] ICE on optional arg

2006-11-27 Thread paulthomas2 at wanadoo dot fr
--- Comment #5 from paulthomas2 at wanadoo dot fr 2006-11-28 05:25 --- Subject: Re: [4.2/4.3 regression] ICE on optional arg jvdelisle at gcc dot gnu dot org wrote: --- Comment #4 from jvdelisle at gcc dot gnu dot org 2006-11-28 01:18 --- I think wrong url in comment #3

[Bug fortran/29976] [4.2/4.3 regression] ICE on optional arg

2006-11-26 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2006-11-27 06:19 --- Subject: Re: [4.2/4.3 regression] ICE on optional arg Andrew, We are calling build_int_cst on a real type. Yes, I discovered the same on my flight back to France last night. Will come up with a fix tonight

[Bug fortran/29391] LBOUND(TRANSPOSE(I)) doesn't work

2006-10-12 Thread paulthomas2 at wanadoo dot fr
--- Comment #11 from paulthomas2 at wanadoo dot fr 2006-10-12 15:57 --- Subject: Re: LBOUND(TRANSPOSE(I)) doesn't work FX ! if (upper) ! { ! cond1 = fold_build2 (GE_EXPR, boolean_type_node, ubound, lbound); ! cond2 = fold_build2 (LE_EXPR, boolean_type_node

[Bug fortran/29391] LBOUND(TRANSPOSE(I)) doesn't work

2006-10-11 Thread paulthomas2 at wanadoo dot fr
--- Comment #5 from paulthomas2 at wanadoo dot fr 2006-10-11 06:11 --- Subject: Re: LBOUND(TRANSPOSE(I)) doesn't work FX, That's because of F95 13.14.53: Case (i): For an array section or for an array expression other than a whole array or array structure component, LBOUND(ARRAY

[Bug fortran/29391] LBOUND(TRANSPOSE(I)) doesn't work

2006-10-11 Thread paulthomas2 at wanadoo dot fr
--- Comment #8 from paulthomas2 at wanadoo dot fr 2006-10-11 08:02 --- Subject: Re: LBOUND(TRANSPOSE(I)) doesn't work FX, I get all intrinsics that work through temporaries working right: Great! So I only have PRODUCT, SUM, MATMUL, PACK and UNPACK to work on. I wonder

[Bug fortran/29373] implicit type declaration and contained function clash

2006-10-11 Thread paulthomas2 at wanadoo dot fr
--- Comment #8 from paulthomas2 at wanadoo dot fr 2006-10-11 17:05 --- Subject: Re: implicit type declaration and contained function clash tobi at gcc dot gnu dot org wrote: --- Comment #6 from tobi at gcc dot gnu dot org 2006-10-11 16:07 --- You're working too fast, Paul

[Bug fortran/29373] implicit type declaration and contained function clash

2006-10-09 Thread paulthomas2 at wanadoo dot fr
--- Comment #3 from paulthomas2 at wanadoo dot fr 2006-10-09 20:11 --- Subject: Re: implicit type declaration and contained function clash tobi at gcc dot gnu dot org wrote: (BTW I added you to the CC list, it is kinda hard to answer in the right place otherwise) Oh s**t - next

[Bug fortran/27900] ICE using intrinsics as arguments

2006-10-05 Thread paulthomas2 at wanadoo dot fr
--- Comment #8 from paulthomas2 at wanadoo dot fr 2006-10-05 16:17 --- Subject: Re: ICE using intrinsics as arguments FX That bug is fixed by my submitted patch about INTRINSICS (http://gcc.gnu.org/ml/fortran/2006-10/msg00022.html). I'll review it tomorrow - I am going to give

[Bug fortran/29343] (Regression) Error on valid specification variables in same call to ALLOCATE

2006-10-04 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2006-10-04 16:33 --- Subject: Re: (Regression) Error on valid specification variables in same call to ALLOCATE Steve, I just wrote to Martin apologising and thanking him - the patch is regtesting right now and I am all geared up

[Bug fortran/29284] [4.1/4.2 Regression] ICE for optional subroutine argument

2006-10-01 Thread paulthomas2 at wanadoo dot fr
--- Comment #5 from paulthomas2 at wanadoo dot fr 2006-10-01 19:59 --- Subject: Re: [4.1/4.2 Regression] ICE for optional subroutine argument Dear All, PS: Just curious.. Why isn't this part of gfc_conv_function_call() coded to check for fsym once and only then have the additional

[Bug fortran/29101] Memory leak in gfortran

2006-09-19 Thread paulthomas2 at wanadoo dot fr
--- Comment #12 from paulthomas2 at wanadoo dot fr 2006-09-19 11:56 --- Subject: Re: Memory leak in gfortran steven at gcc dot gnu dot org wrote: --- Comment #8 from steven at gcc dot gnu dot org 2006-09-18 22:35 --- Not fixed just yet. Steven, I put it to rights

[Bug fortran/28908] [4.1/4.2 Regression]: fold_convert fails for Fortran operator

2006-09-04 Thread paulthomas2 at wanadoo dot fr
--- Comment #31 from paulthomas2 at wanadoo dot fr 2006-09-04 17:48 --- Subject: Re: [4.1/4.2 Regression]: fold_convert fails for Fortran operator hjl at lucon dot org wrote: --- Comment #30 from hjl at lucon dot org 2006-09-04 17:39 --- Gcc 4.2.0 revision 116560 plus

[Bug fortran/28908] [4.1/4.2 Regression]: fold_convert fails for Fortran operator

2006-09-04 Thread paulthomas2 at wanadoo dot fr
--- Comment #33 from paulthomas2 at wanadoo dot fr 2006-09-04 20:33 --- Subject: Re: [4.1/4.2 Regression]: fold_convert fails for Fortran operator Jack, I know *sigh* First I have to fix that which was working that I broke. Then I will fix that which was neither broken nor

[Bug fortran/28908] [4.1/4.2 Regression]: fold_convert fails for Fortran operator

2006-09-01 Thread paulthomas2 at wanadoo dot fr
--- Comment #27 from paulthomas2 at wanadoo dot fr 2006-09-01 17:24 --- Subject: Re: [4.1/4.2 Regression]: fold_convert fails for Fortran operator HJ, I might be slow but I get there... what has been plaguing me all week is doing the development under Cygwin. I just realised

[Bug fortran/28908] [4.1/4.2 Regression]: fold_convert fails for Fortran operator

2006-08-31 Thread paulthomas2 at wanadoo dot fr
--- Comment #13 from paulthomas2 at wanadoo dot fr 2006-08-31 17:41 --- Subject: Re: [4.1/4.2 Regression]: fold_convert fails for Fortran operator hjl at lucon dot org wrote: --- Comment #12 from hjl at lucon dot org 2006-08-31 16:57 --- It also fails with gcc 4.1 revision

[Bug fortran/28908] [4.1/4.2 Regression]: fold_convert fails for Fortran operator

2006-08-31 Thread paulthomas2 at wanadoo dot fr
--- Comment #16 from paulthomas2 at wanadoo dot fr 2006-08-31 18:20 --- Subject: Re: [4.1/4.2 Regression]: fold_convert fails for Fortran operator HJ Yes, I think that function interfaces in general are of the same horrible kind. Thanks Paul -- http://gcc.gnu.org/bugzilla

[Bug fortran/28908] [4.1/4.2 Regression]: fold_convert fails for Fortran operator

2006-08-31 Thread paulthomas2 at wanadoo dot fr
--- Comment #18 from paulthomas2 at wanadoo dot fr 2006-08-31 18:41 --- Subject: Re: [4.1/4.2 Regression]: fold_convert fails for Fortran operator hjl, --- Comment #17 from hjl at lucon dot org 2006-08-31 18:28 --- The previous gfc_get_derived_type tries to reuse the same

[Bug fortran/28908] [4.1/4.2 Regression]: fold_convert fails for Fortran operator

2006-08-31 Thread paulthomas2 at wanadoo dot fr
--- Comment #21 from paulthomas2 at wanadoo dot fr 2006-09-01 04:58 --- Subject: Re: [4.1/4.2 Regression]: fold_convert fails for Fortran operator hjl at lucon dot org wrote: Thanks HJ. It seems that I am going to have to revert this one; I have spent way too much time

[Bug fortran/28908] [4.2 Regression]: fold_convert fails for Fortran operator

2006-08-30 Thread paulthomas2 at wanadoo dot fr
--- Comment #7 from paulthomas2 at wanadoo dot fr 2006-08-30 20:01 --- Subject: Re: [4.2 Regression]: fold_convert fails for Fortran operator hjl at lucon dot org wrote: --- Comment #6 from hjl at lucon dot org 2006-08-30 19:40 --- Before the change, gfc_get_derived_type

[Bug fortran/28908] [4.2 Regression]: fold_convert fails for Fortran operator

2006-08-30 Thread paulthomas2 at wanadoo dot fr
--- Comment #10 from paulthomas2 at wanadoo dot fr 2006-08-30 21:03 --- Subject: Re: [4.2 Regression]: fold_convert fails for Fortran operator hjl at lucon dot org wrote: --- Comment #9 from hjl at lucon dot org 2006-08-30 20:38 --- The patch doesn't work for me: Starting

[Bug fortran/28908] [4.2 Regression]: fold_convert fails for Fortran operator

2006-08-30 Thread paulthomas2 at wanadoo dot fr
--- Comment #11 from paulthomas2 at wanadoo dot fr 2006-08-30 21:56 --- Subject: Re: [4.2 Regression]: fold_convert fails for Fortran operator HJ, I have cross-checked the patch between the two machines; it is the same. One regtests fine and the other segfaults in switch_types. I

[Bug fortran/28788] [gfortran: 4.1, 4.2 regression] ICE on valid code

2006-08-26 Thread paulthomas2 at wanadoo dot fr
--- Comment #12 from paulthomas2 at wanadoo dot fr 2006-08-26 09:30 --- Subject: Re: [gfortran: 4.1, 4.2 regression] ICE on valid code Jerry and Martin, All of this is very depressing - I can reproduce the 32 bit version of the problem and, I suppose, will reproduce the 64 bit

[Bug fortran/28788] [gfortran: 4.1, 4.2 regression] ICE on valid code

2006-08-25 Thread paulthomas2 at wanadoo dot fr
--- Comment #8 from paulthomas2 at wanadoo dot fr 2006-08-25 13:25 --- Subject: Re: [gfortran: 4.1, 4.2 regression] ICE on valid code martin, --- Comment #7 from martin at mpa-garching dot mpg dot de 2006-08-25 12:57 --- Hi Paul, sorry for the late reply, I was away

[Bug fortran/28005] [4.1 only] gfortran: matmul produces wrong result

2006-08-24 Thread paulthomas2 at wanadoo dot fr
--- Comment #9 from paulthomas2 at wanadoo dot fr 2006-08-24 21:40 --- Subject: Re: [4.1 only] gfortran: matmul produces wrong result Tobias, Seeing as it is you, I just put a first version on to cook; I simply copied everything below the line if (GFC_DESCRIPTOR_RANK (retarray

[Bug fortran/18111] spurious warnings with -W -Wunused

2006-08-21 Thread paulthomas2 at wanadoo dot fr
--- Comment #22 from paulthomas2 at wanadoo dot fr 2006-08-21 13:31 --- Subject: Re: spurious warnings with -W -Wunused martin, Should I open a new PR for this? I have a half memory that there is already a PR for this. Could you check first before submitting a new one

[Bug fortran/18111] spurious warnings with -W -Wunused

2006-08-21 Thread paulthomas2 at wanadoo dot fr
--- Comment #24 from paulthomas2 at wanadoo dot fr 2006-08-21 20:13 --- Subject: Re: spurious warnings with -W -Wunused martin, --- Comment #23 from martin at mpa-garching dot mpg dot de 2006-08-21 16:59 --- (In reply to comment #22) I have a half memory

[Bug fortran/18111] spurious warnings with -W -Wunused

2006-08-16 Thread paulthomas2 at wanadoo dot fr
--- Comment #16 from paulthomas2 at wanadoo dot fr 2006-08-16 21:58 --- Subject: Re: spurious warnings with -W -Wunused jakub at gcc dot gnu dot org wrote: --- Comment #15 from jakub at gcc dot gnu dot org 2006-08-16 13:04 --- It looks good to me. Thanks, Jakub; I

[Bug fortran/28548] [4.2 Regression]: Optional argument failed

2006-08-02 Thread paulthomas2 at wanadoo dot fr
--- Comment #4 from paulthomas2 at wanadoo dot fr 2006-08-02 12:02 --- Subject: Re: [4.2 Regression]: Optional argument failed I'll take a look at this as soon as I get home (friday). There is a PR out on PRESENT that I noticed before leaving. I'll try to gather together

[Bug fortran/28094] Modulo of real(kind=10) variables doesn't work

2006-06-20 Thread paulthomas2 at wanadoo dot fr
--- Comment #1 from paulthomas2 at wanadoo dot fr 2006-06-20 19:08 --- Subject: Re: New: Modulo of real(kind=10) variables doesn't work fxcoudert at gcc dot gnu dot org wrote: While working on PR 24518, I found the following: $ cat a.f90 real(kind=10) :: x = 10.0 print *, mod

[Bug fortran/16206] rejects valid array initialization expression

2006-06-16 Thread paulthomas2 at wanadoo dot fr
--- Comment #9 from paulthomas2 at wanadoo dot fr 2006-06-16 16:18 --- Subject: Re: rejects valid array initialization expression Harald, You might wish to extend this to m(5) = ..., because: integer, parameter :: p(8) = (/(m(i:i+1), i = 1,4)/) the last accessed

[Bug fortran/27411] crashes in sra_walk_expr and emit_move_insn

2006-05-18 Thread paulthomas2 at wanadoo dot fr
--- Comment #8 from paulthomas2 at wanadoo dot fr 2006-05-18 20:03 --- Subject: Re: crashes in sra_walk_expr and emit_move_insn tobi at gcc dot gnu dot org wrote: --- Comment #7 from tobi at gcc dot gnu dot org 2006-05-18 16:36 --- Paul, you didn't ask yourself to the CC

[Bug fortran/27155] Transfer of character to integer array and vice versa still doesn't work

2006-05-14 Thread paulthomas2 at wanadoo dot fr
--- Comment #18 from paulthomas2 at wanadoo dot fr 2006-05-14 13:43 --- Subject: Re: Transfer of character to integer array and vice versa still doesn't work bo, Ah, thank goodness for that. I thought that I was going out of my mind! For you purposes, rather than svn, have you

[Bug fortran/27155] Transfer of character to integer array and vice versa still doesn't work

2006-05-13 Thread paulthomas2 at wanadoo dot fr
--- Comment #5 from paulthomas2 at wanadoo dot fr 2006-05-13 07:23 --- Subject: Re: Transfer of character to integer array and vice versa still doesn't work Bo, You're very welcome, but actually thanks in Swedish spells tack. I had guessed you to be Norwegian Due

[Bug fortran/27155] Transfer of character to integer array and vice versa still doesn't work

2006-05-13 Thread paulthomas2 at wanadoo dot fr
--- Comment #7 from paulthomas2 at wanadoo dot fr 2006-05-13 09:31 --- Subject: Re: Transfer of character to integer array and vice versa still doesn't work Bo (and Andrew), I think that I have lost such few marbles as I ever had! Having converted to using the cl-backen_decl

[Bug fortran/27155] Transfer of character to integer array and vice versa still doesn't work

2006-05-13 Thread paulthomas2 at wanadoo dot fr
--- Comment #12 from paulthomas2 at wanadoo dot fr 2006-05-13 19:09 --- Subject: Re: Transfer of character to integer array and vice versa still doesn't work bo, Should I download the latest source code snapshot and apply the patch on that ? No, that will not help

[Bug fortran/27155] Transfer of character to integer array and vice versa still doesn't work

2006-05-13 Thread paulthomas2 at wanadoo dot fr
--- Comment #15 from paulthomas2 at wanadoo dot fr 2006-05-13 20:00 --- Subject: Re: Transfer of character to integer array and vice versa still doesn't work bo, Paul, I have only tried gfortran on 32 bit cpus. I downloaded the latest subversion snapshot, applied the patch

[Bug fortran/17298] gfortran ICE: Not Implemented: Scalarization of non-elemental intrinsic: __transfer1

2006-05-06 Thread paulthomas2 at wanadoo dot fr
--- Comment #24 from paulthomas2 at wanadoo dot fr 2006-05-06 08:02 --- Subject: Re: gfortran ICE: Not Implemented: Scalarization of non-elemental intrinsic: __transfer1 I'm unfamiliar with Bugzilla, so if I annoy anyone, apologies. You made a serious comment... you won't upset

[Bug tree-optimization/26994] [4.2 Regression] Scalar TRANSFER - error: invalid operand to unary operator

2006-04-03 Thread paulthomas2 at wanadoo dot fr
--- Comment #9 from paulthomas2 at wanadoo dot fr 2006-04-04 04:39 --- Subject: Re: [4.2 Regression] Scalar TRANSFER - error: invalid operand to unary operator pinskia at gcc dot gnu dot org wrote: --- Comment #8 from pinskia at gcc dot gnu dot org 2006-04-03 21:13

[Bug fortran/26227] accepts invalid fortran, different dummy types/number

2006-04-03 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2006-04-04 04:42 --- Subject: Re: accepts invalid fortran, different dummy types/number pinskia at gcc dot gnu dot org wrote: --- Comment #1 from pinskia at gcc dot gnu dot org 2006-04-04 01:37 --- Here is another testcase

[Bug tree-optimization/26994] Scalar TRANSFER - error: invalid operand to unary operator

2006-04-02 Thread paulthomas2 at wanadoo dot fr
--- Comment #5 from paulthomas2 at wanadoo dot fr 2006-04-03 00:56 --- Subject: Re: Scalar TRANSFER - error: invalid operand to unary operator pinskia at gcc dot gnu dot org wrote: --- Comment #4 from pinskia at gcc dot gnu dot org 2006-04-02 22:43 --- A work around

[Bug fortran/26891] Automatic conversion for optional parameters of missing dummies

2006-03-28 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2006-03-28 09:46 --- Subject: Re: Automatic conversion for optional parameters of missing dummies toon at moene dot indiv dot nluug dot nl wrote: --- Comment #1 from toon at moene dot indiv dot nluug dot nl 2006-03-28 08:15

[Bug libfortran/26890] SIZE parameter interacts with same variable in IO list character length specification.

2006-03-27 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2006-03-28 04:08 --- Subject: Re: SIZE parameter interacts with same variable in IO list character length specification. jvdelisle at gcc dot gnu dot org wrote: --- Comment #1 from jvdelisle at gcc dot gnu dot org 2006-03-28 01

[Bug fortran/26822] Scalarization of non-elemental intrinsic: __logical_4_l4

2006-03-23 Thread paulthomas2 at wanadoo dot fr
--- Comment #2 from paulthomas2 at wanadoo dot fr 2006-03-23 16:53 --- Subject: Re: New: Scalarization of non-elemental intrinsic: __logical_4_l4 Carsten, Would you be so kind as to send me bessj.f90, please? My Numerical Recipes is the F77 version! I am not sure that I know how

[Bug fortran/20938] Dependency checking fails for equivalences

2006-02-19 Thread paulthomas2 at wanadoo dot fr
--- Comment #4 from paulthomas2 at wanadoo dot fr 2006-02-19 19:25 --- Subject: Re: Dependency checking fails for equivalences tobi, --- Comment #3 from tobi at gcc dot gnu dot org 2006-02-19 18:56 --- I might be a little late, given that you already posted a patch which

[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 paulthomas2 at wanadoo dot fr
--- Comment #10 from paulthomas2 at wanadoo dot fr 2006-01-18 16:45 --- Subject: Re: [4.1/4.2 Regression] gfortran - incorrectly issues an error on tests for optional arguments with assumed length Dale, I am sorry that I upset you. It was completely unintentional. I upset

[Bug fortran/24276] Components of a derived type array not passed as an array

2006-01-09 Thread paulthomas2 at wanadoo dot fr
--- Comment #3 from paulthomas2 at wanadoo dot fr 2006-01-10 05:16 --- Subject: Re: Components of a derived type array not passed as an array pinskia at gcc dot gnu dot org wrote: --- Comment #2 from pinskia at gcc dot gnu dot org 2006-01-09 23:24 --- the parse tree

[Bug fortran/23308] named common block confused as procedure - runtime segfault

2006-01-08 Thread paulthomas2 at wanadoo dot fr
--- Comment #9 from paulthomas2 at wanadoo dot fr 2006-01-08 09:49 --- Subject: Re: named common block confused as procedure - runtime segfault pinskia at gcc dot gnu dot org wrote: --- Comment #8 from pinskia at gcc dot gnu dot org 2006-01-08 06:13 --- (In reply

[Bug fortran/23308] named common block confused as procedure - runtime segfault

2006-01-07 Thread paulthomas2 at wanadoo dot fr
--- Comment #6 from paulthomas2 at wanadoo dot fr 2006-01-07 21:44 --- Subject: Re: named common block confused as procedure - runtime segfault Steve and Andrew, --- Comment #5 from kargl at gcc dot gnu dot org 2006-01-07 20:19 --- Andrew, Lahey's code checking utility

[Bug fortran/23308] named common block confused as procedure - runtime segfault

2006-01-07 Thread paulthomas2 at wanadoo dot fr
--- Comment #7 from paulthomas2 at wanadoo dot fr 2006-01-07 21:46 --- Subject: Re: named common block confused as procedure - runtime segfault The enclosed patch catches Andrew's PR but also snags on g77/19990905-1.f (The Burley test case). In fact, it regtests OK, apart from

[Bug fortran/24409] ICE on module name vs dummy argument name

2005-11-08 Thread paulthomas2 at wanadoo dot fr
--- Comment #6 from paulthomas2 at wanadoo dot fr 2005-11-08 18:56 --- Subject: Re: ICE on module name vs dummy argument name tobi, --- Comment #4 from tobi at gcc dot gnu dot org 2005-11-07 13:07 --- (In reply to comment #3) Thank you Salvatore and Andrew. The proposed

[Bug fortran/24534] [4.0/4.1 Regression] PUBLIC derived types with private components

2005-11-05 Thread paulthomas2 at wanadoo dot fr
--- Comment #6 from paulthomas2 at wanadoo dot fr 2005-11-05 10:51 --- Subject: Re: [4.0/4.1 Regression] PUBLIC derived types with private components tobi at gcc dot gnu dot org wrote: --- Comment #5 from tobi at gcc dot gnu dot org 2005-11-01 19:22 --- CCing pault, as he

[Bug fortran/17744] ice in assignment of derived type constructor

2005-10-20 Thread paulthomas2 at wanadoo dot fr
--- Comment #6 from paulthomas2 at wanadoo dot fr 2005-10-21 04:19 --- Subject: Re: ice in assignment of derived type constructor Paul, do you want to add this as a testcase? I was in two minds about it. Checking that a structure exists before dereferencing it is not going

[Bug fortran/24440] [4.0/4.1 regression] gfortran failed to build 187.facerec

2005-10-18 Thread paulthomas2 at wanadoo dot fr
--- Comment #3 from paulthomas2 at wanadoo dot fr 2005-10-19 02:54 --- Subject: Re: [4.0 regression] gfortran failed to build 187.facerec hjl at lucon dot org wrote: --- Comment #1 from hjl at lucon dot org 2005-10-19 00:48 --- It is caused by http://gcc.gnu.org/ml/gcc

[Bug fortran/24092] ICE in trans-types.c for nested derived types

2005-10-14 Thread paulthomas2 at wanadoo dot fr
--- Comment #4 from paulthomas2 at wanadoo dot fr 2005-10-14 16:38 --- Subject: Re: ICE in trans-types.c for nested derived types pinskia at gcc dot gnu dot org wrote: --- Comment #3 from pinskia at gcc dot gnu dot org 2005-10-14 13:09 --- Fixed. Andrew, You keep

[Bug fortran/24158] ICE in f951 with nested, recursive derived types

2005-10-01 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-10-01 16:59 --- Subject: Re: ICE in f951 with nested, recursive derived types pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-10-01 15:38 --- Confirmed

[Bug fortran/18878] [4.0 only] erronous error message on vaild USE statement

2005-09-09 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-09-09 08:21 --- Subject: Re: [4.0 only] erronous error message on vaild USE statement fxcoudert at gcc dot gnu dot org wrote: --- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-09-09 07:55

[Bug fortran/23515] ICE on correct code

2005-08-22 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-22 18:18 --- Subject: Re: ICE on correct code pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-08-22 17:40 --- Confirmed. Back trace: #0

[Bug fortran/22304] gfortran silently changes values in equilvanence'd variables

2005-08-03 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-03 07:06 --- Mike, As I promised on the fortran list, I am about to tackle module equivalences. Since there are clearly associated issues with equivalences in general, I need to come to grips with those too. Your

[Bug fortran/17917] gfortran ICE on equivalence

2005-08-03 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-03 07:54 --- (In reply to comment #11) Patch posted here: http://gcc.gnu.org/ml/fortran/2005-06/msg00307.html This is still not complete. The example below produces separate unions, which represent the equivalences

[Bug fortran/18022] problem with structure and calling a function

2005-08-03 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-03 10:01 --- Tobi, We should agree the condition by which the call to gfc_trans_arrayfunc_assign is bypassed and get this one out of the way. The original, posted to the list, had: expr1-symtree-n.sym-ts.type

[Bug fortran/18737] ICE on invalid use of external keyword

2005-08-03 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-03 11:42 --- (In reply to comment #4) The bug is caused by the call to gfc_set_default_type in resolve.c:3961 passing 0 as second argument, thereby suppressing the error that should be issued there. Unfortunately

[Bug fortran/18878] Erronous error message on vaild USE statement

2005-08-03 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-03 11:51 --- Two separate USE statements works correctly, as the example below can demonstrate. This has got to be solvable Paul T module a integer, parameter :: b = kind(1.e0) end module a program d use

[Bug fortran/20890] initializing two equivalenced variabled

2005-08-03 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-03 12:05 --- (In reply to comment #1) I was sure this was a duplicate but I couldn't find it. It's effectively 15382, is it not? Paul T -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20890

[Bug fortran/21432] gfortran does not support printing of namelists

2005-08-03 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-03 12:31 --- Sorry if I appear dense, but where is the problem in changing namelist /cor/ a print cor to namelist /cor/ a write (*,cor) ? Or even horrible, horrible, horrible

[Bug fortran/18108] [gfortran] overloading does not work for functions

2005-08-02 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-02 07:54 --- I do apologise for missing this one: My fix for PR16940 fixes this fellow too. I would be grateful if the reporters can give the latest cvs a whirl to confirm that this is the case. This expanded

[Bug libfortran/16435] gfortran X edit descriptor failure: test f77-edit-x-out.f

2005-08-02 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-08-02 15:44 --- Subject: Re: gfortran X edit descriptor failure: test f77-edit-x-out.f fxcoudert at gcc dot gnu dot org wrote: --- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-08-02 10:52

[Bug fortran/20363] interface body has incorrect scope

2005-07-27 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-27 16:21 --- interfaces. This brings me to a question: what is a named interface? I This is a nameless interface, isn't it? module snafu interface subroutine really_snafu (foo) integer, intent

[Bug fortran/17379] Generic functions not resolved

2005-07-22 Thread paulthomas2 at wanadoo dot fr
-- Bug 17379 depends on bug 16940, which changed state. Bug 16940 Summary: Failure to perform host association correctly http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16940 What|Old Value |New Value

[Bug libfortran/22570] Null Characters instead of blanks in text output.

2005-07-22 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-22 19:19 --- fixed on mainline and 4.02 -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22570

[Bug libfortran/22570] Null Characters instead of blanks in text output.

2005-07-20 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-20 16:35 --- (In reply to comment #1) Confirmed, I think this was caused by: 2005-07-12 Paul Thomas [EMAIL PROTECTED] It sure as heck looks like me. I'm on to it! Paul -- http://gcc.gnu.org/bugzilla

[Bug libfortran/22570] Null Characters instead of blanks in text output.

2005-07-20 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-20 19:07 --- Subject: Re: Null Characters instead of blanks in text output. pinskia at gcc dot gnu dot org wrote: --- Additional Comments From pinskia at gcc dot gnu dot org 2005-07-20 15:41 --- Confirmed

[Bug libfortran/22570] Null Characters instead of blanks in text output.

2005-07-20 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-20 22:02 --- Subject: Re: Null Characters instead of blanks in text output. Steve, There are two problems: The output looks good though: 19 1 4 9162536496481 100 121 144

[Bug libfortran/22570] Null Characters instead of blanks in text output.

2005-07-20 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-21 05:33 --- Subject: Re: Null Characters instead of blanks in text output. Steven, The output looks good though: 19 1 4 9162536496481 100 121 144 169 196 225

[Bug libfortran/16435] gfortran X edit descriptor failure: test f77-edit-x-out.f

2005-07-19 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-20 04:23 --- Subject: Re: gfortran X edit descriptor failure: test f77-edit-x-out.f Please send me the test cases and preferably, post them on Bugzilla. Paul T -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id

[Bug libfortran/16435] gfortran X edit descriptor failure: test f77-edit-x-out.f

2005-07-19 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-20 04:29 --- I can help you with a test case if you need it. Yup, can't do a durned thing unless you show me where it hurts. I checked every aspect of the standard that I could. -- http://gcc.gnu.org

[Bug fortran/21730] Character length incorrect.

2005-07-13 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-13 17:43 --- (In reply to comment #2) Patch here http://gcc.gnu.org/ml/gcc-patches/2005-07/msg00937.html What about the testcase, David? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21730

[Bug fortran/20363] interface body has incorrect scope

2005-07-12 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-12 07:16 --- Subject: Re: interface body has incorrect scope Paul, do you have any idea what find_special could be intended for? It seems obvious that it does the wrong thing in the case of this PR, and I can't see

[Bug fortran/20363] interface body has incorrect scope

2005-07-11 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-11 20:02 --- Subject: Re: interface body has incorrect scope That seems to be as good as one could want! Paul T -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20363

[Bug fortran/15966] [4.0 Only] ICE and segmentation fault on internal write

2005-07-11 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-12 05:44 --- (In reply to comment #19) Fixed in 4.0.2 and above. Strictly speaking, pr15966 is fixed. However, writing to array internal files is still broken because no record length (aka character length) is being

[Bug fortran/20363] interface body has incorrect scope

2005-07-10 Thread paulthomas2 at wanadoo dot fr
--- Additional Comments From paulthomas2 at wanadoo dot fr 2005-07-10 16:57 --- Subject: Re: interface body has incorrect scope tobi at gcc dot gnu dot org wrote: --- Additional Comments From tobi at gcc dot gnu dot org 2005-07-10 15:37 --- Erik has posted a patch

  1   2   >