From: Mark Wielaard <mark@klomp.org>
To: jcb62281@gmail.com
Cc: NightStrike <nightstrike@gmail.com>,
Jacek Caban <jacek@codeweavers.com>,
fortran@gcc.gnu.org, Eric Pouech <eric.pouech@orange.fr>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>,
dejagnu@gnu.org
Subject: Re: testsuite under wine
Date: Sat, 24 Dec 2022 12:05:38 +0100 [thread overview]
Message-ID: <Y6bdAuMx13vb+ACc@wildebeest.org> (raw)
In-Reply-To: <63A67964.6080902@gmail.com>
Hi,
On Fri, Dec 23, 2022 at 10:00:36PM -0600, Jacob Bachmeyer via Gcc wrote:
> NightStrike wrote:
> > Rust is getting \r\r\n\n (as opposed to \r\n\r\n), so... yeah. Could
> > be the rust test, could be the rust frontend, could be another weird
> > Wine interaction.
>
> That is probably either a Rust bug or the intended behavior.
Note that in rust a string tokens or doc comments with an "Isolated
CR" (a \r not immediately followed by an \n) is an error and the
testsuite contains a couple of tests to make sure the compiler detects
that. Which might cause even more confusion.
Cheers,
Mark
next prev parent reply other threads:[~2022-12-24 11:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAF1jjLtJW0juQR6L-VybJ8SSaqkfi=qN9FnxJVaY=oQBtkSLxA@mail.gmail.com>
[not found] ` <3f62bac2-ac1b-5c55-2488-ede2389d35d2@netcologne.de>
[not found] ` <CAF1jjLvJU2fnU0u0p9SwPre5mnhFdmv9pm_OvZGOvjQApCROqw@mail.gmail.com>
2022-12-17 10:52 ` Thomas Koenig
2022-12-17 23:24 ` NightStrike
2022-12-18 3:44 ` Jacob Bachmeyer
2022-12-18 21:13 ` NightStrike
2022-12-19 4:29 ` Jacob Bachmeyer
2022-12-19 10:43 ` Torbjorn SVENSSON
2022-12-19 11:00 ` NightStrike
2022-12-19 11:13 ` NightStrike
2022-12-20 3:51 ` Jacob Bachmeyer
[not found] ` <7cb45ab2-cc6e-c502-5592-51ffabcbc6f8@codeweavers.com>
2022-12-22 1:01 ` NightStrike
2022-12-22 4:37 ` Jacob Bachmeyer
2022-12-23 10:36 ` NightStrike
2022-12-23 12:43 ` Eric Pouech
2022-12-24 4:00 ` Jacob Bachmeyer
2022-12-24 11:05 ` Mark Wielaard [this message]
2023-01-05 2:50 ` NightStrike
2023-01-06 3:33 ` Jacob Bachmeyer
2023-01-06 3:44 ` Jerry D
2023-01-08 7:12 ` NightStrike
2023-01-11 2:30 ` Jacob Bachmeyer
2023-01-11 9:33 ` NightStrike
2023-01-12 4:11 ` Jacob Bachmeyer
2023-01-06 3:41 ` Jerry D
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=Y6bdAuMx13vb+ACc@wildebeest.org \
--to=mark@klomp.org \
--cc=dejagnu@gnu.org \
--cc=eric.pouech@orange.fr \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=jacek@codeweavers.com \
--cc=jcb62281@gmail.com \
--cc=nightstrike@gmail.com \
/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).