From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] sourcebuild.texi: Document new toplevel directories [PR82383]
Date: Sat, 28 May 2022 12:29:55 -0600 [thread overview]
Message-ID: <4bddccab-1713-6691-920b-0bf5a20a7efb@gmail.com> (raw)
In-Reply-To: <CAMfHzOvFnLFiJTZ7bcrsEsC856uAMJ-1U05sTXd8OVdHa8JwTQ@mail.gmail.com>
On 5/24/2022 11:32 AM, Eric Gallager via Gcc-patches wrote:
> This patch adds entries for the c++tools, gotools, libbacktrace,
> libcc1, libcody, liboffloadmic, and libsanitizer directories into the
> list of toplevel source directories in sourcebuild.texi. I also
> removed the entry for boehm-gc (which is no longer in-tree), and fixed
> the alphabetization for libquadmath while I was at it. Any style nits
> I need to fix before committing (with a proper ChangeLog entry)?
I think this is fine. If you're looking for a good cleanup, removing
liboffloadmic would be useful IMHO. MIC is dead.
jeff
next prev parent reply other threads:[~2022-05-28 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 17:32 Eric Gallager
2022-05-28 18:29 ` Jeff Law [this message]
2022-05-29 5:04 ` Eric Gallager
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=4bddccab-1713-6691-920b-0bf5a20a7efb@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@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).