From: Ken Matsui <kmatsui@cs.washington.edu>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Ken Matsui <kmatsui@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: Re: [PATCH v2 2/2] libstdc++: Use using instead of typedef in opts-common.h
Date: Thu, 11 Jan 2024 02:10:02 -0800 [thread overview]
Message-ID: <dhrevx7vung4brsaekngtriqt4gnurxgajavmp4nr3y6u6cbzf@jgcysdcm3cr6> (raw)
In-Reply-To: <CAH6eHdT0wYmxes6JH9wyBtdE73xQ-Rr32=7cAJ+jRUtXsPAwmA@mail.gmail.com>
On Thu, 11 Jan 2024 at 09:55, Jonathan Wakely <jwakely.gcc@gmail.com> wrote:
> On Thu, 11 Jan 2024, 09:43 Ken Matsui, <[1]kmatsui@gcc.gnu.org> wrote:
>
> > libstdc++-v3/ChangeLog:
>
> > * src/filesystem/ops-common.h (stat_type): Use using.
>
> > Signed-off-by: Ken Matsui <[2]kmatsui@gcc.gnu.org>
> > ---
> > libstdc++-v3/src/filesystem/ops-common.h | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
>
> > diff --git a/libstdc++-v3/src/filesystem/ops-common.h
> > b/libstdc++-v3/src/filesystem/ops-common.h
> > index d78a54754c2..e302d8caae6 100644
> > --- a/libstdc++-v3/src/filesystem/ops-common.h
> > +++ b/libstdc++-v3/src/filesystem/ops-common.h
> > @@ -118,7 +118,7 @@ namespace __gnu_posix
> > inline int close(int fd)
> > { return ::_close(fd); }
>
> > - typedef struct ::__stat64 stat_type;
> > + using stat_type = struct ::_stat64;
>
> You've removed an underscore, is that intentional? Has this been compiled
> + tested with mingw?
This is totally unintentional. I'll fix it. I've tested it with Linux
and do not have a mingw environment to test it with. Would you have any
suggestions on how to test it?
>
> > inline int stat(const wchar_t* path, stat_type* buffer)
> > { return ::_wstat64(path, buffer); }
> > @@ -184,7 +184,7 @@ namespace __gnu_posix
> > using ::open;
> > using ::close;
> > # ifdef _GLIBCXX_HAVE_SYS_STAT_H
> > - typedef struct ::stat stat_type;
> > + using stat_type = struct ::stat;
> > using ::stat;
> > # ifdef _GLIBCXX_USE_LSTAT
> > using ::lstat;
> > --
> > 2.43.0
>
> References
>
> Visible links
> 1. mailto:kmatsui@gcc.gnu.org
> 2. mailto:kmatsui@gcc.gnu.org
--
Ken Matsui
next prev parent reply other threads:[~2024-01-11 10:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-11 6:22 [PATCH] libstdc++: Fix error handling for std::filesystem::equivalent [PR113250] Ken Matsui
2024-01-11 9:40 ` [PATCH v2 1/2] libstdc++: Fix error handling in filesystem::equivalent [PR113250] Ken Matsui
2024-01-11 9:40 ` [PATCH v2 2/2] libstdc++: Use using instead of typedef in opts-common.h Ken Matsui
2024-01-11 9:55 ` Jonathan Wakely
2024-01-11 10:10 ` Ken Matsui [this message]
2024-01-11 10:50 ` Jonathan Wakely
2024-01-11 11:28 ` Ken Matsui
2024-01-11 12:01 ` Jonathan Wakely
2024-01-11 12:18 ` Ken Matsui
2024-01-11 12:01 ` Jonathan Wakely
2024-01-11 12:19 ` Ken Matsui
2024-01-11 10:12 ` [PATCH v3 " Ken Matsui
2024-01-11 10:46 ` [PATCH v2 1/2] libstdc++: Fix error handling in filesystem::equivalent [PR113250] Jonathan Wakely
2024-01-11 10:55 ` Ken Matsui
2024-01-11 11:14 ` Backporting [was Re: [PATCH v2 1/2] libstdc++: Fix error handling in filesystem::equivalent [PR113250]] Jonathan Wakely
2024-01-11 11:45 ` Ken Matsui
2024-01-11 12:22 ` Ken Matsui
2024-01-11 12:26 ` Jonathan Wakely
2024-01-11 12:35 ` Ken Matsui
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=dhrevx7vung4brsaekngtriqt4gnurxgajavmp4nr3y6u6cbzf@jgcysdcm3cr6 \
--to=kmatsui@cs.washington.edu \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=kmatsui@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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).