public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Brian D. McGrew" <brian@visionpro.com>
To: <gcc-help@gcc.gnu.org>, 		<gcc@gcc.gnu.org>
Subject: 64-Bit Operator Overloading Adventure
Date: Sat, 12 Jan 2008 22:55:00 -0000	[thread overview]
Message-ID: <01CB178573DD65409C3958440EF758AD106D39@mvpexchange126.machinevisionproducts.com> (raw)

Good morning,

I've got a codebase that's a hundred years old, started in life on Sun3
and have evolved to 32-Bit X86 Linux (Fedora 5).  We're trying to move
to 64-Bit now and this same code that has compiled for years is barking
about operators cannot be overloaded.

This is a Fedora 8 x86-64 machine using gcc-4.1.2 (stock Fedora).  I'm
brand new to 64-Bit but all of this compiles and runs just fine on
32-Bit using the same compiler!  

I've already changed long to int in many places to maintain 32-bit where
I know I need it but I don't think that has anything to do with the
errors from overloaded operators.

Can anyone offer me some help or point me in the right direction?

Thanks,

-brian

             reply	other threads:[~2008-01-11 18:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-12 22:55 Brian D. McGrew [this message]
2008-01-14  3:20 ` Jonathan Wakely

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=01CB178573DD65409C3958440EF758AD106D39@mvpexchange126.machinevisionproducts.com \
    --to=brian@visionpro.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=gcc@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).