public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/104992] [missed optimization] x / y * y == x not optimized to x % y == 0
Date: Thu, 11 Aug 2022 08:29:47 +0000 [thread overview]
Message-ID: <bug-104992-4-qFchAAYdDK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104992-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104992
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:
https://gcc.gnu.org/g:8e69f2a6e91b7a01619dfd3b0788bfda4ad28941
commit r13-2018-g8e69f2a6e91b7a01619dfd3b0788bfda4ad28941
Author: Jakub Jelinek <jakub@redhat.com>
Date: Thu Aug 11 10:26:32 2022 +0200
testsuite: Fix up pr104992* tests on i686-linux [PR104992]
These 2 tests were FAILing on i686-linux or e.g. with
--target_board=unix/-m32/-mno-sse on x86_64-linux due to
-Wpsabi warnings and also because dg-options in the latter
test has been ignored due to missing space, so even -O2
wasn't passed at all.
2022-08-11 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/104992
* gcc.dg/pr104992.c: Add -Wno-psabi to dg-options.
* g++.dg/pr104992-1.C: Likewise. Add space between " and } in
dg-options.
next prev parent reply other threads:[~2022-08-11 8:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 15:19 [Bug tree-optimization/104992] New: " tilkax at gmail dot com
2022-03-20 20:25 ` [Bug tree-optimization/104992] " pinskia at gcc dot gnu.org
2022-03-21 9:37 ` rguenth at gcc dot gnu.org
2022-08-01 13:24 ` cvs-commit at gcc dot gnu.org
2022-08-03 16:00 ` seurer at gcc dot gnu.org
2022-08-11 8:29 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-23 12:12 ` xry111 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-104992-4-qFchAAYdDK@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).