public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jim Cobban <jcobban@magma.ca>
To: Optymizer Sez <optymizer@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: C++ intermediate bytecode
Date: Fri, 18 Jul 2008 09:10:00 -0000	[thread overview]
Message-ID: <487FFD2F.3050900@magma.ca> (raw)
In-Reply-To: <759067.8352.qm@web53705.mail.re2.yahoo.com>



Optymizer Sez wrote:
> Hi!
>
> I'd like to ask if there is a way to use GCC in order to compile a C++ source program into machine-independent code (bytecode, perhaps?) and then translate the bytecode into processor-dependent code on the target machine?
> Something like the Amsterdam Compiler Kit, but for C++ and x86_64 would be great!
>   
The language definition of C++ is not machine independent so the exact 
meaning of a particular source program varies from platform to 
platform.  For example there are significant differences in the 
interpretation of programs on big-endian as opposed to little-endian 
platforms, and even between 32-bit and 64-bit processors in the same 
family.  Furthermore there are vast differences between different 
operating systems.  Dealing with those differences is one of the issues 
that Java was designed to address.

-- 
Jim Cobban   jcobban@magma.ca
34 Palomino Dr.
Kanata, ON, CANADA
K2M 1M1
+1-613-592-9438

  parent reply	other threads:[~2008-07-18  2:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 15:30 Optymizer Sez
2008-07-14 16:25 ` Ian Lance Taylor
2008-07-15 13:33 ` Tom St Denis
2008-07-18  9:10 ` Jim Cobban [this message]
2008-07-19 13:11 ` Dario Saccavino
2008-07-19 15:24   ` Andrew Haley

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=487FFD2F.3050900@magma.ca \
    --to=jcobban@magma.ca \
    --cc=gcc-help@gcc.gnu.org \
    --cc=optymizer@yahoo.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).