public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112505] [12/13/14 Regression]  internal compiler error: in build_vector_from_val, at tree.cc:2104
Date: Mon, 13 Nov 2023 06:10:02 +0000	[thread overview]
Message-ID: <bug-112505-4-AkWZONcjhH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112505-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      Known to work|                            |11.1.0, 11.4.0
           Keywords|                            |ice-on-valid-code,
                   |                            |needs-bisection
     Ever confirmed|0                           |1
      Known to fail|                            |12.1.0
   Target Milestone|---                         |12.4
            Summary|GCC: 14: internal compiler  |[12/13/14 Regression]
                   |error: in                   |internal compiler error: in
                   |build_vector_from_val, at   |build_vector_from_val, at
                   |tree.cc:2104                |tree.cc:2104
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2023-11-13
          Component|c                           |tree-optimization

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Simplier testcase:
```
short int w9;
struct T {
  short a : 14;
  int b;
};
struct T v;
void zc() {
        for(int i = 0; i < 4; i ++)
  w9 *= v.b ? v.a-- < 0 : 0;
}
```
Just compiler at `-O3 -fno-vect-cost-model`

  <unnamed-unsigned:14> _30;
  vector(4) unsigned short _31;
...
  _31 = {_60, _59, _2, _30};
  _52 = (vector(4) signed short) _31;

  reply	other threads:[~2023-11-13  6:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-13  3:45 [Bug c/112505] New: GCC: 14: " 141242068 at smail dot nju.edu.cn
2023-11-13  6:10 ` pinskia at gcc dot gnu.org [this message]
2023-11-13  6:11 ` [Bug tree-optimization/112505] [12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-11-13  9:32 ` rguenth at gcc dot gnu.org
2023-12-07  9:53 ` [Bug tree-optimization/112505] [11/12/13/14 Regression] internal compiler error: in build_vector_from_val, at tree.cc:2104 since r10-4076 jakub at gcc dot gnu.org
2024-01-11 13:08 ` rguenth at gcc dot gnu.org
2024-01-11 14:13 ` cvs-commit at gcc dot gnu.org
2024-02-06 13:20 ` [Bug tree-optimization/112505] [11/12/13 " cvs-commit at gcc dot gnu.org
2024-05-17 11:12 ` [Bug tree-optimization/112505] [11/12 " 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-112505-4-AkWZONcjhH@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).