public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/97292] [11 Regression] dealII from SPECCPU 2016 no longer terminates after g:c34db4b6f8a5d80367c709309f9b00cb32630054
Date: Tue, 06 Oct 2020 08:27:17 +0000	[thread overview]
Message-ID: <bug-97292-4-I5gzxjDfBS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97292-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Created attachment 49314
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49314&action=edit
Debug counter patch

First bad debug counter value is -fdbg-cnt=ipa_mod_ref:2793.
Difference is for: TriaObjectAccessor<3, 3>::operator++():

  LTO stores:
    Limits: 32 bases, 16 refs
      Base 0:struct TriaObjectAccessor (alias set 172)
        Ref 0:int (alias set 6)
          access: Parm 0
          access: Parm 0 param offset:0 offset:0 size:32 max_size:32

  LTO stores:
    Limits: 32 bases, 16 refs
      Base 0:struct TriaObjectAccessor (alias set 172)
        Ref 0:int (alias set 6)
          access: Parm 0 param offset:0 offset:32 size:32 max_size:32
          access: Parm 0 param offset:0 offset:0 size:32 max_size:32

template <int dim>
inline
void
TriaObjectAccessor<3,dim>::operator ++ ()
{
  ++this->present_index;
                                   // is index still in the range of
                                   // the vector?
  while (this->present_index
         >=
        
static_cast<int>(this->tria->levels[this->present_level]->hexes.hexes.size()))
    {
                                       // no -> go one level up
      ++this->present_level;
      this->present_index = 0;
                                       // highest level reached?
      if (this->present_level >= static_cast<int>(this->tria->levels.size()))
        {
                                           // return with past the end pointer
          this->present_level = this->present_index = -1;
          return;
        };
    };
}

hope it helps.

  parent reply	other threads:[~2020-10-06  8:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-05 13:53 [Bug ipa/97292] New: " tnfchris at gcc dot gnu.org
2020-10-06  7:40 ` [Bug ipa/97292] " marxin at gcc dot gnu.org
2020-10-08  8:25   ` Jan Hubicka
2020-10-06  8:27 ` marxin at gcc dot gnu.org [this message]
2020-10-06 16:44 ` hubicka at ucw dot cz
2020-10-07  9:13 ` marxin at gcc dot gnu.org
2020-10-07 11:20 ` rguenth at gcc dot gnu.org
2020-10-08  8:25 ` hubicka at ucw dot cz
2020-10-08 11:38 ` marxin at gcc dot gnu.org
2020-10-08 12:18 ` marxin at gcc dot gnu.org
2020-10-08 12:18 ` marxin at gcc dot gnu.org
2020-10-08 12:23 ` marxin at gcc dot gnu.org
2020-10-08 15:34 ` [Bug ipa/97292] [11 Regression] dealII from SPECCPU 2006 " marxin at gcc dot gnu.org
2020-10-08 15:53 ` tnfchris at gcc dot gnu.org
2020-10-08 17:29 ` hubicka at gcc dot gnu.org
2020-10-08 17:36 ` hubicka at gcc dot gnu.org
2020-10-08 17:44 ` hubicka at gcc dot gnu.org
2020-10-09  7:07 ` marxin at gcc dot gnu.org
2020-10-09  7:31 ` hubicka at gcc dot gnu.org
2020-10-09  7:42 ` marxin at gcc dot gnu.org
2020-10-09 10:27 ` cvs-commit at gcc dot gnu.org
2020-10-09 10:28 ` marxin 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-97292-4-I5gzxjDfBS@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).