https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89266
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #12 from Domi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84387
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #10 from Domi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87751
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86979
--- Comment #15 from Dominique d'Humieres ---
Full test completed, the PR is fixed without regression. Thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86979
--- Comment #14 from Dominique d'Humieres ---
The patch in comment 13 fixes the ICE for pr69102.c. Testing will start soon.
Thanks for the work!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89539
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77604
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #5 from Dominique
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60576
--- Comment #29 from Dominique d'Humieres ---
> Is this still an issue?
I still get the stack-buffer-overflow reported in comment 26 with 8.2 and trunk
(9.0) but not with 7.4.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87625
--- Comment #7 from Dominique d'Humieres ---
> Yes, can this please be back-ported? Still broken on at least 8.
This is not a regression.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67542
--- Comment #10 from Dominique d'Humieres ---
> Yep, done.
Do you mean that the PR can be closed as FIXED?
I am wondering if the tests are valid Fortran.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89531
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53481
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89516
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79864
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67542
--- Comment #8 from Dominique d'Humieres ---
I cannot get any ICE with the options and revisions I have tried.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89492
--- Comment #2 from Dominique d'Humieres ---
> Can you please verify that your testcases work?
With the patch I get
pr34202_red.f90:8:54:
8 |write(*,*) transfer(transfer([1],[bug4()]),[1],size[1])
|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43210
--- Comment #7 from Dominique d'Humieres ---
> This is definitely an area where improvement would be quite helpful -
> our performance there is abysmal.
Compiling the test on my laptop takes less than 3s!
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43210
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70149
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31392
Bug 31392 depends on bug 70149, which changed state.
Bug 70149 Summary: [F08] Character pointer initialization causes ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70149
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68241
Bug 68241 depends on bug 70149, which changed state.
Bug 70149 Summary: [F08] Character pointer initialization causes ICE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70149
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71544
Dominique d'Humieres changed:
What|Removed |Added
CC||relliott at umn dot edu
--- Comme
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71412
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71935
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89282
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89496
Dominique d'Humieres changed:
What|Removed |Added
Keywords||ice-on-valid-code
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89492
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|UNCONFIRMED
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
CC: anlauf at gcc dot gnu.org
Target Milestone: ---
As reported at https://gcc.gnu.org/ml/fortran/2019-02/msg00198.html, after
revision
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89274
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88117
--- Comment #11 from Dominique d'Humieres ---
The ICE is now gone, but I get segmentation fault at run time. If I comment the
line
z = (z)
I get
ab
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Is this e
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89451
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61765
--- Comment #9 from Dominique d'Humieres ---
For the record, after revision r267902 the test in pr34500 comment 0 gives an
ICE instead of a wrong error (see pr34500 comment 6).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52879
--- Comment #7 from Dominique d'Humieres ---
> I think the current implementation has a decent protection against bad seeds,
> so lets close this as fixed.
The least I can say is that I am not convinced about the "decent protection".
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89366
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
--- Comment #6 from Dominique
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89348
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88117
Dominique d'Humieres changed:
What|Removed |Added
CC||pault at gcc dot gnu.org
Kno
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89365
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89431
--- Comment #3 from Dominique d'Humieres ---
program test
use iso_fortran_env
implicit none
write(*,*) integer_kinds
#ifdef __GFC_INT_1__
write(*,*) "__GFC_INT_1__ defined"
#else
write(*,*) "__GFC_INT_1__ undefined"
#endif
#ifdef __GFC_
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89431
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P5
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89366
--- Comment #4 from Dominique d'Humieres ---
> Fortran 2018 FDIS section 18.3.6, para 2, item 5, bullet 2:
On my draft it is probably
18.3.7 Interoperability of procedures and procedure interfaces
For
character(kind=c_char,len=:), allocat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46496
--- Comment #5 from Dominique d'Humieres ---
b) -Wno-c-binding-type silences the warnings related to C binding.
It remains in this PR the missed warnings in d) and e).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89366
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89348
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89385
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89365
--- Comment #4 from Dominique d'Humieres ---
> I agree with Harald's assessment. The test case as delivered by me
> is indeed incorrectly written for the POINTER and ALLOCATABLE cases,
> in both of which I believe the bounds should be taken from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89413
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89365
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60144
--- Comment #6 from Dominique d'Humieres ---
I don't understand the goal of the block (line 1651 of gcc/fortran/match.c)
/* The gfc_match_assignment() above may have returned a MATCH_NO
where the assignment was to a named constant. Check
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118
--- Comment #16 from Dominique d'Humieres ---
Compiling the reduced test
type :: any_vector
class(*), allocatable :: v(:)
end type
type(any_vector) :: x, y
x%v = ['foo','bar']
end
with -fsanitize=address gives
==54286==ERROR: AddressSanitize
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89388
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89363
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89384
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68649
--- Comment #26 from Dominique d'Humieres ---
> > The warnings are gone between revisions r265814 and r265942.
>
> I can confirm that.
> So, are there objections to just committing a test case and
> closing this bug?
My (shallow) understanding
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89375
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89364
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89374
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70149
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #13 from Domi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88248
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71880
Dominique d'Humieres changed:
What|Removed |Added
CC||clange001 at gmail dot com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68241
Bug 68241 depends on bug 89352, which changed state.
Bug 89352 Summary: Deferred length character array pointer error
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89352
What|Removed |Added
--
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89352
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89344
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89333
Dominique d'Humieres changed:
What|Removed |Added
Keywords||ice-on-valid-code
Sta
Component: ada
Assignee: unassigned at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
CC: ebotcazou at gcc dot gnu.org, iains at gcc dot gnu.org
Target Milestone: ---
Between revisions and the following ADA tests have started to fail:
FAIL: gnat.dg/vect1.adb 3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89291
--- Comment #4 from Dominique d'Humieres ---
> Installed gcc-5.5.0 and built the identical WRF version.
>
> No ICE encountered with 5.5.0.
Then if you get an ICE with 7.4, it a regression. Did you try 8.2 or trunk.
> Contacted NCAR, the provid
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78983
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83700
Bug 83700 depends on bug 78983, which changed state.
Bug 78983 Summary: [7/8/9 Regression] ICE with CAF-DT with allocatable member
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78983
What|Removed |Added
-
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89286
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89291
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89282
--- Comment #4 from Dominique d'Humieres ---
> Maybe it's been solved as part of other bugs I couldn't find by searching?
I don't think it is worth the effort to find when this has been fixed. I'll
commit your test and close the PR as FIXED.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89282
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49565
--- Comment #9 from Dominique d'Humieres ---
> I'd like some informed feedback on this before closing.
Me too, but what be done when I don't get any feedback over years?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53694
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49565
--- Comment #7 from Dominique d'Humieres ---
> Any progress after two years and a half?
Any progress after two and a half more years? Shouldn't this PR be closed as
FIXED (AFAIU this is not a fortran bug).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51591
--- Comment #6 from Dominique d'Humieres ---
> Nay progress after more than two years?
No progress after more than three more years?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83218
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87337
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61073
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56581
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56581
--- Comment #11 from Dominique d'Humieres ---
AFAIU "Unicode byte-order marker" is not part of the Fortran character set and
I think the test starting with it is invalid. No feedback, closing as INVALID.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51637
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89274
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P4
Status|UNCONFIRMED
: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
CC: jvdelisle at gcc dot gnu.org
Target Milestone: ---
The following test
integer(8) :: i(2)
integer(16) :: j(2)
i = -huge(1)
print *, i
i = -huge(1_8)
print *, i
j = huge(1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89266
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81552
--- Comment #4 from Dominique d'Humieres ---
> > IMO this PR should be closed as WONTFIX.
>
> Or document it - a single sentence should be enough.
Well the following patch (untested) "fixes" this PR:
--- ../_clean/gcc/fortran/gfortran.h2019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81552
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #2 from Domin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68940
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69061
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89236
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P5
Status|WAITING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52789
Dominique d'Humieres changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89240
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89236
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89219
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84006
--- Comment #4 from Dominique d'Humieres ---
> Looks valid to me.
>
> F2018, 16.9.184 STORAGE_SIZE (A [, KIND])
>
> 3 Arguments.
> A shall be a data object of any type. If it is polymorphic it shall not
> be an undefined pointer. If it is unlimit
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410
--- Comment #33 from Dominique d'Humieres ---
> Some of the tests in this PR are fixed by the patch at
>
> https://gcc.gnu.org/ml/fortran/2019-01/msg00065.html
Namely the original test does not ICE after r267820.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36383
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
--- Comment #1 from Domin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39624
Dominique d'Humieres changed:
What|Removed |Added
Priority|P3 |P5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54880
--- Comment #7 from Dominique d'Humieres ---
> The assert is meaningful, it is a bug if something is created
> with one context once and then something tries to change that
> context to something else. So whatever wants to change that
> is doing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56850
--- Comment #3 from Dominique d'Humieres ---
> Using GCC 4.1 with -std=f95 (but not GCC >=4.3) shows:
> real*8
>1
> Error: Nonstandard type declaration REAL*8 at (1)
While /opt/gcc/gcc4.3.1/bin/gfortran pr56850_red.f90 -std=f95 does n
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89204
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
801 - 900 of 7788 matches
Mail list logo