From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: Jan Hubicka <hubicka@ucw.cz>,
Jan Hubicka via Gcc-patches <gcc-patches@gcc.gnu.org>,
gcc-patches@gcc.gnu.org, rguenther@suse.de
Subject: Re: Unloop no longer looping loops in loop-ch
Date: Tue, 25 Apr 2023 18:04:35 +0200 [thread overview]
Message-ID: <116D73F6-1281-4378-9F26-E4A47DF46775@gmail.com> (raw)
In-Reply-To: <ZEft8nJK6sP93fM+@kam.mff.cuni.cz>
On 25 April 2023 17:12:50 CEST, Jan Hubicka via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
+ fprintf (stderr, "Bingo\n");
You forgot to remove that..
Do we prune Bingo in the testsuite? ;-)
next prev parent reply other threads:[~2023-04-25 16:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 15:12 Jan Hubicka
2023-04-25 16:04 ` Bernhard Reutner-Fischer [this message]
2023-04-25 16:10 ` Jan Hubicka
2023-04-26 7:34 ` Richard Biener
2023-04-26 10:30 ` Jan Hubicka
2023-04-26 12:17 ` Richard Biener
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=116D73F6-1281-4378-9F26-E4A47DF46775@gmail.com \
--to=rep.dot.nop@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=rguenther@suse.de \
/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).