public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, cltang@codesourcery.com
Subject: Re: [PATCH] nios2-linux: add missing cpp specs
Date: Sat, 30 May 2015 04:50:00 -0000	[thread overview]
Message-ID: <20150530032823.GC2101@vapier> (raw)
In-Reply-To: <5568B0A4.9050106@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]

On 29 May 2015 12:32, Sandra Loosemore wrote:
> On 05/29/2015 11:36 AM, Mike Frysinger wrote:
> > On 29 May 2015 08:44, Sandra Loosemore wrote:
> >> On 05/27/2015 10:00 AM, Mike Frysinger wrote:
> >>> Define CPP_SPEC for nios2 linux targets so that -posix & -pthread work
> >>> like on all other linux targets.
> >>>
> >>> 2015-05-27  Mike Frysinger  <vapier@gentoo.org>
> >>>
> >>> 	* config/nios2/linux.h (CPP_SPEC): Define.
> >>
> >> I see that -posix is not documented at all in invoke.texi and -pthread
> >> is documented only for RS6000 and Solaris (which is not Linux).  What,
> >> exactly, are these options supposed to do on "all other linux targets"?
> >>    If these options are supposed to be generic to all Linux targets,
> >> can't they be handled in some common way instead of duplicating the
> >> CPP_SPEC code in all the individual back ends?
> >
> > please see my other threads/patches
> 
> (Sorry, I am a few days behind in mailing list traffic, was just trying 
> to respond to the review request that was CC'ed to me directly.)
> 
> Do you mean this one?
> 
> https://gcc.gnu.org/ml/gcc-patches/2015-05/msg02708.html

yes

> That addresses my concern about not duplicating this in every back end, 
> but I still don't see any documentation and don't really understand what 
> these flags are supposed to do or why I might need to add them to my 
> command line.  Taking off my nios2 maintainer hat and putting on the 
> docs maintainer one instead, I think proper documentation for these 
> options is a requirement here....

i'm not familiar with the history.  i'm merely cleaning up some of the mess.
both defines are respected by glibc and make a difference to compilation.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-05-30  3:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 16:05 Mike Frysinger
2015-05-29 15:41 ` Sandra Loosemore
2015-05-29 18:42   ` Mike Frysinger
2015-05-29 19:32     ` Sandra Loosemore
2015-05-30  4:50       ` Mike Frysinger [this message]
2015-05-30 16:09         ` Sandra Loosemore
2015-05-30 19:13           ` Mike Frysinger

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=20150530032823.GC2101@vapier \
    --to=vapier@gentoo.org \
    --cc=cltang@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=sandra@codesourcery.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).