From: Ian Lance Taylor <iant@google.com>
To: mario guerra <emailformario@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: supporting multiple versions of GCC with a single shared object release?
Date: Fri, 17 Apr 2009 15:30:00 -0000 [thread overview]
Message-ID: <m33ac7mh77.fsf@google.com> (raw)
In-Reply-To: <43380.59367.qm@web34802.mail.mud.yahoo.com> (mario guerra's message of "Fri\, 17 Apr 2009 07\:55\:16 -0700 \(PDT\)")
mario guerra <emailformario@yahoo.com> writes:
> On a related note, if we tried this approach would we have to worry
> about any differences in the implementation of exception handling
> between different versions of GCC?
Exception is handling is identical and compatible since 3.2 or so.
Ian
next prev parent reply other threads:[~2009-04-17 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 14:55 mario guerra
2009-04-17 15:30 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-15 17:13 mario guerra
2009-04-15 17:40 ` Ian Lance Taylor
2009-04-15 17:09 mario guerra
[not found] <5480d0a80904141452g45324a9ch68c1e1a6e5e51904@mail.gmail.com>
2009-04-14 22:02 ` mario guerra
2009-04-14 22:09 ` Brian Budge
2009-04-14 22:21 ` Ian Lance Taylor
2009-04-15 15:09 ` John Fine
2009-04-16 17:06 ` 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=m33ac7mh77.fsf@google.com \
--to=iant@google.com \
--cc=emailformario@yahoo.com \
--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).