public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Charlie Xiaoli Huang <hxl@ibm.net>
To: hjl@lucon.org (H.J. Lu)
Subject: here's a short example
Date: Sun, 14 Dec 1997 20:16:00 -0000	[thread overview]
Message-ID: <199712150018.AAA95766@out2.ibm.net> (raw)
In-Reply-To: <m0xhHp6-0004ecC@ocean.lucon.org>

>> ( report on id's in egcs asm file containing '?' that gas chokes on  ...)

> Please send me the smallest preprocessed C++ code and
> your asm output. I will take a look at them.

Here's a very simple example:

    #include <stl.h>
    typedef int *intP;
    typedef  list<intP> intlist;
    fubar()
    {
       intlist alist;
       remove(alist.begin(), alist.end(), NULL);
    }

The interesting thing is that if one were to replace NULL above with
an (intP)0, everything is okay. No errors were reported. 

The cpp output does not seem to transform any lines in there except
making NULL into __null. 

I'm not a c++ language lawyer, but I thought the use of NULL was
okay. Even if it's not, egcs shouldn't generate a bad id for asm to
choke on, right?

I'm sending you the output of egcs -E and egcs -S in a seperate
message for fear that my mailer would not let such a long message
thru...

Thanks for looking into it.

hxl




-- 
H.J. Lu (hjl@gnu.org)

           reply	other threads:[~1997-12-14 20:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <m0xhHp6-0004ecC@ocean.lucon.org>]

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=199712150018.AAA95766@out2.ibm.net \
    --to=hxl@ibm.net \
    --cc=hjl@lucon.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).