public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: <gcc-patches@gcc.gnu.org>
Cc: <nathan@acm.org>, <yvan.roux@foss.st.com>
Subject: PING [PATCH v3] c++: Allow module name to be a single letter on Windows
Date: Fri, 25 Nov 2022 20:03:05 +0100	[thread overview]
Message-ID: <0a727ec2-e385-f23b-f6a6-b415d1688b51@foss.st.com> (raw)
In-Reply-To: <20221117132021.1143935-1-torbjorn.svensson@foss.st.com>

Hi,

Ping, https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606528.html

Kind regards,
Torbjörn

On 2022-11-17 14:20, Torbjörn SVENSSON wrote:
> v1 -> v2:
> Paths without "C:" part can still be absolute if they start with / or
> \ on Windows.
> 
> v2 -> v3:
> Use alternative approach by having platform specific code in module.cc.
> 
> Truth table for the new expression:
> c:\foo     -> true
> c:/foo     -> true
> /foo       -> true
> \foo       -> true
> c:foo      -> false
> foo        -> false
> ./foo      -> true
> .\foo      -> true
> 
> 
> Ok for trunk?
> 
> ---
> 
> On Windows, the ':' character is special and when the module name is
> a single character, like 'A', then the flatname would be (for
> example) 'A:Foo'. On Windows, 'A:Foo' is treated as an absolute
> path by the module loader and is likely not found.
> 
> Without this patch, the test case pr98944_c.C fails with:
> 
> In module imported at /src/gcc/testsuite/g++.dg/modules/pr98944_b.C:7:1,
> of module A:Foo, imported at /src/gcc/testsuite/g++.dg/modules/pr98944_c.C:7:
> A:Internals: error: header module expected, module 'A:Internals' found
> A:Internals: error: failed to read compiled module: Bad file data
> A:Internals: note: compiled module file is 'gcm.cache/A-Internals.gcm'
> In module imported at /src/gcc/testsuite/g++.dg/modules/pr98944_c.C:7:8:
> A:Foo: error: failed to read compiled module: Bad import dependency
> A:Foo: note: compiled module file is 'gcm.cache/A-Foo.gcm'
> A:Foo: fatal error: returning to the gate for a mechanical issue
> compilation terminated.
> 
> gcc/cp/ChangeLog:
> 
> 	* module.cc: On Windows, 'A:Foo' is supposed to be a module
> 	and not a path.
> 
> 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/module.cc | 10 +++++++++-
>   1 file changed, 9 insertions(+), 1 deletion(-)
> 
> diff --git a/gcc/cp/module.cc b/gcc/cp/module.cc
> index 0e9af318ba4..fa41a86213f 100644
> --- a/gcc/cp/module.cc
> +++ b/gcc/cp/module.cc
> @@ -13960,7 +13960,15 @@ get_module (tree name, module_state *parent, bool partition)
>   static module_state *
>   get_module (const char *ptr)
>   {
> -  if (ptr[0] == '.' ? IS_DIR_SEPARATOR (ptr[1]) : IS_ABSOLUTE_PATH (ptr))
> +  /* On DOS based file systems, there is an ambiguity with A:B which can be
> +     interpreted as a module Module:Partition or Drive:PATH.  Interpret strings
> +     which clearly starts as pathnames as header-names and everything else is
> +     treated as a (possibly malformed) named moduled.  */
> +  if (IS_DIR_SEPARATOR (ptr[ptr[0] == '.']) // ./FOO or /FOO
> +#if HAVE_DOS_BASED_FILE_SYSTEM
> +      || (HAS_DRIVE_SPEC (ptr) && IS_DIR_SEPARATOR (ptr[2])) // A:/FOO
> +#endif
> +      || false)
>       /* A header name.  */
>       return get_module (build_string (strlen (ptr), ptr));
>   

  reply	other threads:[~2022-11-25 19:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 13:20 Torbjörn SVENSSON
2022-11-25 19:03 ` Torbjorn SVENSSON [this message]
2022-11-28 11:21   ` PING " Nathan Sidwell
2022-11-28 15:50     ` 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=0a727ec2-e385-f23b-f6a6-b415d1688b51@foss.st.com \
    --to=torbjorn.svensson@foss.st.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nathan@acm.org \
    --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).