From: Joel Brobecker <brobecker@adacore.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: gdb-patches@sourceware.org
Subject: Re: GDB 10 branching - 2020-07-18 Update
Date: Mon, 20 Jul 2020 08:22:52 -0700 [thread overview]
Message-ID: <20200720152252.GB11122@adacore.com> (raw)
In-Reply-To: <yddy2nea08s.fsf@CeBiTec.Uni-Bielefeld.DE>
> > * [RainerO]
> > Unify Solaris procfs and largefile handling
> > https://sourceware.org/pipermail/gdb-patches/2020-June/169977.html
> >
> > Seems to require a fair amount of coordination. binutils approved
>
> as I'd mentionen before: no coordination required, just a GDB review ;-)
>
> While GCC hosts the master copy of config/largefile.m4, it isn't used
> anywhere in that tree.
Grumpf. Copy/paste/edit error. I added the note about not having to
coordinate the part in config/, but then forgot to remove the initial
sentence. I amended my local copy, so hopefully I won't repeat that!
> > that part of the patch. Waiting for a review on the GDB side (the part
> > in config/ is only used by GDB, so we will review it on the GDB side
> > as well).
>
> Actually, ACX_LARGEFILE defined there is used on both sides. However,
> the primary benefit is for GDB, so an additional review with that in
> mind would certainly be helpful.
--
Joel
next prev parent reply other threads:[~2020-07-20 15:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-18 19:45 Joel Brobecker
2020-07-19 2:28 ` Eli Zaretskii
2020-07-19 15:03 ` Joel Brobecker
2020-07-25 7:56 ` Eli Zaretskii
2020-07-20 11:34 ` Rainer Orth
2020-07-20 15:22 ` Joel Brobecker [this message]
2020-07-21 20:38 ` Tom Tromey
2020-07-22 12:57 ` Joel Brobecker
2020-07-22 20:32 ` Kevin Buettner
2020-07-23 18:43 ` Joel Brobecker
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=20200720152252.GB11122@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=ro@CeBiTec.Uni-Bielefeld.DE \
/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