public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc Glisse <marc.glisse@inria.fr>
To: Kevin Lee <kevinl@rivosinc.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Different outputs in Gimple pass dump generated by two different architectures
Date: Fri, 11 Nov 2022 09:55:27 +0100 (CET)	[thread overview]
Message-ID: <037c79a6-037a-768d-3794-abd065d41831@inria.fr> (raw)
In-Reply-To: <CALkvSf9Vk3N1_NdsQCJWVKwrvT3syMk65h2ZD8jFkNtxjS6w2w@mail.gmail.com>

On Thu, 10 Nov 2022, Kevin Lee wrote:

> While looking at the failure for gcc.dg/uninit-pred-9_b.c, I observed that
> x86-64 and risc-v has a different output for the gimple pass since
> r12-4790-g4b3a325f07acebf4
> <https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=4b3a325f07acebf4>.

Probably since earlier.

> What would be causing the difference? Is this intended? Link 
> <https://godbolt.org/z/eWxnYsK1z> for details. Thank you!

See LOGICAL_OP_NON_SHORT_CIRCUIT in fold-const.cc (and various discussions 
on the topic in mailing lists and bugzilla).

-- 
Marc Glisse

  reply	other threads:[~2022-11-11  8:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  0:05 Kevin Lee
2022-11-11  8:55 ` Marc Glisse [this message]
2022-11-11 16:38   ` Andrew Pinski
2022-11-11 18:51     ` Kevin Lee

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=037c79a6-037a-768d-3794-abd065d41831@inria.fr \
    --to=marc.glisse@inria.fr \
    --cc=gcc@gcc.gnu.org \
    --cc=kevinl@rivosinc.com \
    /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).