From: Joseph Myers <joseph@codesourcery.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] unify -posix/-pthread cpp handling for gnu-user targets
Date: Fri, 29 May 2015 23:24:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.10.1505292144350.17156@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1432853300-20232-1-git-send-email-vapier@gentoo.org>
On Thu, 28 May 2015, Mike Frysinger wrote:
> Some targets still define -posix/-pthread in SUBTARGET_CPP_SPEC and in
> CPP_SUBTARGET_SPEC, but I can't seem to find any reference to either of
> those defines. Are they dead/confused code and I should just delete it ?
Any correct definitions of those macros will have a target-specific use
e.g. in EXTRA_SPECS (with %(subtarget_cpp_spec) included in CPP_SPEC).
It's entirely possible that there are some definitions that are in fact
unused because those architectures lack such code to use them..
--
Joseph S. Myers
joseph@codesourcery.com
prev parent reply other threads:[~2015-05-29 21:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 2:04 Mike Frysinger
2015-05-29 23:24 ` Joseph Myers [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=alpine.DEB.2.10.1505292144350.17156@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=vapier@gentoo.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).