[Bug other/86656] [meta-bug] Issues found with -fsanitize=address

2020-09-17 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86656 Bug 86656 depends on bug 96041, which changed state. Bug 96041 Summary: [11 regression] ICE in gfortran.dg/pr93423.f90 after r11-1792 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96041 What|Removed |Added --

[Bug fortran/93423] [8/9/10/11 Regression] ICE on invalid with argument list for module procedure

2020-09-17 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93423 Bug 93423 depends on bug 96041, which changed state. Bug 96041 Summary: [11 regression] ICE in gfortran.dg/pr93423.f90 after r11-1792 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96041 What|Removed |Added --

[Bug target/97102] New: [nvptx] PTX JIT compilation failed when using aliases

2020-09-18 Thread burnus at gcc dot gnu.org
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: vries at gcc dot gnu.org Target Milestone: --- [Found when testing a patch for PR96390, which works with GCN offloading but not with nvptx

[Bug target/97102] [nvptx] PTX JIT compilation failed when using aliases

2020-09-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97102 --- Comment #1 from Tobias Burnus --- (In reply to Tobias Burnus from comment #0) > .visible .func (.param.u32 %value_out) foo https://docs.nvidia.com/cuda/parallel-thread-execution/index.html#kernel-and-function-directives-alias has the exampl

[Bug target/97102] [nvptx] PTX JIT compilation failed when using aliases

2020-09-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97102 --- Comment #2 from Tobias Burnus --- Created attachment 49239 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49239&action=edit Draft patch PTX ISA Notes .alias directive introduced in PTX ISA 6.3. Thus, it does not work everywhere :-( P

[Bug target/97102] [nvptx] PTX JIT compilation failed when using aliases

2020-09-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97102 --- Comment #3 from Tobias Burnus --- (In reply to Tobias Burnus from comment #2) > PTX ISA Notes > .alias directive introduced in PTX ISA 6.3. Which is CUDA 10.0, cf. https://docs.nvidia.com/cuda/archive/10.0/cuda-toolkit-release-notes/index.ht

[Bug target/97106] New: [nvptx] Issues with weak aliases introduced by C++

2020-09-18 Thread burnus at gcc dot gnu.org
Priority: P3 Component: target Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: vries at gcc dot gnu.org Depends on: 97102 Target Milestone: --- Created attachment 49240 --> https://gcc.gnu.org/bugzi

[Bug target/97106] [nvptx] Issues with weak aliases introduced by C++

2020-09-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97106 --- Comment #1 from Tobias Burnus --- Suggested fix: 14:11 < amonakov> Tobias__: I think the proper way to solve this is define hooks for the backend to print something for aliases, and then have nvptx-ld.c resolve them 14:12 < amonakov> (right

[Bug lto/97179] New: [LTO][Offloading] LTO's ltrans partiitioning causes link errors for offload_vars + offload_funcs ("undefined reference")

2020-09-23 Thread burnus at gcc dot gnu.org
Product: gcc Version: 11.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org

[Bug fortran/92122] [coarrays, polymophism] Error 'must be a scalar of type LOCK_TYPE'

2019-10-17 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92122 --- Comment #2 from Tobias Burnus --- Regarding the discussion of comment 0, see: https://mailman.j3-fortran.org/pipermail/j3/2019-October/011691.html https://mailman.j3-fortran.org/pipermail/j3/2019-October/011692.html "So, the whole argument h

[Bug libfortran/92027] [10 regression] gfortran.dg/ISO_Fortran_binding_10.f90 FAILs – conditional jump based on uninitialized memory in runtime/ISO_Fortran_binding.c

2019-10-17 Thread burnus at gcc dot gnu.org
|UNCONFIRMED |NEW Last reconfirmed||2019-10-17 CC||burnus at gcc dot gnu.org, ||pault at gcc dot gnu.org Summary|[10 regression] |[10 regression

[Bug fortran/91586] [9/10 Regression] ICE in gfc_find_derived_vtab, at fortran/class.c:2245

2019-10-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91586 --- Comment #1 from Tobias Burnus --- Author: burnus Date: Fri Oct 18 12:04:31 2019 New Revision: 277153 URL: https://gcc.gnu.org/viewcvs?rev=277153&root=gcc&view=rev Log: Fortran] PR91586 Fix ICE on invalid code with CLASS gcc/fortran/

[Bug fortran/91586] [9/10 Regression] ICE in gfc_find_derived_vtab, at fortran/class.c:2245

2019-10-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91586 --- Comment #2 from Tobias Burnus --- Author: burnus Date: Fri Oct 18 12:38:26 2019 New Revision: 277154 URL: https://gcc.gnu.org/viewcvs?rev=277154&root=gcc&view=rev Log: Fortran] PR91586 Fix ICE on invalid code with CLASS gcc/fortran/

[Bug fortran/91586] [9/10 Regression] ICE in gfc_find_derived_vtab, at fortran/class.c:2245

2019-10-18 Thread burnus at gcc dot gnu.org
||burnus at gcc dot gnu.org Resolution|--- |FIXED --- Comment #3 from Tobias Burnus --- FIXED on trunk + GCC 9 branch. Thanks for the report!

[Bug fortran/91941] [8/9/10 Regression] ICE in gfc_conv_expr_descriptor, at fortran/trans-array.c:7336

2019-10-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91941 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug fortran/92189] New: Fortran-written bind(C) function with allocatable argument does not update C descriptor on exit

2019-10-23 Thread burnus at gcc dot gnu.org
Keywords: wrong-code Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: pault at gcc dot gnu.org Target Milestone: --- Created attachment 47090

[Bug fortran/91863] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:156

2019-10-28 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91863 --- Comment #2 from Tobias Burnus --- Author: burnus Date: Mon Oct 28 07:33:29 2019 New Revision: 277502 URL: https://gcc.gnu.org/viewcvs?rev=277502&root=gcc&view=rev Log: Fortran] PR91863 - fix call to bind(C) with array descriptor PR

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-10-28 Thread burnus at gcc dot gnu.org
|UNCONFIRMED |NEW Last reconfirmed||2019-10-28 CC||burnus at gcc dot gnu.org Summary|internal compile error, |[9/10 Regression] internal |character array of dynamic |compile

[Bug middle-end/92250] New: valgrind: ira_traverse_loop_tree – Conditional jump or move depends on uninitialised value

2019-10-28 Thread burnus at gcc dot gnu.org
Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- When looking at PR 92191. If I compile the example there (attachment 47091) using valgrind as wrapper, I

[Bug fortran/91863] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:156

2019-10-28 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91863 --- Comment #3 from Tobias Burnus --- Author: burnus Date: Mon Oct 28 09:36:27 2019 New Revision: 277505 URL: https://gcc.gnu.org/viewcvs?rev=277505&root=gcc&view=rev Log: Fortran] PR91863 - fix call to bind(C) with array descriptor Bac

[Bug fortran/91863] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:156

2019-10-28 Thread burnus at gcc dot gnu.org
||burnus at gcc dot gnu.org Resolution|--- |FIXED --- Comment #4 from Tobias Burnus --- FIXED in GCC 9 + 10. Thanks for the report! When fixing this issue, I found another issue – if the bind(C) function is written in Fortran. That's tracked

[Bug fortran/92189] Fortran-written bind(C) function with allocatable argument does not update C descriptor on exit

2019-10-28 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92189 --- Comment #1 from Tobias Burnus --- The attached test case is gcc/testsuite/gfortran.dg/bind-c-intent-out.f90 which is part of the committed to fix PR 91863. Due to this PR, the committed test case uses 'dg-do compile' instead of 'dg-do run'.

[Bug fortran/91863] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:156

2019-10-28 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91863 --- Comment #6 from Tobias Burnus --- (In reply to paul.richard.tho...@gmail.com from comment #5) > It was my intention to commit the patch for PR91926 to 9-branch > tonight. I take it that there was no problem with yours? Yes, fine with me. (I

[Bug fortran/92178] Segmentation fault after passing allocatable array as intent(out) and its element as value into the same subroutine

2019-10-28 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92178 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-10-28 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208 Tobias Burnus changed: What|Removed |Added CC||tkoenig at gcc dot gnu.org --- Comment #

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-10-29 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208 --- Comment #3 from Tobias Burnus --- "fixed" by the following patch: * The LHS [se->string_length] is the string length represented as MAX_EXPR <(integer(kind=8)) D.4012, 0> * The RHS [expr->ts.u.cl->backend_decl] is ..__result The question i

[Bug fortran/92277] [10 Regression] ICE with assumed rank in gfc_conv_gfc_desc_to_cfi_desc

2019-10-30 Thread burnus at gcc dot gnu.org
|UNCONFIRMED |NEW Last reconfirmed||2019-10-30 CC||burnus at gcc dot gnu.org, ||pault at gcc dot gnu.org Summary|ICE with assumed rank |[10

[Bug fortran/92284] Subroutine with bind(c) attribute causing varied problems

2019-10-30 Thread burnus at gcc dot gnu.org
||burnus at gcc dot gnu.org Depends on||92189 Resolution|--- |INVALID --- Comment #1 from Tobias Burnus --- > The problems reported vary depending on the array having the allocatable or > pointer attribute

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-10-30 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208 --- Comment #4 from Tobias Burnus --- Author: burnus Date: Wed Oct 30 20:01:36 2019 New Revision: 277639 URL: https://gcc.gnu.org/viewcvs?rev=277639&root=gcc&view=rev Log: Fortran] PR 92208 don't use function-result dummy variable as actual argu

[Bug fortran/92284] Subroutine with bind(c) attribute causing varied problems

2019-10-30 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92284 Tobias Burnus changed: What|Removed |Added Keywords||wrong-code Status|RESOLVED

[Bug fortran/92277] [10 Regression] ICE with assumed rank in gfc_conv_gfc_desc_to_cfi_desc

2019-10-31 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92277 --- Comment #2 from Tobias Burnus --- Author: burnus Date: Thu Oct 31 10:06:19 2019 New Revision: 277661 URL: https://gcc.gnu.org/viewcvs?rev=277661&root=gcc&view=rev Log: Fortran] PR92277 - Fix assumed-rank array with bind(C) gcc/fortr

[Bug fortran/92284] Subroutine with bind(c) attribute causing varied problems

2019-10-31 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92284 --- Comment #6 from Tobias Burnus --- Author: burnus Date: Thu Oct 31 10:12:55 2019 New Revision: 277663 URL: https://gcc.gnu.org/viewcvs?rev=277663&root=gcc&view=rev Log: Fortran] PR92284 – gfc_desc_to_cfi_desc fixes gcc/fortran/

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-10-31 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #1 from Tobias Burnus --- Technically, this patch only adds '{ dg-do run }' which has the effect that the code is not only run once but multiple times with different compiler options (-O1, -O2 etc.). Your code fails to execute with -

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-10-31 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #2 from Tobias Burnus --- (In reply to Tobias Burnus from comment #1) > As you could nail it down to a single commit, I assume, you could reproduce > the problem – still, I am completely lost why it fails for you at -O0. Can > you try

[Bug fortran/92350] New: Document non-standard namelist quote handling in gfortran

2019-11-04 Thread burnus at gcc dot gnu.org
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jvdelisle at gcc dot gnu.org Target Milestone: --- This came up very recently at https://software.intel.com/en

[Bug fortran/92350] Document non-standard namelist quote handling in gfortran

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92350 --- Comment #1 from Tobias Burnus --- Just found: gfortran.texi – Extensions to namelist When writing a namelist, if no @code{DELIM=} is specified, by default a double quote is used to delimit character strings. If -std=F95, F2003, or F200

[Bug fortran/92350] Document non-standard namelist quote handling in gfortran

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92350 --- Comment #2 from Tobias Burnus --- For the added text, cf. PR 60148 and https://gcc.gnu.org/ml/fortran/2014-03/msg00145.html I missed that patch when writing this PR because it wasn't posted to gcc-patches@ :-(

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #4 from Tobias Burnus --- Author: burnus Date: Mon Nov 4 10:01:22 2019 New Revision: 277769 URL: https://gcc.gnu.org/viewcvs?rev=277769&root=gcc&view=rev Log: libgomp/testsuite - use unique numbers with Fortran's 'stop' PR

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #5 from Tobias Burnus --- (In reply to seurer from comment #3) > Is there an easy way I can catch any of them that fire? Now fixed by using unique numbers in libgomp/testsuite. But replacing 'stop' by 'error stop' is one option - th

[Bug fortran/92311] Fortran and OpenMP use_device_ptr and OpenACC attach_ptr/dettach_ptr

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92311 --- Comment #6 from Tobias Burnus --- (In reply to Nichols A. Romero from comment #0) > For the OpenACC program, it may be that this is part of the OpenACC spec > that has not been implemented yet. [That's detach/attach] This OpenACC 2.6 feature

[Bug fortran/92284] Subroutine with bind(c) attribute causing varied problems

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92284 --- Comment #8 from Tobias Burnus --- Author: burnus Date: Mon Nov 4 14:14:43 2019 New Revision: 277781 URL: https://gcc.gnu.org/viewcvs?rev=277781&root=gcc&view=rev Log: Backport Fortran BIND(C) fixes gcc/fortran/ Backport fro

[Bug fortran/92277] [10 Regression] ICE with assumed rank in gfc_conv_gfc_desc_to_cfi_desc

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92277 --- Comment #3 from Tobias Burnus --- Author: burnus Date: Mon Nov 4 14:14:43 2019 New Revision: 277781 URL: https://gcc.gnu.org/viewcvs?rev=277781&root=gcc&view=rev Log: Backport Fortran BIND(C) fixes gcc/fortran/ Backport fro

[Bug fortran/92277] [10 Regression] ICE with assumed rank in gfc_conv_gfc_desc_to_cfi_desc

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92277 Tobias Burnus changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/92284] Subroutine with bind(c) attribute causing varied problems

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92284 Tobias Burnus changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208 --- Comment #5 from Tobias Burnus --- Author: burnus Date: Mon Nov 4 15:07:19 2019 New Revision: 277783 URL: https://gcc.gnu.org/viewcvs?rev=277783&root=gcc&view=rev Log: Fortran] PR 92208 don't use function-result dummy variable as actual argu

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-11-04 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208 Tobias Burnus changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/92358] New: libgfortran/io/async.c:548:37: warning: unused parameter 'cmp'

2019-11-04 Thread burnus at gcc dot gnu.org
ty: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jvdelisle at gcc dot gnu.org Target Milestone: --- I get the following warning when compiling libgfortran: libgfortran/io/asyn

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-11-05 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208 --- Comment #8 from Tobias Burnus --- (In reply to Christophe Lyon from comment #7) > On gcc-9, the patch introduced regressions, seen on arm and aarch64: On trunk, the following was needed (PR92277, r277661) – but I it did not trigger on the br

[Bug fortran/92277] [10 Regression] ICE with assumed rank in gfc_conv_gfc_desc_to_cfi_desc

2019-11-05 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92277 --- Comment #5 from Tobias Burnus --- Author: burnus Date: Tue Nov 5 14:28:07 2019 New Revision: 277840 URL: https://gcc.gnu.org/viewcvs?rev=277840&root=gcc&view=rev Log: PR 92208 + PR 92277 – GCC 9 follow-up fix PR fortran/92208

[Bug fortran/92208] [9/10 Regression] internal compile error, character array of dynamic length returned from function and passed to subroutine

2019-11-05 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92208 --- Comment #10 from Tobias Burnus --- Author: burnus Date: Tue Nov 5 14:28:07 2019 New Revision: 277840 URL: https://gcc.gnu.org/viewcvs?rev=277840&root=gcc&view=rev Log: PR 92208 + PR 92277 – GCC 9 follow-up fix PR fortran/92208

[Bug fortran/92277] [10 Regression] ICE with assumed rank in gfc_conv_gfc_desc_to_cfi_desc

2019-11-05 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92277 --- Comment #6 from Tobias Burnus --- (In reply to Tobias Burnus from comment #4) > The test case was also added to the GCC 9 branch - where it passes without > requiring a compiler patch. Spoke to early - it was needed for arm and aarch64 as PR

[Bug fortran/91253] [9/10 Regression] gfortran.dg/continuation_6.f fails when using -pre_include as done with latest glibc

2019-11-07 Thread burnus at gcc dot gnu.org
||2019-11-07 CC||burnus at gcc dot gnu.org, ||marxin at gcc dot gnu.org Summary|gfortran.dg/continuation_6. |[9/10 Regression] |f fails when using latest

[Bug fortran/92123] [F2018/array-descriptor] Scalar allocatable/pointer with array descriptor (via bind(C)): ICE with select rank or error scalar variable with POINTER or ALLOCATABLE in procedure wit

2019-11-07 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123 --- Comment #2 from Tobias Burnus --- Submitted and approved patch: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00072.html – still to be committed by the author.

[Bug fortran/91253] [9/10 Regression] gfortran.dg/continuation_6.f fails when using -pre_include as done with latest glibc

2019-11-08 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91253 --- Comment #2 from Tobias Burnus --- Author: burnus Date: Fri Nov 8 08:14:40 2019 New Revision: 277948 URL: https://gcc.gnu.org/viewcvs?rev=277948&root=gcc&view=rev Log: Fortran] PR91253 fix continuation-line handling with -pre_include

[Bug fortran/91253] [9/10 Regression] gfortran.dg/continuation_6.f fails when using -pre_include as done with latest glibc

2019-11-08 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91253 --- Comment #4 from Tobias Burnus --- Author: burnus Date: Fri Nov 8 09:25:40 2019 New Revision: 277957 URL: https://gcc.gnu.org/viewcvs?rev=277957&root=gcc&view=rev Log: Fortran] PR91253 fix continuation-line handling with -pre_include

[Bug fortran/91253] [9/10 Regression] gfortran.dg/continuation_6.f fails when using -pre_include as done with latest glibc

2019-11-08 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91253 Tobias Burnus changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug fortran/92142] CFI_setpointer corrupts descriptor

2019-11-11 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92142 --- Comment #1 from Tobias Burnus --- Author: burnus Date: Mon Nov 11 10:18:14 2019 New Revision: 278048 URL: https://gcc.gnu.org/viewcvs?rev=278048&root=gcc&view=rev Log: PR fortran/92142 - CFI_setpointer corrupts descriptor 2019-11-11 José R

[Bug fortran/92142] CFI_setpointer corrupts descriptor

2019-11-11 Thread burnus at gcc dot gnu.org
||burnus at gcc dot gnu.org Resolution|--- |FIXED --- Comment #2 from Tobias Burnus --- FIXED on the trunk (GCC 10); I think it is neither a regression nor a serious bug (for valid code), hence, it doesn't merit a GCC 9 backport. (But I am ope

[Bug fortran/92142] CFI_setpointer corrupts descriptor

2019-11-11 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92142 --- Comment #3 from Tobias Burnus --- Author: burnus Date: Mon Nov 11 15:35:50 2019 New Revision: 278055 URL: https://gcc.gnu.org/viewcvs?rev=278055&root=gcc&view=rev Log: Fix commit for PR fortran/92142 - CFI_setpointer corrupts descriptor 201

[Bug fortran/92457] [10 Regression] FAIL: gfortran.dg/ISO_Fortran_binding_16.f90

2019-11-11 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92457 Tobias Burnus changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-11 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 Tobias Burnus changed: What|Removed |Added Status|ASSIGNED|NEW --- Comment #7 from Tobias Burnus -

[Bug fortran/92470] New: CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-12 Thread burnus at gcc dot gnu.org
Keywords: wrong-code Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- Mentioned at https://gcc.gnu.org/ml/fortran/2019-11/msg00060.html refers

[Bug fortran/92470] CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92470 --- Comment #1 from Tobias Burnus --- Created attachment 47215 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47215&action=edit Lightly tested patch

[Bug fortran/83118] [7/8/9/10 Regression] Bad intrinsic assignment of class(*) array component of derived type

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug fortran/92123] [F2018/array-descriptor] Scalar allocatable/pointer with array descriptor (via bind(C)): ICE with select rank or error scalar variable with POINTER or ALLOCATABLE in procedure wit

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123 --- Comment #6 from Tobias Burnus --- Some side remarks: (In reply to Jakub Jelinek from comment #5) > The type used on the C side is: This type is described in the Fortran standard; for Fortran 2018, it is described in "18.5.3 The CFI_cdesc_t

[Bug fortran/92470] CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92470 Tobias Burnus changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #8 from Tobias Burnus --- (In reply to Thomas Schwinge from comment #6) > On powerpc64le-unknown-linux-gnu I can reproduce it on a powerpc64le-unknown-linux-gnu w/o real offloading. It fails here for subroutine test_dummy_opt_val_cal

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #9 from Tobias Burnus --- (In reply to Tobias Burnus from comment #8) In gdb [GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.3) 7.7.1], which is really not the newest, I get: (gdb) pt c_aptr type = and stepping in, gives (all variables shoul

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #10 from Tobias Burnus --- The callee is: > and the hidden argument (_c_aptr) is: constant 1> which both look fine.

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #11 from Tobias Burnus --- Optimized dump is: void * c_bptr; void * c_aptr; real(kind=8) * bptr; real(kind=8) bb; real(kind=8) * aptr; real(kind=8) aa; real(kind=8) aa.1_1; real(kind=8) bb.2_2; : aa.1_1 = aa; bb.

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #12 from Tobias Burnus --- Created attachment 47223 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47223&action=edit -fdump-rtl-expand for test case in comment 9, compiled on powerpc64le-unknown-linux-gnu using -O0 (it doesn't f

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 Tobias Burnus changed: What|Removed |Added CC||dje at gcc dot gnu.org,

[Bug fortran/92470] CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92470 --- Comment #3 from Tobias Burnus --- Author: burnus Date: Tue Nov 12 19:33:10 2019 New Revision: 278101 URL: https://gcc.gnu.org/viewcvs?rev=278101&root=gcc&view=rev Log: PR fortran/92470 Fixes for CFI_address libgfortran/ PR f

[Bug fortran/92189] Fortran-written bind(C) function with allocatable argument does not update C descriptor on exit

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92189 --- Comment #2 from Tobias Burnus --- Created attachment 47227 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47227&action=edit Minor cleanup patch for trans-decl.c's convert_CFI_desc I think there many issues: (A) For assumed-shape/assum

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-12 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #14 from Tobias Burnus --- If the actual argument is itself optional but without value attribute, gfc_conv_expr_present returns a 'logical_type_node' (default-integer size, typically 4 bytes type) instead of a boolean_type_node (1 byt

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-13 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #15 from Tobias Burnus --- The mentioned patch (for a related case but not relevant for this bug) is now committed as r278114, see https://gcc.gnu.org/ml/gcc-patches/2019-11/msg00990.html Regarding the issue in this bug: Janne pointe

[Bug fortran/92470] CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-13 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92470 --- Comment #4 from Tobias Burnus --- Author: burnus Date: Wed Nov 13 11:13:57 2019 New Revision: 278128 URL: https://gcc.gnu.org/viewcvs?rev=278128&root=gcc&view=rev Log: PR fortran/92470 Fixes for CFI_address libgfortran/ PR f

[Bug target/91851] [m68k] Convert the backend to MODE_CC so it can be kept in future releases

2019-11-13 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91851 --- Comment #4 from Tobias Burnus --- Bernd posted the CC0-to-MODE_CC patches for review, cf: https://gcc.gnu.org/ml/gcc-patches/2019-11/msg01028.html [0/4] https://gcc.gnu.org/ml/gcc-patches/2019-11/msg01029.html [1/4] https://gcc.gnu.org/ml/gc

[Bug fortran/92470] CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-13 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92470 --- Comment #5 from Tobias Burnus --- Author: burnus Date: Wed Nov 13 15:06:47 2019 New Revision: 278143 URL: https://gcc.gnu.org/viewcvs?rev=278143&root=gcc&view=rev Log: PR fortran/92470 Fixes for CFI_address Backport from mainline

[Bug fortran/92470] CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-13 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92470 Tobias Burnus changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug testsuite/92466] new test case gfortran.dg/ISO_Fortran_binding_15.f90 in r278025 fails

2019-11-13 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92466 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug fortran/92482] BIND(C) with array-descriptor mishandled for type character

2019-11-13 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92482 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org

[Bug testsuite/92500] New testcase gfortran.dg/ISO_Fortran_binding_17.f90 fails (added in r278143)

2019-11-14 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92500 --- Comment #4 from Tobias Burnus --- Author: burnus Date: Thu Nov 14 08:02:42 2019 New Revision: 278201 URL: https://gcc.gnu.org/viewcvs?rev=278201&root=gcc&view=rev Log: Fix gfortran.dg/ISO_Fortran_binding_17.c using rel. #include PR

[Bug fortran/92470] CFI_address wrongly assumes that lower bounds are at zero – invalid for pointers + allocatables

2019-11-14 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92470 --- Comment #7 from Tobias Burnus --- Author: burnus Date: Thu Nov 14 08:02:42 2019 New Revision: 278201 URL: https://gcc.gnu.org/viewcvs?rev=278201&root=gcc&view=rev Log: Fix gfortran.dg/ISO_Fortran_binding_17.c using rel. #include PR

[Bug testsuite/92500] New testcase gfortran.dg/ISO_Fortran_binding_17.f90 fails (added in r278143)

2019-11-14 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92500 Tobias Burnus changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug fortran/92123] [F2018/array-descriptor] Scalar allocatable/pointer with array descriptor (via bind(C)): ICE with select rank or error scalar variable with POINTER or ALLOCATABLE in procedure wit

2019-11-14 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123 --- Comment #12 from Tobias Burnus --- (all related to gcc/testsuite/gfortran.dg/ISO_Fortran_binding_15.f90) I tried - with Paul's attached patch (attachment 47261) DECL_CONTEXT (gfc_desc) = current_function_decl; instead of TREE_STATIC - but

[Bug fortran/92189] Fortran-written bind(C) function with allocatable argument does not update C descriptor on exit

2019-11-14 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92189 --- Comment #3 from Tobias Burnus --- (In reply to Tobias Burnus from comment #2) > (A) For assumed-shape/assumed-rank arrays, there is trans-decl.c's > convert_CFI_desc I wonder if one needs to take care of TREE_THIS_VOLATILE() with any of the

[Bug fortran/92533] New: [F2018] Permit module names in access-stmt (public::/private::)

2019-11-15 Thread burnus at gcc dot gnu.org
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- Fortran 2018 now permits: module A use B private :: B Namely, R827 access-stmt is access-spec

[Bug fortran/92533] [F2018] Permit module names in access-stmt (public::/private::)

2019-11-15 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92533 --- Comment #1 from Tobias Burnus --- Note that one needs to handle: module A; integer, parameter :: A1 = 1, A2 = 2; end module A module B; use A; end module B module C; use A; end module B module D use B use C private private B public

[Bug fortran/92533] [F2018] Permit module names in access-stmt (public::/private::)

2019-11-15 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92533 --- Comment #3 from Tobias Burnus --- NOTE: use, public :: C is not (yet) permitted, but might well be added in the future. See https://github.com/j3-fortran/fortran_proposals/issues/88 and https://mailman.j3-fortran.org/pipermail/j3/2019-Novem

[Bug libgomp/81886] Means to determine at runtime foffload targets specified at compile time

2019-11-18 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81886 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org

[Bug fortran/92568] New: OpenMP 5 - implicit mapping of scalar with TARGET/ALLOCATABLE/POINTER attribute: shall be 'tofrom' mapped

2019-11-18 Thread burnus at gcc dot gnu.org
sion: 10.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target

[Bug middle-end/92463] Cleanups due to minimum MPFR version bump to 3.1.0

2019-11-21 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92463 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug target/91851] [m68k] Convert the backend to MODE_CC so it can be kept in future releases

2019-11-22 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91851 --- Comment #6 from Tobias Burnus --- A seemingly independent conversation to ccmode + lra has been posted by Coerl [I don't know whether he has a FSF copyright assignment] at https://gcc.gnu.org/ml/gcc-patches/2019-11/msg02131.html

[Bug middle-end/92628] New: Make use of TYPE_RESTRICT for function-call pointer-escape analysis – especially for Fortran

2019-11-22 Thread burnus at gcc dot gnu.org
Keywords: missed-optimization Severity: normal Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: burnus at gcc dot gnu.org Target Milestone: --- As discussed, TYPE_RESTRICT should also be used for of pointer

[Bug middle-end/92628] Make use of TYPE_RESTRICT for function-call pointer-escape analysis – especially for Fortran

2019-11-22 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92628 --- Comment #1 from Tobias Burnus --- *** Bug 49733 has been marked as a duplicate of this bug. ***

[Bug middle-end/49733] Missed optimization: Variable value not propagated to remove "if" condition

2019-11-22 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49733 Tobias Burnus changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug tree-optimization/60712] "restrict" qualifier ignored on local variable or after inlining

2019-11-22 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60712 Tobias Burnus changed: What|Removed |Added CC||burnus at gcc dot gnu.org --- Comment

[Bug middle-end/92628] Make use of TYPE_RESTRICT for function-call pointer-escape analysis – especially for Fortran

2019-11-22 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92628 --- Comment #2 from Tobias Burnus --- (In reply to Tobias Burnus from comment #0) > A similar rule applies to other variables in Fortran See also PR 60712 regarding restrict and local variables (as opposed to PARAM_DECL) for a simpler case (no fu

[Bug libgomp/92305] [10 regression] libgomp.fortran/use_device_addr-1.f90 fails starting with r277606

2019-11-22 Thread burnus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92305 --- Comment #16 from Tobias Burnus --- Recap (see comment 11): Callee's arguments are (aa, bb, c_aptr, c_bptr, aptr, bptr, _aa, _bb, _c_aptr, _c_bptr) i.e. 2 real(kind=4)/float variables, 4 pointers and 4 Booleans. And the call is (aa.1_1, bb.

<    1   2   3   4   5   6   7   8   9   10   >