public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112494] ICE in ix86_cc_mode, at config/i386/i386.cc:16477
Date: Mon, 13 Nov 2023 09:59:04 +0000	[thread overview]
Message-ID: <bug-112494-4-VI4kdF8vas@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112494-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Uroš Bizjak <ubizjak at gmail dot com> ---
Now we have:

#1  0x000000000286a3aa in try_combine (i3=0x7fffe3c18100, i2=0x7fffe3c18000,
i1=0x0, i0=0x0, new_direct_jump_p=0x7fffffffd8eb, 
    last_combined_insn=0x7fffe3c18100) at ../../git/gcc/gcc/combine.cc:3207
3207                    = SELECT_CC_MODE (compare_code, op0, op1);
(gdb) p compare_code
$1 = UNSPEC

compare_code = UNSPEC won't fly...

  parent reply	other threads:[~2023-11-13  9:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-12 14:25 [Bug c/112494] New: GCC: 14: internal compiler error: " 141242068 at smail dot nju.edu.cn
2023-11-12 20:57 ` [Bug rtl-optimization/112494] " ubizjak at gmail dot com
2023-11-12 21:12 ` [Bug rtl-optimization/112494] ICE " pinskia at gcc dot gnu.org
2023-11-13  7:57 ` pinskia at gcc dot gnu.org
2023-11-13  8:50 ` ubizjak at gmail dot com
2023-11-13  8:52 ` [Bug target/112494] " ubizjak at gmail dot com
2023-11-13  9:54 ` ubizjak at gmail dot com
2023-11-13  9:59 ` ubizjak at gmail dot com [this message]
2023-11-13 10:51 ` ubizjak at gmail dot com
2023-11-13 21:47 ` cvs-commit at gcc dot gnu.org
2023-11-28 15:57 ` cvs-commit at gcc dot gnu.org
2023-11-28 16:00 ` ubizjak at gmail dot com

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-112494-4-VI4kdF8vas@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).