public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Dibyendu Majumdar <mobile@majumdar.org.uk>
To: David Malcolm <dmalcolm@redhat.com>
Cc: jit@gcc.gnu.org
Subject: Re: Basic linking / compilation question
Date: Thu, 01 Jan 2015 00:00:00 -0000	[thread overview]
Message-ID: <CACXZuxfqotba_7qdzkFbA8fN-Y=17_pb4B57vEK53eJ-PHRVHg@mail.gmail.com> (raw)
In-Reply-To: <1433798708.12727.135.camel@surprise>

On 8 June 2015 at 22:25, David Malcolm <dmalcolm@redhat.com> wrote:
> On Mon, 2015-06-08 at 21:58 +0100, Dibyendu Majumdar wrote:
>> Is it a requirement that the application using libgccjit needs to be
>> compiled using gcc 5.1 or does it not matter?
>
> I don't think it should matter; I think it ought to just work.  For
> example, using an older gcc for the application ought to be fine (though
> that said, the testsuite doesn't cover this possibility).
>
> [I'm assuming that the compiler you're using for the application is
> sufficiently ABI-compatible with that used to compile libgccjit (e.g.
> calling conventions) - you're not attempting to e.g. link code compiled
> with Visual C++ against code compiled with gcc or anything like that are
> you?]

I used gcc 4.8.2 to compile gcc 5.1 (building on Ubuntu so no VC++).
Would like to continue using 4.8.2 for building Ravi (simply because
that's the installed version).

Regards
Dibyendu

  reply	other threads:[~2015-06-08 21:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-01  0:00 Dibyendu Majumdar
2015-01-01  0:00 ` David Malcolm
2015-01-01  0:00   ` Dibyendu Majumdar [this message]
2015-01-01  0:00     ` Dibyendu Majumdar
2015-01-01  0:00       ` David Malcolm
2015-01-01  0:00         ` Dibyendu Majumdar

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='CACXZuxfqotba_7qdzkFbA8fN-Y=17_pb4B57vEK53eJ-PHRVHg@mail.gmail.com' \
    --to=mobile@majumdar.org.uk \
    --cc=dmalcolm@redhat.com \
    --cc=jit@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).