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/113010] [RISCV] sign-extension lost in comparison with constant embedded in comma-op expression
Date: Wed, 24 Jan 2024 21:47:38 +0000	[thread overview]
Message-ID: <bug-113010-4-y8DYjyuayI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113010-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Patrick O'Neill from comment #8)
> From the CI run here:
> https://patchwork.sourceware.org/project/gcc/patch/20240116221914.267015-1-
> gkm@rivosinc.com/
> 
> It looks like this issue also affects ARM since the testcase fails.

That is aarch32 (a ILP32 target) where long is the same size as int. I suspect
you will end up with a failure even on i386 (32bit) with the current testcase.

I suspect you want to use either 0xffffffffull or limit it to `sizeof(long) >
sizeof(int)` targets.

  parent reply	other threads:[~2024-01-24 21:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 21:55 [Bug target/113010] New: " gkm at rivosinc dot com
2023-12-13 22:06 ` [Bug target/113010] " pinskia at gcc dot gnu.org
2024-01-04  1:55 ` patrick at rivosinc dot com
2024-01-09 21:56 ` gkm at rivosinc dot com
2024-01-09 22:05 ` pinskia at gcc dot gnu.org
2024-01-09 22:12 ` pinskia at gcc dot gnu.org
2024-01-09 22:12 ` pinskia at gcc dot gnu.org
2024-01-11  2:45 ` gkm at rivosinc dot com
2024-01-11  2:50 ` gkm at rivosinc dot com
2024-01-24 21:33 ` patrick at rivosinc dot com
2024-01-24 21:47 ` pinskia at gcc dot gnu.org [this message]
2024-03-03 21:50 ` cvs-commit at gcc dot gnu.org
2024-03-03 21:53 ` law at gcc dot gnu.org
2024-03-04 18:24 ` 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-113010-4-y8DYjyuayI@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).