From: David Wohlferd <dw@LimeGreenSocks.com>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Gerald Pfeifer <gerald@pfeifer.com>
Subject: Re: [DOC Patch] symbol rename pragmas
Date: Tue, 13 May 2014 22:37:00 -0000 [thread overview]
Message-ID: <53729E8F.3020507@LimeGreenSocks.com> (raw)
In-Reply-To: <yddwqdp3o6d.fsf@lokon.CeBiTec.Uni-Bielefeld.DE>
> You misunderstood completely: I'm not at all demanding to remove support
> for that pragma in the cross-platform part of the docs or even in the
> code,
Whew! Ok, that's good. Sorry I went all crazy on you. When I thought
that *was* what you were asking for, I wanted to try to talk you out of it.
> just ask to keep documenting the heritage so it's clear why it
> exists and when to use it (or not).
Ok, I get this. I've written text that "discouraged" using things in
the past, even though technically they work just fine.
> Just restoring the first sentence you deleted describing the heritage
> should be enough to do so.
Speaking for myself, I didn't see the old text as favoring one course of
action over another. How would you feel about:
GCC supports a @code{#pragma} directive that changes the name used in
assembly for a given declaration. While this pragma is supported on all
platforms, it is intended primarily to provide compatibility with the
Solaris system headers. This effect can also be achieved using the asm
labels extension (@pxref{Asm Labels}).
To me, this subtly discourages using the pragma other than for Solaris,
maintains the heritage, and immediately provides a viable alternative
for other platforms.
dw
next prev parent reply other threads:[~2014-05-13 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 21:46 David Wohlferd
2014-05-12 22:38 ` Gerald Pfeifer
2014-05-13 5:57 ` Rainer Orth
2014-05-13 11:16 ` David Wohlferd
2014-05-13 11:37 ` Rainer Orth
2014-05-13 17:41 ` Joseph S. Myers
2014-05-13 22:37 ` David Wohlferd [this message]
2014-05-17 1:24 ` David Wohlferd
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=53729E8F.3020507@LimeGreenSocks.com \
--to=dw@limegreensocks.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).