public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/113808] [14 Regression] FAIL: libgomp.fortran/non-rectangular-loop-1.f90
Date: Wed, 07 Feb 2024 13:28:03 +0000	[thread overview]
Message-ID: <bug-113808-4-usYDWuLqwS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113808-4@http.gcc.gnu.org/bugzilla/>

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |14.0
           Keywords|                            |wrong-code
                 CC|                            |tnfchris at gcc dot gnu.org

--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The error must be for the continuation of 'k' to the scalar loop where we have

  <bb 5> [local count: 829590381]:
  MEM <vector(4) integer(kind=4)> [(integer(kind=4) *)&D.4344] =
vect_vec_iv_.27_95;
  vect_k.32_118 = vect_vec_iv_.27_95 + { 1, 1, 1, 1 };
  k.4_23 = k.4_55 + 1; 
  ivtmp_120 = ivtmp_119 + 1;
  if (ivtmp_120 < bnd.23_89)
    goto <bb 15>; [85.44%]
  else
    goto <bb 18>; [14.56%]

  <bb 18> [local count: 136777259]:
  # k.4_45 = PHI <k.4_23(5)>
  # ivtmp_76 = PHI <ivtmp_14(5)>
  # vect_vec_iv_.27_99 = PHI <vect_vec_iv_.27_95(5)>
  # vect__19.29_108 = PHI <{ 0, 1, 2, 3 }(5)>
  _109 = BIT_FIELD_REF <vect__19.29_108, 32, 96>;
  _48 = _109;
  _100 = BIT_FIELD_REF <vect_vec_iv_.27_99, 32, 0>;
  k.4_43 = _100;
  niters_vector_mult_vf.24_90 = bnd.23_89 << 2;
  tmp.26_93 = 53 - niters_vector_mult_vf.24_90;
  _92 = (integer(kind=4)) niters_vector_mult_vf.24_90;
  tmp.25_91 = _92 + 1;
  if (niters.22_12 == niters_vector_mult_vf.24_90)
    goto <bb 6>; [25.00%]
  else
    goto <bb 22>; [75.00%]

  <bb 22> [local count: 136777259]:
  # k.4_74 = PHI <tmp.25_91(18), k.4_78(23)>
  # ivtmp_77 = PHI <tmp.26_93(18), ivtmp_79(23)>

but I can't really see anything wrong here (besides redundant code).

It's possible to elide the middle loop, but I failed to emulate the
inner loop how it's presented without -fopenmp-simd.

  reply	other threads:[~2024-02-07 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 12:47 [Bug tree-optimization/113808] New: " rguenth at gcc dot gnu.org
2024-02-07 13:28 ` rguenth at gcc dot gnu.org [this message]
2024-02-07 13:37 ` [Bug tree-optimization/113808] " tnfchris at gcc dot gnu.org
2024-02-07 13:39 ` [Bug tree-optimization/113808] [14 Regression] FAIL: libgomp.fortran/non-rectangular-loop-1.f90 since r14-8768 jakub at gcc dot gnu.org
2024-02-07 13:48 ` rguenth at gcc dot gnu.org
2024-02-07 13:53 ` rguenth at gcc dot gnu.org
2024-02-07 14:09 ` rguenth at gcc dot gnu.org
2024-02-07 14:20 ` jakub at gcc dot gnu.org
2024-02-07 14:20 ` jakub at gcc dot gnu.org
2024-02-07 14:25 ` rguenth at gcc dot gnu.org
2024-02-08  4:28 ` tnfchris at gcc dot gnu.org
2024-02-08 10:44 ` cvs-commit at gcc dot gnu.org
2024-02-08 10:45 ` tnfchris at gcc dot gnu.org
2024-02-08 11:11 ` cvs-commit 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-113808-4-usYDWuLqwS@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).