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 rtl-optimization/105459] [12/13 Regression] ICE: Segmentation fault (in record_operand_costs) since r12-3721-g63c6446f77b9001d
Date: Mon, 11 Jul 2022 09:22:18 +0000 [thread overview]
Message-ID: <bug-105459-4-GcovhLZ6v6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105459-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105459
--- Comment #13 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Richard Biener <rguenth@gcc.gnu.org>:
https://gcc.gnu.org/g:4c94382a132a4b2b9d020806549a006fa6764d1b
commit r13-1600-g4c94382a132a4b2b9d020806549a006fa6764d1b
Author: Richard Biener <rguenther@suse.de>
Date: Fri Jul 1 14:11:35 2022 +0200
target/105459 - allow delayed target option node fixup
The following avoids the need to massage the target optimization
node at WPA time when we fixup the optimization node, copying
FP related flags from callee to caller. The target is already
set up to fixup, but that only works when not switching between
functions. After fixing that the fixup is then done at LTRANS
time when materializing the function.
2022-07-01 Richard Biener <rguenthert@suse.de>
PR target/105459
* config/i386/i386-options.cc (ix86_set_current_function):
Rebuild the target optimization node whenever necessary,
not only when the optimization node didn't change.
* gcc.dg/lto/pr105459_0.c: New testcase.
next prev parent reply other threads:[~2022-07-11 9:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 5:24 [Bug rtl-optimization/105459] New: ICE: Segmentation fault (in record_operand_costs) asolokha at gmx dot com
2022-05-03 7:07 ` [Bug rtl-optimization/105459] " rguenth at gcc dot gnu.org
2022-05-03 8:46 ` [Bug rtl-optimization/105459] [12/13 Regression] ICE: Segmentation fault (in record_operand_costs) since r12-3721-g63c6446f77b9001d marxin at gcc dot gnu.org
2022-05-03 8:47 ` marxin at gcc dot gnu.org
2022-05-03 9:00 ` rguenth at gcc dot gnu.org
2022-05-05 5:45 ` linkw at gcc dot gnu.org
2022-05-06 8:33 ` jakub at gcc dot gnu.org
2022-05-17 9:08 ` linkw at gcc dot gnu.org
2022-05-17 9:10 ` linkw at gcc dot gnu.org
2022-05-23 6:28 ` linkw at gcc dot gnu.org
2022-05-23 8:14 ` linkw at gcc dot gnu.org
2022-05-25 7:43 ` linkw at gcc dot gnu.org
2022-06-02 2:15 ` linkw at gcc dot gnu.org
2022-06-02 2:18 ` linkw at gcc dot gnu.org
2022-07-11 9:22 ` cvs-commit at gcc dot gnu.org [this message]
2022-07-11 9:22 ` [Bug rtl-optimization/105459] [12 " rguenth at gcc dot gnu.org
2022-07-19 11:37 ` cvs-commit at gcc dot gnu.org
2022-07-19 11:38 ` rguenth 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-105459-4-GcovhLZ6v6@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).