From: Bernd Schmidt <bernds_cb1@t-online.de>
To: Mikael Pettersson <mikpelinux@gmail.com>,
Andreas Schwab <schwab@linux-m68k.org>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/4] Eliminate cc0 from m68k
Date: Mon, 18 Nov 2019 19:39:00 -0000 [thread overview]
Message-ID: <962cf853-0809-f6ea-fbf7-48ac161e0cc6@t-online.de> (raw)
In-Reply-To: <CAM43=SM3sAYrchnFUAEMhJCVQDe5+XXk4AooPSAHJ5XzN4hhhQ@mail.gmail.com>
Hi Mikael,
> This fixed the problem, thanks.
Could you also run the testsuite to see if you can reproduce the
g++.old-deja failures Andreas reported?
Bernd
next prev parent reply other threads:[~2019-11-18 19:31 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-17 16:19 Mikael Pettersson
2019-11-17 16:58 ` Andreas Schwab
2019-11-17 18:04 ` Jeff Law
2019-11-17 19:45 ` Mikael Pettersson
2019-11-18 19:39 ` Bernd Schmidt [this message]
2019-11-18 20:57 ` Mikael Pettersson
2019-11-20 13:52 ` Mikael Pettersson
2019-11-20 14:29 ` Bernd Schmidt
2019-11-20 16:59 ` Jeff Law
2019-11-20 20:04 ` Mikael Pettersson
2019-11-20 20:29 ` Jeff Law
2019-11-20 20:50 ` Bernd Schmidt
2019-11-20 22:18 ` Richard Earnshaw
2019-11-21 12:32 ` Matthias Klose
2019-11-21 14:02 ` Bernd Schmidt
2019-11-21 14:36 ` John Paul Adrian Glaubitz
-- strict thread matches above, loose matches on Subject: below --
2019-11-13 13:08 Bernd Schmidt
2019-11-13 18:58 ` Segher Boessenkool
2019-11-13 19:07 ` Bernd Schmidt
2019-11-13 19:25 ` Segher Boessenkool
2019-11-15 13:48 ` John Paul Adrian Glaubitz
2019-11-15 14:36 ` John Paul Adrian Glaubitz
2019-11-13 19:41 ` Jeff Law
2019-11-14 15:00 ` Richard Henderson
2019-11-15 13:49 ` Andreas Schwab
2019-11-15 16:34 ` Bernd Schmidt
2019-11-15 16:36 ` Andreas Schwab
2019-11-15 21:41 ` Bernd Schmidt
2019-11-15 22:21 ` Andreas Schwab
2019-11-15 22:22 ` Bernd Schmidt
2019-11-15 22:57 ` Andreas Schwab
2019-11-16 0:17 ` Bernd Schmidt
2019-11-16 8:26 ` Andreas Schwab
2019-11-16 13:32 ` Bernd Schmidt
2019-11-16 10:47 ` Andreas Schwab
2019-11-16 12:16 ` John Paul Adrian Glaubitz
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=962cf853-0809-f6ea-fbf7-48ac161e0cc6@t-online.de \
--to=bernds_cb1@t-online.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikpelinux@gmail.com \
--cc=schwab@linux-m68k.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).