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 tree-optimization/101636] [11/12 Regression] ICE: verify_gimple failed (error: conversion of register to a different size in 'view_convert_expr')
Date: Tue, 03 Aug 2021 13:47:13 +0000	[thread overview]
Message-ID: <bug-101636-4-E9m8ylh2NM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101636-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
> Please bisect with -fno-vect-cost-model then

Doing that, it starts with r11-1450-g8a9e230f41eb4063.

  parent reply	other threads:[~2021-08-03 13:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27  9:15 [Bug tree-optimization/101636] New: " asolokha at gmx dot com
2021-07-27 11:30 ` [Bug tree-optimization/101636] " rguenth at gcc dot gnu.org
2021-07-28  7:07 ` rguenth at gcc dot gnu.org
2021-08-03 12:42 ` marxin at gcc dot gnu.org
2021-08-03 13:06 ` rguenther at suse dot de
2021-08-03 13:47 ` marxin at gcc dot gnu.org [this message]
2021-08-06  9:58 ` rguenth at gcc dot gnu.org
2021-11-08 11:27 ` rguenth at gcc dot gnu.org
2021-11-08 11:43 ` marxin at gcc dot gnu.org
2021-11-08 11:44 ` marxin at gcc dot gnu.org
2021-11-08 12:56 ` rguenther at suse dot de
2021-11-08 15:33 ` marxin at gcc dot gnu.org
2021-11-08 15:33 ` marxin at gcc dot gnu.org
2021-11-09  7:24 ` rguenther at suse dot de
2022-02-22 14:52 ` rguenth at gcc dot gnu.org
2022-02-23  9:21 ` rguenth at gcc dot gnu.org
2022-02-23 11:14 ` cvs-commit at gcc dot gnu.org
2022-02-23 11:15 ` [Bug tree-optimization/101636] [11 " rguenth at gcc dot gnu.org
2022-03-07 11:34 ` rguenth at gcc dot gnu.org
2022-03-23 14:08 ` cvs-commit at gcc dot gnu.org
2022-03-23 14:08 ` rguenth 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-101636-4-E9m8ylh2NM@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).