From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Tom Tromey <tom@tromey.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH RFC 4/5] Introduce scoped_mmapped_file
Date: Sat, 12 May 2018 15:49:00 -0000 [thread overview]
Message-ID: <878t8p4jif.fsf@tromey.com> (raw)
In-Reply-To: <1601635db4edc8926dfcf2a82db65c3e@polymtl.ca> (Simon Marchi's message of "Thu, 10 May 2018 17:10:44 -0400")
>>>>> "Simon" == Simon Marchi <simon.marchi@polymtl.ca> writes:
>> ... however, then I thought perhaps this question could be avoided by
>> just initializing m_fd directly, like:
>>
>> scoped_mmapped_file (const char *filename)
>> : m_fd (open (filename, 0, O_RDONLY))
>>
>> Then "reset" wouldn't be needed at all.
Simon> I can do that, but I am using reset() in the following patch anyway.
Oops, I didn't notice that. FWIW I think it's fine to have a reset
method.
Tom
next prev parent reply other threads:[~2018-05-12 3:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 21:27 [PATCH RFC 0/5] Add a DWARF index cache Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 3/5] Make index reading functions more modular Simon Marchi
2018-05-10 21:02 ` Tom Tromey
2018-05-10 21:18 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 4/5] Introduce scoped_mmapped_file Simon Marchi
2018-05-10 21:04 ` Tom Tromey
2018-05-10 21:27 ` Simon Marchi
2018-05-12 15:49 ` Tom Tromey [this message]
2018-06-13 1:36 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 5/5] Add DWARF index cache Simon Marchi
2018-05-10 22:24 ` Tom Tromey
2018-07-09 20:56 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 1/5] Rename some functions, index -> gdb_index Simon Marchi
2018-05-10 20:40 ` Tom Tromey
2018-06-12 2:03 ` Simon Marchi
2018-05-09 21:27 ` [PATCH RFC 2/5] Remove mapped_index::total_size Simon Marchi
2018-05-09 23:08 ` Simon Marchi
2018-05-10 20:54 ` Tom Tromey
2018-05-18 20:26 ` Simon Marchi
2018-05-09 21:57 ` [PATCH RFC 0/5] Add a DWARF index cache Simon Marchi
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=878t8p4jif.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
--cc=simon.marchi@polymtl.ca \
/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).