From: Patrick Begou <Patrick.Begou@univ-grenoble-alpes.fr>
To: Harald Anlauf <anlauf@gmx.de>,
"fortran@gcc.gnu.org" <fortran@gcc.gnu.org>
Subject: Re: (GCC) 13.0.1: internal compiler error
Date: Mon, 24 Apr 2023 19:39:15 +0200 [thread overview]
Message-ID: <cdf0bd71-3655-5641-8f09-c1cbe0c446fe@univ-grenoble-alpes.fr> (raw)
In-Reply-To: <eb85274f-7f02-63fd-d01b-e6c926ae0660@gmx.de>
Hi Harald
as I said, it is a large, massively parallel fortran code: more than 700
files, some with several thousands of lines. It could be difficult to
create a small reproducer but I will try if the problem is not known as
an other git branch of this code also create an internal error on
another file.
Best regards
Patrick
Le 24/04/2023 à 19:27, Harald Anlauf a écrit :
> Hi Patrick,
>
> I did not see any similar report in bugzilla, so could you please
> open a PR and attach a self-contained reproducer? Ideally the
> reproducer would be reduced to simplify the analysis for those
> familiar with the status of the OpenACC implementation.
>
> Thanks,
> Harald
>
> Am 21.04.23 um 17:13 schrieb Patrick Begou:
>> Hi,
>>
>> I have built this morning the latest gfortran from a git clone:
>>
>> GNU Fortran (GCC) 13.0.1 20230421 (prerelease)
>>
>> I'm trying this compiler on a large and complexe Fortran90 code with
>> offloading using OpenACC.
>>
>> At this time:
>>
>> - code compiles with nvfortran and runs on A100 GPU.
>>
>> - code compiles with Cray Fortran (with some difficulties) but do not
>> run on MI250 GPU (we are tacking the problem, a segfault if openacc is
>> set on)
>>
>> - code compile with GNU GCC 13 without -fopenacc option and runs on cpu
>> (Epyc2 7302)
>>
>> - a basic test-code using OpenACC compiles and run on the GPU.
>>
>> - compiling my large code with gcc 13.0.1 using -fopenacc for A100 GPU
>> produce an internal error in the compiler :
>>
>>
>> transforms_defs_m.f90:354:53:
>>
>> 354 | !$acc enter data attach(atransform2%next)
>> | ^
>> internal compiler error: in omp_group_base, at gimplify.cc:9412
>> 0xa830c6 omp_group_base
>> ../../gcc/gcc/gimplify.cc:9412
>> 0xa830c6 omp_index_mapping_groups_1
>> ../../gcc/gcc/gimplify.cc:9441
>> 0xa833c7 omp_index_mapping_groups
>> ../../gcc/gcc/gimplify.cc:9502
>> 0xa96a9a gimplify_scan_omp_clauses
>> ../../gcc/gcc/gimplify.cc:10802
>> 0xa8660d gimplify_omp_target_update
>> ../../gcc/gcc/gimplify.cc:15563
>> 0xa8660d gimplify_expr(tree_node**, gimple**, gimple**, bool
>> (*)(tree_node*), int)
>> ../../gcc/gcc/gimplify.cc:16928
>> 0xa89826 gimplify_stmt(tree_node**, gimple**)
>> ../../gcc/gcc/gimplify.cc:7219
>> 0xa875a3 gimplify_statement_list
>> ../../gcc/gcc/gimplify.cc:2019
>> 0xa875a3 gimplify_expr(tree_node**, gimple**, gimple**, bool
>> (*)(tree_node*), int)
>> ../../gcc/gcc/gimplify.cc:16821
>> 0xa89826 gimplify_stmt(tree_node**, gimple**)
>> ../../gcc/gcc/gimplify.cc:7219
>> 0xa86e8a gimplify_and_add(tree_node*, gimple**)
>> ../../gcc/gcc/gimplify.cc:492
>> 0xa86e8a gimplify_loop_expr
>> ../../gcc/gcc/gimplify.cc:1993
>> 0xa86e8a gimplify_expr(tree_node**, gimple**, gimple**, bool
>> (*)(tree_node*), int)
>> ../../gcc/gcc/gimplify.cc:16581
>> 0xa89826 gimplify_stmt(tree_node**, gimple**)
>> ../../gcc/gcc/gimplify.cc:7219
>> 0xa875a3 gimplify_statement_list
>> ../../gcc/gcc/gimplify.cc:2019
>> 0xa875a3 gimplify_expr(tree_node**, gimple**, gimple**, bool
>> (*)(tree_node*), int)
>> ../../gcc/gcc/gimplify.cc:16821
>> 0xa89826 gimplify_stmt(tree_node**, gimple**)
>> ../../gcc/gcc/gimplify.cc:7219
>> 0xa89d2b gimplify_bind_expr
>> ../../gcc/gcc/gimplify.cc:1430
>> 0xa86d8e gimplify_expr(tree_node**, gimple**, gimple**, bool
>> (*)(tree_node*), int)
>> ../../gcc/gcc/gimplify.cc:16577
>> 0xa89826 gimplify_stmt(tree_node**, gimple**)
>> ../../gcc/gcc/gimplify.cc:7219
>> Please submit a full bug report, with preprocessed source (by using
>> -freport-bug).
>>
>>
>> Options used (I've just added -fopenacc for moving from cpu version to
>> OpenACC):
>>
>> -fopenacc -freport-bug -g -fpic -x f95-cpp-input -std=gnu -ffree-form
>> -fall-intrinsics -fallow-argument-mismatch -Wall -Wextra -W
>> -Wno-unused-function -Wno-compare-reals -fno-omit-frame-pointer -O3
>> -ftree-vectorize -ffast-math -funroll-loops -pipe
>>
>> No additionnal files a produced with -freport-bug.
>>
>> In attachment the script used to build the compiler.
>>
>> Let me know how I can help with informations to improve Gnu fortran
>> compilers.
>>
>> Patrick
>
next prev parent reply other threads:[~2023-04-24 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-21 15:13 Patrick Begou
2023-04-24 17:27 ` Harald Anlauf
2023-04-24 17:39 ` Patrick Begou [this message]
2023-04-24 18:29 ` Bernhard Reutner-Fischer
2023-04-25 10:41 ` Patrick Begou
2023-04-27 18:36 ` [PATCH] OpenACC: Stand-alone attach/detach clause fixes for Fortran [PR109622] Julian Brown
2023-04-28 8:16 ` Tobias Burnus
2023-04-28 12:56 ` Thomas Schwinge
2023-04-29 10:57 ` [PATCH] OpenACC: Further " Julian Brown
2023-05-02 10:29 ` Tobias Burnus
2023-05-03 12:59 ` Julian Brown
2023-05-03 13:50 ` Tobias Burnus
2023-05-03 11:29 ` Thomas Schwinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cdf0bd71-3655-5641-8f09-c1cbe0c446fe@univ-grenoble-alpes.fr \
--to=patrick.begou@univ-grenoble-alpes.fr \
--cc=anlauf@gmx.de \
--cc=fortran@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).