public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Lionel B <lionelbuk@yahoo.co.uk>
To: gcc-help@gcc.gnu.org
Subject: Re: errors in porting on gcc 3.4.6 from gcc 3.2.3
Date: Tue, 15 May 2007 11:14:00 -0000	[thread overview]
Message-ID: <f2c4l1$dup$1@sea.gmane.org> (raw)
In-Reply-To: <10620590.post@talk.nabble.com>

On Tue, 15 May 2007 03:47:03 -0700, kushwaha wrote:

> hi all..
> 
> Following is the part of a code giving error with gcc 3.4.6  which
> previously compiled with gcc 3.2.3.

Are you sure...? Compiling your code (gcc 4.1.2) I get:

error: ‘class HString_Key’ has no member named ‘mpcCallId’
error: ‘class HString_Key’ has no member named ‘mulHashId’

from these lines:

    key.mpcCallId = apcCallId;
    key.mulHashId = apcHashId;

and sure enough, your class template HString_Key does not contain those 
members. I don't see how this could have compiled with gcc 3.2.3. Didn't 
you mean:

    key.mpcId = apcCallId;
    key.mulId = apcHashId;

in Equal_to_HString_Key::Equal_to_HString_Key(...) ? Compiles ok for me 
with this change.

[...]

-- 
Lionel B

  reply	other threads:[~2007-05-15 11:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-15 10:47 kushwaha
2007-05-15 11:14 ` Lionel B [this message]
2007-05-15 11:49   ` kushwaha
2007-05-15 12:19     ` Lionel B

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='f2c4l1$dup$1@sea.gmane.org' \
    --to=lionelbuk@yahoo.co.uk \
    --cc=gcc-help@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).