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 middle-end/97357] [10 Regression] Unable to coalesce ssa_names which are marked as MUST COALESCE. Date: Mon, 12 Oct 2020 14:09:25 +0000 [thread overview] Message-ID: <bug-97357-4-dqX9ygY2a5@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97357-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97357 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Christophe Lyon <clyon@gcc.gnu.org>: https://gcc.gnu.org/g:f10f11eb63b0ed082674d9a589e67230aa49efb5 commit r11-3824-gf10f11eb63b0ed082674d9a589e67230aa49efb5 Author: Christophe Lyon <christophe.lyon@linaro.org> Date: Mon Oct 12 14:04:06 2020 +0000 tree-optimization/97357: Fix testcase Calling _setjmp causing a warning when targeting newlib. 2020-10-12 Christophe Lyon <christophe.lyon@linaro.org> gcc/testsuite/ PR tree-optimization/97357 * gcc.dg/pr97357.c: Call setjmp instead of _setjmp.
next prev parent reply other threads:[~2020-10-12 14:09 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-09 16:33 [Bug middle-end/97357] New: " qinzhao at gcc dot gnu.org 2020-10-09 16:35 ` [Bug middle-end/97357] " qinzhao at gcc dot gnu.org 2020-10-12 6:23 ` [Bug middle-end/97357] [10 Regression] " rguenth at gcc dot gnu.org 2020-10-12 7:11 ` marxin at gcc dot gnu.org 2020-10-12 8:27 ` cvs-commit at gcc dot gnu.org 2020-10-12 8:28 ` cvs-commit at gcc dot gnu.org 2020-10-12 8:28 ` rguenth at gcc dot gnu.org 2020-10-12 14:09 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-12 14:12 ` cvs-commit at gcc dot gnu.org 2020-10-12 16:56 ` qinzhao 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-97357-4-dqX9ygY2a5@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: linkBe 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).