From: Nathan Sidwell <nathan@acm.org>
To: "Torbjörn SVENSSON" <torbjorn.svensson@foss.st.com>,
gcc-patches@gcc.gnu.org
Cc: yvan.roux@foss.st.com
Subject: Re: [PATCH v2] c++: Use in-process client when networking is disabled
Date: Thu, 3 Nov 2022 09:13:13 -0400 [thread overview]
Message-ID: <700a9410-c69d-93da-5975-69cae5db33db@acm.org> (raw)
In-Reply-To: <20221103093748.2671754-1-torbjorn.svensson@foss.st.com>
On 11/3/22 05:37, Torbjörn SVENSSON wrote:
> v1 -> v2:
> Updated expression in bad-mapper-3.C
>
> Ok for trunk?
>
> ---
>
> Without the patch, the output for bad-mapper-3.C would be:
>
> /src/gcc/gcc/testsuite/g++.dg/modules/bad-mapper-3.C:2:1: error: unknown Compiled Module Interface: no such module
>
> As this line is unexpected, the test case would fail.
> The same problem can also be seen for g++.dg/modules/bad-mapper-2.C.
>
> gcc/cp/ChangeLog:
>
> * mapper-client.cc: Use in-process client when networking is
> disabled.
>
> gcc/testsuite/ChangeLog:
>
> * g++.dg/modules/bad-mapper-3.C: Update dg-error pattern.
>
> Tested on Windows with arm-none-eabi for Cortex-M3 in gcc-11 tree.
>
> Co-Authored-By: Yvan ROUX <yvan.roux@foss.st.com>
> Signed-off-by: Torbjörn SVENSSON <torbjorn.svensson@foss.st.com>
> ---
> gcc/cp/mapper-client.cc | 4 ++++
> gcc/testsuite/g++.dg/modules/bad-mapper-3.C | 2 +-
> 2 files changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/gcc/cp/mapper-client.cc b/gcc/cp/mapper-client.cc
> index fe9544b5ba4..4dcb3a03660 100644
> --- a/gcc/cp/mapper-client.cc
> +++ b/gcc/cp/mapper-client.cc
> @@ -227,6 +227,8 @@ module_client::open_module_client (location_t loc, const char *o,
> int fd = -1;
> #if CODY_NETWORKING
> fd = Cody::OpenLocal (&errmsg, name.c_str () + 1);
> +#else
> + errmsg = "CODY_NETWORKING disabled";
CODY_NETWORKING is implementor speak. I think just "disabled" is sufficient here?
> #endif
> if (fd >= 0)
> c = new module_client (fd, fd);
> @@ -254,6 +256,8 @@ module_client::open_module_client (location_t loc, const char *o,
> int fd = -1;
> #if CODY_NETWORKING
> fd = Cody::OpenInet6 (&errmsg, name.c_str (), port);
> +#else
> + errmsg = "CODY_NETWORKING disabled";
> #endif
> name[colon] = ':';
>
> diff --git a/gcc/testsuite/g++.dg/modules/bad-mapper-3.C b/gcc/testsuite/g++.dg/modules/bad-mapper-3.C
> index 9dab332ccb2..c91bb4e260c 100644
> --- a/gcc/testsuite/g++.dg/modules/bad-mapper-3.C
> +++ b/gcc/testsuite/g++.dg/modules/bad-mapper-3.C
> @@ -1,6 +1,6 @@
> // { dg-additional-options "-fmodules-ts -fmodule-mapper=localhost:172477262" }
> import unique3.bob;
> -// { dg-error {failed connecting mapper 'localhost:172477262'} "" { target *-*-* } 0 }
> +// { dg-error {failed (connecting|CODY_NETWORKING disabled) mapper 'localhost:172477262'} "" { target *-*-* } 0 }
> // { dg-prune-output "fatal error:" }
> // { dg-prune-output "failed to read" }
> // { dg-prune-output "compilation terminated" }
--
Nathan Sidwell
next prev parent reply other threads:[~2022-11-03 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 9:37 Torbjörn SVENSSON
2022-11-03 13:13 ` Nathan Sidwell [this message]
2022-11-03 13:48 ` Torbjorn SVENSSON
2022-11-03 14:09 ` Nathan Sidwell
2022-11-04 7:57 ` Torbjorn SVENSSON
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=700a9410-c69d-93da-5975-69cae5db33db@acm.org \
--to=nathan@acm.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=torbjorn.svensson@foss.st.com \
--cc=yvan.roux@foss.st.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).