public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Lynn York II" <ph34r3d@ptd.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/5726: .moc/release-mt/../../command.h:497: Internal compiler error.
Date: Mon, 18 Feb 2002 15:36:00 -0000 [thread overview]
Message-ID: <20020218233602.4713.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/5726; it has been noted by GNATS.
From: "Lynn York II" <ph34r3d@ptd.net>
To: <nathan@gcc.gnu.org>,
<gcc-bugs@gcc.gnu.org>,
<gcc-prs@gcc.gnu.org>,
<nobody@gcc.gnu.org>,
<ph34r3d@ptd.net>,
<gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: c++/5726: .moc/release-mt/../../command.h:497: Internal compiler error.
Date: Mon, 18 Feb 2002 18:26:43 -0500
What exactly do you mean by preprocessed source code?
Lynn York II
ph34r3d
ph34r3d@ph34r3d-tech.net
Ph34r3d Technologies
http://www.ph34r3d-tech.net
----- Original Message -----
From: <nathan@gcc.gnu.org>
To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <nobody@gcc.gnu.org>;
<ph34r3d@ptd.net>
Sent: Monday, February 18, 2002 5:13 PM
Subject: Re: c++/5726: .moc/release-mt/../../command.h:497: Internal
compiler error.
> Synopsis: .moc/release-mt/../../command.h:497: Internal compiler error.
>
> State-Changed-From-To: open->feedback
> State-Changed-By: nathan
> State-Changed-When: Mon Feb 18 14:13:56 2002
> State-Changed-Why:
> please provide preprocessed source code
>
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=5726
>
next reply other threads:[~2002-02-18 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-18 15:36 Lynn York II [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-27 19:38 rodrigc
2002-03-03 11:26 Craig Rodrigues
2002-02-18 14:13 nathan
2002-02-18 13:36 ph34r3d
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=20020218233602.4713.qmail@sources.redhat.com \
--to=ph34r3d@ptd.net \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.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).