public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paul.hua.gm at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/94920] Failure to optimize abs pattern from arithmetic with selected operands based on comparisons with 0
Date: Sat, 06 Aug 2022 08:14:24 +0000 [thread overview]
Message-ID: <bug-94920-4-0Ipv0Y3ylf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94920-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94920
Paul Hua <paul.hua.gm at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |paul.hua.gm at gmail dot com
--- Comment #5 from Paul Hua <paul.hua.gm at gmail dot com> ---
(In reply to CVS Commits from comment #3)
> The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
>
> https://gcc.gnu.org/g:0bc1566dec0cab9410723c96d2ef3280fdab8e8e
>
> commit r13-1854-g0bc1566dec0cab9410723c96d2ef3280fdab8e8e
> Author: Jakub Jelinek <jakub@redhat.com>
> Date: Wed Jul 27 12:02:12 2022 +0200
>
> testsuite: Add -Wno-psabi to pr94920 tests [PR94920]
>
> These tests fail on ia32, because we get -Wpsabi warnings.
> Fixed by adding -Wno-psabi. The pr94920.C test still fails the
> ABS_EXPR scan-tree-dump though, I think we'll need to add vect
> options and use vect_int effective target or something similar.
Yes, we should do. This also fails the ABS_EXPR scan-tree-dump on LoongArch.
>
> 2022-07-27 Jakub Jelinek <jakub@redhat.com>
>
> PR tree-optimization/94920
> * g++.dg/pr94920.C: Add -Wno-psabi to dg-options.
> * g++.dg/pr94920-1.C: Add dg-additional-options -Wno-psabi.
next prev parent reply other threads:[~2022-08-06 8:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 10:53 [Bug tree-optimization/94920] New: " gabravier at gmail dot com
2020-05-04 6:37 ` [Bug tree-optimization/94920] " rguenth at gcc dot gnu.org
2021-08-14 23:58 ` pinskia at gcc dot gnu.org
2022-07-21 21:27 ` cvs-commit at gcc dot gnu.org
2022-07-27 10:04 ` cvs-commit at gcc dot gnu.org
2022-07-27 10:27 ` gabravier at gmail dot com
2022-08-06 8:14 ` paul.hua.gm at gmail dot com [this message]
2022-08-25 22:20 ` pinskia at gcc dot gnu.org
2022-08-25 22:23 ` pinskia at gcc dot gnu.org
2022-10-14 17:56 ` danglin at gcc dot gnu.org
2023-03-04 22:35 ` sandra at gcc dot gnu.org
2023-09-17 16:44 ` 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-94920-4-0Ipv0Y3ylf@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).