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 target/111260] arm: ice in maybe_legitimize_operand, at optabs.cc:8054
Date: Fri, 06 Oct 2023 05:04:29 +0000	[thread overview]
Message-ID: <bug-111260-4-S6nXcKW7nh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111260-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Zdenek Sojka from comment #2)
> Different testcase:
> $ cat testcase.c
> long
> bar (long x)
> {
>   x *= x == 0 / 0;
>   return (x);
> }
> 
> long
> foo (void)
> {
>   return bar (822920);
> }
> 
> $ aarch64-unknown-linux-gnu-gcc -O testcase.c 
> testcase.c: In function 'bar':
> testcase.c:4:15: warning: division by zero [-Wdiv-by-zero]
>     4 |   x *= x == 0 / 0;
>       |               ^
> during RTL pass: expand
> testcase.c: In function 'foo':
> testcase.c:11:10: internal compiler error: in maybe_legitimize_operand, at
> optabs.cc:8046
>    11 |   return bar (822920);
>       |          ^~~~~~~~~~~~
> 0x7ff794 maybe_legitimize_operand
>         /repo/gcc-trunk/gcc/optabs.cc:8046
> 0x7ff794 maybe_legitimize_operands(insn_code, unsigned int, unsigned int,
> expand_operand*)
>         /repo/gcc-trunk/gcc/optabs.cc:8194
> ...

That is 100% a different bug and should be filed separately.

  parent reply	other threads:[~2023-10-06  5:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-31 18:48 [Bug target/111260] New: " dcb314 at hotmail dot com
2023-09-01  8:09 ` [Bug target/111260] " dcb314 at hotmail dot com
2023-10-06  4:52 ` zsojka at seznam dot cz
2023-10-06  5:04 ` pinskia at gcc dot gnu.org [this message]
2023-10-06  5:09 ` zsojka at seznam dot cz
2023-10-06  8:45 ` [Bug middle-end/111260] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-06  8:48 ` pinskia at gcc dot gnu.org
2023-10-06  8:48 ` pinskia at gcc dot gnu.org
2023-10-06  8:51 ` pinskia at gcc dot gnu.org
2023-10-06  8:53 ` pinskia at gcc dot gnu.org
2023-10-17 12:29 ` [Bug target/111260] [14 Regression] arm/aarch64: " rguenth at gcc dot gnu.org
2023-10-17 16:00 ` [Bug middle-end/111260] [14 Regression] arm/aarch64: ice in maybe_legitimize_operand with ?: and constants and different types since r14-2667-gceae1400cf24f329393e96dd9720 pinskia at gcc dot gnu.org
2023-12-13  6:00 ` pinskia at gcc dot gnu.org
2023-12-13 16:52 ` pinskia at gcc dot gnu.org
2023-12-14 21:39 ` cvs-commit at gcc dot gnu.org
2023-12-14 21:39 ` pinskia 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-111260-4-S6nXcKW7nh@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).