public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: schnetter@uni-tuebingen.de
To: gcc-gnats@gcc.gnu.org
Subject: web/10254: Explain binary compatibility to other vendors' compilers
Date: Fri, 28 Mar 2003 11:56:00 -0000 [thread overview]
Message-ID: <20030328115155.4481.qmail@sources.redhat.com> (raw)
>Number: 10254
>Category: web
>Synopsis: Explain binary compatibility to other vendors' compilers
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: gerald
>State: open
>Class: doc-bug
>Submitter-Id: net
>Arrival-Date: Fri Mar 28 11:56:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: Erik Schnetter
>Release: unknown-1.0
>Organization:
>Environment:
n/a
>Description:
I have been searching the web pages to find out whether g++ 3.3 and Intel's icc 7.1 are binary compatible. I found no such pages on the gcc web site, only a page on Intel's site at http://www.intel.com/support/performancetools/c/linux/iccgcclink.htm.
However, this page does not give any details of what might go wrong, what the symptoms are, what to avoid, or whether there are plans to become more compatible.
It would be nice if gcc had such a page itself, possibly extended to other languages and other vendors. Possibly such a page already exists, and I just didn't find the link. For the beginning, it would be enough to point to other vendors' pages that exist.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-03-28 11:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 11:56 schnetter [this message]
2003-03-28 22:44 Janis Johnson
2003-03-29 13:36 gerald
2003-03-31 15:06 Erik Schnetter
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=20030328115155.4481.qmail@sources.redhat.com \
--to=schnetter@uni-tuebingen.de \
--cc=gcc-gnats@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).