public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: William Tambe <tambewilliam@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: How to customize GCC builtin search paths
Date: Mon, 13 Apr 2020 21:56:45 +0100	[thread overview]
Message-ID: <CAH6eHdTHGSwyx10D-ZYMiHoOPi19iVDBR=t=w8z6QLkb=-yBAQ@mail.gmail.com> (raw)
In-Reply-To: <CAFyWVab7XmS6AUjdAoYzTvSbpuPx-C9W8qcAhUY1SHBD2Zf1rQ@mail.gmail.com>

On Mon, 13 Apr 2020 at 21:46, Jim Wilson wrote:
>
> On Sun, Apr 12, 2020 at 9:06 AM William Tambe <tambewilliam@gmail.com> wrote:
> > I can hardly find examples on how to use startfile_prefixes. Currently
> > when running gcc as follow:
> > arch-elf-gcc -v test.c
> >
> > I get the following excerpt showing how gcc looks for includes:
>
> You have the source code.  You can find a lot of info by using grep to
> search for obvious things, like /usr/include for instance, and then
> follow the code to see where it takes you.

Right, the following commands were all I needed to answer your
question about thread model:

git grep 'Thread model' gcc
git grep thrmod gcc
git grep thread_model gcc
gvim gcc/configure.ac
git grep thread_file gcc
gvim gcc/config.gcc

You could have done that yourself pretty easily, and probably found
the answer quicker than waiting for a reply from the mailing list.

      reply	other threads:[~2020-04-13 20:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10  2:52 William Tambe
2020-04-10 17:15 ` Jim Wilson
2020-04-12 16:06   ` William Tambe
2020-04-13 20:44     ` Jim Wilson
2020-04-13 20:56       ` Jonathan Wakely [this message]

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='CAH6eHdTHGSwyx10D-ZYMiHoOPi19iVDBR=t=w8z6QLkb=-yBAQ@mail.gmail.com' \
    --to=jwakely.gcc@gmail.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=tambewilliam@gmail.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).