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

On Fri, Nov 11, 2022 at 12:57 AM Marc Glisse via Gcc <gcc@gcc.gnu.org> wrote:
>
> 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).

I filed https://gcc.gnu.org/PR107642 to cover the issues around
LOGICAL_OP_NON_SHORT_CIRCUIT and BRANCH_COST.
I hope to get some time in the GCC 14 timeframe to flush out some of
these target macro/hooks issue where the
definitions are not so clear.

Thanks,
Andrew

>
> --
> Marc Glisse

  reply	other threads:[~2022-11-11 16:39 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
2022-11-11 16:38   ` Andrew Pinski [this message]
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='CA+=Sn1=KGiO6rF_HQFc8dra8FYcBAc7zu01XyXOGiDx3E3qqeA@mail.gmail.com' \
    --to=pinskia@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=kevinl@rivosinc.com \
    --cc=marc.glisse@inria.fr \
    /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).