https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #9 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #8)
> If regtesting complete ok,
This is the case.
> and Mikael doesn't find any additional problems. Please commit.
The only thing I was
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #7 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #6)
> Harald, I looked at your patch and agree that simplification should be done.
> I don't know why I did not do it when I wrote walk_array_constructor().
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #14 from anlauf at gcc dot gnu.org ---
Is it conceivable that a somewhat weaker form of simplification, which
addresses the parentheses as well as the basic unary and binary operators
could still be used for the time being?
There is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #15 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #14)
> Is it conceivable that a somewhat weaker form of simplification, which
> addresses the parentheses as well as the basic unary and binary operators
> could
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #12 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #11)
> Here is an example, where the array simplifies using the host-associated
> parameter value instead of calling the contained function with the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
--- Comment #23 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #22)
> In looking at the patch, there is a
>
>gcc_assert (op1->ts.type != BT_UNKNOWN);
>
> in reduce_binary_ac() near line 1334 and
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107075
--- Comment #5 from anlauf at gcc dot gnu.org ---
There is a check in expr.cc:2623 that is reached if one changes the
testcase to a subroutine, but not if it is a program:
4615 if (!attr.save && rvalue->expr_type == EXPR_VARIABLE
4616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107075
--- Comment #6 from anlauf at gcc dot gnu.org ---
I tried the following patch, which however regresses on a couple testcases:
diff --git a/gcc/fortran/resolve.cc b/gcc/fortran/resolve.cc
index d9d101775f6..cfc6fc055bd 100644
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100971
--- Comment #3 from anlauf at gcc dot gnu.org ---
Just from a purely technical point, the following would allow to trigger the
proper check, as it allows to look into arrays, and regtests OK:
diff --git a/gcc/fortran/resolve.cc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #6 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #5)
> Both match type "integer", kind "4", rank "0".
>
> AFAIK, there is no other consideration than TKR to discern which function
> to call.
Yes, assuming
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66409
--- Comment #10 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #7)
> I think it's in 15.4.3.4.5 Restrictions on generic declarations.
> But it's too late for me to decipher what's written there.
Tomorrow you'll
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105371
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107217
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107215
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107215
--- Comment #2 from anlauf at gcc dot gnu.org ---
Created attachment 53692
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53692=edit
Patch
Check type of source expr before conversion.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107219
anlauf at gcc dot gnu.org changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107215
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107217
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107215
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107074
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Attachment #53651|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100029
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100040
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102275
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to fail||10.4.0, 11.2.0, 11.3.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100971
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100103
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |12.3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100132
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Attachment #53601|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
--- Comment #17 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #16)
> Created attachment 53651 [details]
> Revised patch
Unfortunately this regresses on gfortran.dg/pr91552.f90, e.g.
print *, 2 * [real :: 1, [2], 3]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #21 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #17)
> Like this for the first part of the test from the patch:
>
> diff --git a/gcc/fortran/arith.cc b/gcc/fortran/arith.cc
> index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #22 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #11)
> Here is an example, where the array simplifies using the host-associated
> parameter value instead of calling the contained function with the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #23 from anlauf at gcc dot gnu.org ---
Created attachment 53706
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53706=edit
Updated patch
Here's a patch that incorporates comment#17 and comment#20 and adds a testcase
for comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100971
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Attachment #53706|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #25 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #24)
> First, the ARITH_INVALID_TYPE should be renamed as it has now a broader
> usage (ARITH_OP_NOT_LITERAL_VALUE is a bit long, ARITH_OP_NOT_CONSTANT is a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107141
--- Comment #3 from anlauf at gcc dot gnu.org ---
Placing the subroutine into a module also avoids the error.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107141
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93483
--- Comment #28 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #27)
> (In reply to anlauf from comment #25)
> > (In reply to Mikael Morin from comment #24)
> > > First, the ARITH_INVALID_TYPE should be renamed as it has
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107272
Bug ID: 107272
Summary: ICE in gfc_compare_string and others (related to
pr107217)
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107054
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107000
--- Comment #14 from anlauf at gcc dot gnu.org ---
(In reply to Mikael Morin from comment #13)
> If we pass this check, we proceed to reduce_binary, where if one (or both)
> of the operands is an array, we do numerical evaluation for every
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82868
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |10.5
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83700
Bug 83700 depends on bug 82868, which changed state.
Bug 82868 Summary: ICE in generate_coarray_sym_init, at
fortran/trans-decl.c:5203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82868
What|Removed |Added
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102334
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102312
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99349
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106817
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92805
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77652
--- Comment #8 from anlauf at gcc dot gnu.org ---
I have pushed a relaxed version of the checks as agreed upon on the ML.
As compilers seem to differ here (we are now closer to Crayftn and Nvidia),
and as suggested by Toon, Mikael plans to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107444
--- Comment #1 from anlauf at gcc dot gnu.org ---
It appears that there is also confusion about the procedure decl.
This is demonstrated by:
program p
call s()
call s('') ! Actual argument is too short, reject?
call s('a')
call
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107444
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107444
--- Comment #3 from anlauf at gcc dot gnu.org ---
Regarding ABI questions, I've inquired on the ML:
https://gcc.gnu.org/pipermail/fortran/2022-November/058410.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107331
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69604
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||accepts-invalid,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[10/11/12/13 Regression]|[10/11 Regression]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97345
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97345
--- Comment #4 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #3)
> (In reply to anlauf from comment #2)
> > +
> > + mpz_clear (do_start);
> > + mpz_clear (do_end);
> > + mpz_clear (do_step);
> >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97345
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107508
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108336
--- Comment #4 from anlauf at gcc dot gnu.org ---
There is one flaw with the testcase: when OMP_NUM_THREADS > n1,
array elements threadval(n1+1:OMP_NUM_THREADS) are filled with
undefined values.
When I replace the line
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108369
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108233
Bug ID: 108233
Summary: [Coarray] bcast to non-allocatable COMPLEX scalar
coarray may generate wrong result
Product: gcc
Version: 13.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69604
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
--- Comment #15 from anlauf at gcc dot gnu.org ---
Created attachment 54006
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54006=edit
Modified testcase
I found that I get a hang on my system when I specify -fopenmp.
It appears that there
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
--- Comment #17 from anlauf at gcc dot gnu.org ---
(In reply to Jerry DeLisle from comment #16)
> (In reply to anlauf from comment #15)
> --- snip ---
> > Can you please verify?
>
> Yes, this fixes the test case.
OK, thanks for confirming.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
--- Comment #19 from anlauf at gcc dot gnu.org ---
(In reply to john.harper from comment #18)
> An interesting problem! But I thought my original test case did not have
> recursive I/O because tstuff and fstuff each print something in the
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
--- Comment #20 from anlauf at gcc dot gnu.org ---
(In reply to anlauf from comment #19)
> I don't recall having seen a mentioning in the standard of the order of
> evaluation of different function (or subroutine) arguments. Do you?
The
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107753
--- Comment #15 from anlauf at gcc dot gnu.org ---
(In reply to kargl from comment #14)
> Comment #10 contains a simple timing measurement in from my Intel Core2 Duo
> based system. gfortran with its current method (ie., -fcx-fortran-rules)
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107874
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107753
--- Comment #13 from anlauf at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #12)
> The optimization level is irrelevant. gfortran unilaterally
> uses -fcx-fortran-rules, and there is no way to disable this
> option to user the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108010
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108010
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-12-07
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108010
--- Comment #3 from anlauf at gcc dot gnu.org ---
Submitted: https://gcc.gnu.org/pipermail/fortran/2022-December/058586.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108010
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |13.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102180
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107872
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107872
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107995
--- Comment #6 from anlauf at gcc dot gnu.org ---
Can we close this one? (Target milestone 13)?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102180
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107995
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
Target
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107441
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106856
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107968
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2022-12-05
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131
--- Comment #2 from anlauf at gcc dot gnu.org ---
Possibly caused by the fix for pr103505 (commit r12-5779).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Known to work||10.3.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108109
--- Comment #1 from anlauf at gcc dot gnu.org ---
Is this attached file to be preprocessed? Or does it need special options?
Can't reproduce here.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95947
--- Comment #5 from anlauf at gcc dot gnu.org ---
The dump tree shows near the pack intrinsic:
- for character(len=10):
atmp.4.dtype = {.elem_len=10, .rank=1, .type=6};
atmp.4.span = 10;
atmp.4.data = 0B;
atmp.4.offset = 0;
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108131
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Keywords||wrong-code
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107872
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107872
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|--- |13.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107872
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Target Milestone|13.0|10.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79426
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Summary|[10/11/12/13 Regression]|[10 Regression] fortran -
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108109
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95947
--- Comment #6 from anlauf at gcc dot gnu.org ---
Setting a breakpoint in gfc_resolve_pack, I find for the len=: case:
(gdb) p *array->ts.u.cl
$12 = {length = 0x0, next = 0x2cc7af0, length_from_typespec = false,
backend_decl = 0x0,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107423
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79426
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Status|NEW |WAITING
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95375
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |anlauf at gcc dot
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95375
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |FIXED
1201 - 1300 of 2141 matches
Mail list logo