public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@redhat.com>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: Richard Guenther <richard.guenther@gmail.com>,
	gcc-patches@gcc.gnu.org,         joseph@codesourcery.com
Subject: Re: [PATCH PING 2/5] Named address spaces: support multiple pointer        modes
Date: Wed, 23 Sep 2009 15:26:00 -0000	[thread overview]
Message-ID: <4ABA3CFD.6040008@redhat.com> (raw)
In-Reply-To: <200909230055.n8N0tuj5027457@d12av02.megacenter.de.ibm.com>

On 09/22/2009 05:55 PM, Ulrich Weigand wrote:
> So I guess the macro can either go into targhooks.h after all,
> or maybe it should go into target.h with the additional rule
> that you need to also include targhooks.h if you want to use it.

When I get into those kind of nasty header situations,
I usually break down and put the thing in a function
somewhere.


r~

  reply	other threads:[~2009-09-23 15:21 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 16:50 Ulrich Weigand
2009-09-20  1:52 ` Richard Guenther
2009-09-21 13:52   ` Ulrich Weigand
2009-09-21 15:31     ` Richard Guenther
2009-09-21 15:35       ` Ulrich Weigand
2009-09-22 20:26     ` Richard Henderson
2009-09-22 22:51       ` Ulrich Weigand
2009-09-22 23:21         ` Joseph S. Myers
2009-09-23  0:11         ` Richard Henderson
2009-09-23  1:17           ` Ulrich Weigand
2009-09-23 15:26             ` Richard Henderson [this message]
2009-09-24 16:08               ` Ulrich Weigand
2009-09-24 16:50                 ` Richard Henderson
2009-09-24 18:26                   ` Ulrich Weigand
2009-09-24 18:43                     ` Richard Henderson
2009-09-24 20:40                       ` Ulrich Weigand
2009-11-14 20:53 Dmitry Gorbachev
2009-11-16 20:06 ` Ulrich Weigand
2009-11-17  6:13   ` Dmitry Gorbachev
2009-11-17 16:18     ` Ulrich Weigand

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=4ABA3CFD.6040008@redhat.com \
    --to=rth@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=richard.guenther@gmail.com \
    --cc=uweigand@de.ibm.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).