public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104676] [12 Regression] ICE in verify_loop_structure, at cfgloop.cc:1748 (error: loop 3's number of iterations '(unsigned int) + 4294967295' references the released SSA name '<unknown>')
Date: Thu, 28 Apr 2022 03:23:05 +0000	[thread overview]
Message-ID: <bug-104676-4-WjC0McBJwb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104676-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kito Cheng <kito@gcc.gnu.org>:

https://gcc.gnu.org/g:d5b66a905322262483af5c4ca6cb6676c24e1f3f

commit r12-8295-gd5b66a905322262483af5c4ca6cb6676c24e1f3f
Author: Jia-Wei Chen <jiawei@iscas.ac.cn>
Date:   Tue Apr 19 11:11:24 2022 +0800

    testsuite: Skip target not support -pthread [PR104676].

    The "ftree-parallelize-loops=" imply -pthread option in gcc/gcc.cc,
    some target are not support pthread like elf target use newlib,
    and will get an error:

    "*-*-elf-gcc: error: unrecognized command-line option '-pthread'"

    so we add an additional condition "{target pthread}" to make sure the
    dg-additional-options runs on support targets.

    gcc/testsuite/ChangeLog

            PR target/104676
            * gcc.dg/torture/pr104676.c: Add "{target pthread}" check.

      parent reply	other threads:[~2022-04-28  3:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-24 12:48 [Bug tree-optimization/104676] New: " asolokha at gmx dot com
2022-02-24 13:24 ` [Bug tree-optimization/104676] " jakub at gcc dot gnu.org
2022-02-24 13:25 ` rguenth at gcc dot gnu.org
2022-02-24 13:33 ` rguenth at gcc dot gnu.org
2022-02-24 14:58 ` cvs-commit at gcc dot gnu.org
2022-02-24 14:58 ` rguenth at gcc dot gnu.org
2022-04-28  3:23 ` cvs-commit at gcc dot gnu.org [this message]

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-104676-4-WjC0McBJwb@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).