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/115307] [avr] Don't expand isinf() like a built-in
Date: Sat, 01 Jun 2024 09:12:10 +0000 [thread overview]
Message-ID: <bug-115307-4-plcqjQbAkU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115307-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115307
--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-14 branch has been updated by Georg-Johann Lay
<gjl@gcc.gnu.org>:
https://gcc.gnu.org/g:9d08c55f7c99329f4289ad3a4157c2d8d8a78d8c
commit r14-10266-g9d08c55f7c99329f4289ad3a4157c2d8d8a78d8c
Author: Georg-Johann Lay <avr@gjlay.de>
Date: Sat Jun 1 10:38:00 2024 +0200
AVR: tree-optimization/115307 - Work around isinf bloat from early passes.
PR tree-optimization/115307
gcc/
* config/avr/avr.md (SFDF): New mode iterator.
(isinf<mode>2) [sf, df]: New expanders.
gcc/testsuite/
* gcc.target/avr/torture/pr115307-isinf.c: New test.
(cherry picked from commit fabb545026f714b7d1cbe586f4c5bbf6430bdde3)
next prev parent reply other threads:[~2024-06-01 9:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 13:50 [Bug middle-end/115307] New: " gjl at gcc dot gnu.org
2024-05-31 13:52 ` [Bug middle-end/115307] " gjl at gcc dot gnu.org
2024-05-31 15:49 ` [Bug target/115307] " rguenth at gcc dot gnu.org
2024-06-01 8:54 ` [Bug tree-optimization/115307] " cvs-commit at gcc dot gnu.org
2024-06-01 9:12 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-01 9:14 ` gjl at gcc dot gnu.org
2024-06-01 9:34 ` gjl at gcc dot gnu.org
2024-06-01 11:40 ` cvs-commit at gcc dot gnu.org
2024-06-01 15:21 ` gjl at gcc dot gnu.org
2024-06-03 17:12 ` jsm28 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-115307-4-plcqjQbAkU@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).