public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Per Bothner <per@bothner.com>
Cc: "Joseph S. Myers" <jsm@polyomino.org.uk>,  gcc@gcc.gnu.org
Subject: Re: #pragma interface/implementation broken if --enable-mapped-location
Date: Wed, 29 Sep 2004 20:56:00 -0000	[thread overview]
Message-ID: <87acv9t012.fsf@codesourcery.com> (raw)
In-Reply-To: <415AF988.9090208@bothner.com> (Per Bothner's message of "Wed, 29 Sep 2004 11:06:00 -0700")

Per Bothner <per@bothner.com> writes:

> Zack Weinberg wrote:
>
>> Given all that, I think it makes sense for all pragmas to become
>> token sequences.
>
> How close are we to having this?
>
> I'm hoping to check in today my gcc/java changes to handle
> --enable-mapped-location.  That would allow bootstrapping gcc
> with the default set of languages.  But that requires a fix
> or workaround for the #pragma interface/implementation bug,
> since otherwise libjava won't build.
>
> If we're not close to the #pragma-as-token change, I could
> implement a quickie fix to for example temporarily clear
> cb.line_change during cpp_handle_deferred_pragma.

I think we're at least a couple weeks away from #pragma-as-tokens.  A
quickie fix would be fine by me.

zw

  reply	other threads:[~2004-09-29 18:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-24  2:08 Per Bothner
2004-09-24  2:22 ` Zack Weinberg
2004-09-24  2:43   ` Per Bothner
2004-09-24  4:58     ` Zack Weinberg
2004-09-24 14:17       ` Joseph S. Myers
2004-09-24 21:47         ` Zack Weinberg
2004-09-24 22:15           ` Joseph S. Myers
2004-09-24 22:34             ` Zack Weinberg
2004-09-29 19:24           ` Per Bothner
2004-09-29 20:56             ` Zack Weinberg [this message]
2004-09-29 21:57               ` Matt Austern
2004-09-29 22:50                 ` Zack Weinberg
2004-09-30  7:57               ` Per Bothner

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=87acv9t012.fsf@codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jsm@polyomino.org.uk \
    --cc=per@bothner.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).