public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/102330] [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 since r12-980-g29a2f51806c
Date: Fri, 04 Feb 2022 11:46:33 +0000	[thread overview]
Message-ID: <bug-102330-4-7fxsGuhQZ5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102330-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102330

Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rguenth at gcc dot gnu.org

--- Comment #8 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Posting my current status here, in case anybody feels like verifying my
thoughts.  :-)

So I'm looking into Jakub's last, simplest reproducer:

(In reply to Jakub Jelinek from comment #7)
> program p
>   i = 0
>   !$omp task shared(i)
>   i = 1
>   !$omp end task
>   !$omp taskwait
>   !$acc parallel loop
>   do i = 1, 8
>   end do
> end
> 
> also ICEs

ACK.

> it just needs the iterator that is marked addressable during
> omp-low.c which has code to regimplify statements that access such
> variables, but it seems the problematic stmts are emitted only during
> omp-expand.c.

ACK, 'gcc/omp-expand.cc:expand_oacc_for'.

> The various expand_omp_* loop expansions have DECL_P (...) &&
> TREE_ADDRESSABLE (...) conditions in various spots, but perhaps OpenACC loop
> expansion doesn't.

(Thanks, that has help me with PR104132!)

However, that doesn't seem to be the problem here: we get reported
"non-register as LHS of binary operation", but we've got in
'gcc/omp-expand.cc:expand_oacc_for':

    7868          ass = gimple_build_assign (v, expr);
    (gdb) n
    7869          gsi_insert_before (&gsi, ass, GSI_SAME_STMT);
    (gdb) call debug_gimple_stmt(ass)
    i = 1 + .offset.8;
    (gdb) call debug_tree(v)
     <var_decl 0x7ffff7fc3e10 i
        type <integer_type 0x7ffff75555e8 integer(kind=4) public SI
            size <integer_cst 0x7ffff753ee40 constant 32>
            unit-size <integer_cst 0x7ffff753ee58 constant 4>
            align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff75555e8 precision:32 min <integer_cst 0x7ffff753edf8 -2147483648> max
<integer_cst 0x7ffff753ee10 2147483647>
            pointer_to_this <pointer_type 0x7ffff755da80>>
        used SI
source-gcc/gcc/testsuite/gfortran.dg/goacc-gomp/pr102330-3.f90:9:3 size
<integer_cst 0x7ffff753ee40 32> unit-size <integer_cst 0x7ffff753ee58 4>
        align:32 warn_if_not_align:0 context <function_decl 0x7ffff7730d00 p>>
    (gdb) call is_gimple_lvalue(v)
    $4 = true
    (gdb) call is_gimple_reg(v)
    $5 = true
    (gdb) print v.base.addressable_flag 
    $6 = 0

So, 'i' is not 'TREE_ADDRESSABLE'.

Is the problem rather, that we earlier have done wrong, as Richard pointed out:

(In reply to Richard Biener from comment #1)
> Confirmed.  omp expansion seems to introudce this non-gimple code and likely also makes 'i' not a register (for OACC):
> 
>   .data_dep.5D.4044 = .UNIQUE (OACC_PRIVATE, .data_dep.5D.4044, -1, &iD.4045);

That's built in 'gcc/omp-low.cc:lower_oacc_private_marker'.  It's not marked
'TREE_ADDRESSABLE' (per debug log above), but the address of 'i' has been taken
(here).

> but
> 
>   iD.4045 = 1 + .offset.9D.4049;
> 
> and
> 
>   iD.4045 = 1 + 8;
> 
> (which is also unfolded)

Assuming 'TREE_ADDRESSABLE', that last item is resolved via my proposed
PR104132 change:

    [...]
    +gimple_simplified to D.4257 = 9;
    [...]
    -  iD.4257 = 1 + 8;
    +  D.4266 = 9;
    +  iD.4259 = D.4266;
    [...]

So if in 'gcc/omp-expand.cc:expand_oacc_for' I force 'TREE_ADDRESSABLE', then
the ICE goes away, and we get valid GIMPLE generated, per my understanding.

So, something like this maybe (untested)?  

    --- gcc/omp-low.cc
    +++ gcc/omp-low.cc
    @@ -11513,6 +11513,7 @@ lower_oacc_private_marker (omp_context *ctx)
            }
           gcc_checking_assert (decl);

    +      TREE_ADDRESSABLE (decl) = 1;
           tree addr = build_fold_addr_expr (decl);
           args.safe_push (addr);
         }

However: given that the '#pragma acc loop' has an implicit 'private(i)' -- why
does the 'gcc/omp-expand.cc:expand_oacc_for' even bother about the "outer 'i'"?
 The loop variable 'i' should be a completely separate, local, register-like
temporary.  Amy I misunderstanding something, or what's going wrong, elsewhere?

  parent reply	other threads:[~2022-02-04 11:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-14 17:27 [Bug fortran/102330] New: [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 gscfq@t-online.de
2021-09-15  8:00 ` [Bug fortran/102330] " rguenth at gcc dot gnu.org
2021-09-15  8:00 ` rguenth at gcc dot gnu.org
2021-09-15  8:01 ` rguenth at gcc dot gnu.org
2021-09-15  8:50 ` [Bug fortran/102330] [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 since r12-1139-gf6bf436d9ab907d0 marxin at gcc dot gnu.org
2021-09-15  9:04 ` jakub at gcc dot gnu.org
2021-09-15 10:27 ` tschwinge at gcc dot gnu.org
2021-09-15 10:32 ` [Bug fortran/102330] [12 Regression] ICE in expand_gimple_stmt_1, at cfgexpand.c:3932 since r12-980-g29a2f51806c burnus at gcc dot gnu.org
2021-09-15 10:41 ` jakub at gcc dot gnu.org
2022-01-17 13:30 ` rguenth at gcc dot gnu.org
2022-01-17 16:15 ` tschwinge at gcc dot gnu.org
2022-02-04 11:46 ` tschwinge at gcc dot gnu.org [this message]
2022-02-04 12:03 ` jakub at gcc dot gnu.org
2022-02-04 12:06 ` jakub at gcc dot gnu.org
2022-02-11 13:42 ` tschwinge at gcc dot gnu.org
2022-03-10 11:07 ` cvs-commit at gcc dot gnu.org
2022-03-10 11:07 ` cvs-commit at gcc dot gnu.org
2022-03-10 11:31 ` [Bug middle-end/102330] " tschwinge at gcc dot gnu.org

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=bug-102330-4-7fxsGuhQZ5@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).