public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Janis Johnson <janis187@us.ibm.com> To: gerald@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: web/10254: Explain binary compatibility to other vendors' compilers Date: Fri, 28 Mar 2003 22:44:00 -0000 [thread overview] Message-ID: <20030328223601.31647.qmail@sources.redhat.com> (raw) The following reply was made to PR web/10254; it has been noted by GNATS. From: Janis Johnson <janis187@us.ibm.com> To: schnetter@uni-tuebingen.de Cc: gcc-gnats@gcc.gnu.org Subject: Re: web/10254: Explain binary compatibility to other vendors' compilers Date: Fri, 28 Mar 2003 14:38:13 -0800 Information about binary compatibility between GCC and other compilers would be useful, but a page keeping track of such information could get messy very quickly. The information itself could become outdated when new versions of compilers are released, and links like this are difficult to keep up to date. There's another problem with providing links to information about other compilers. I looked up a particular compiler to see if it had a statement about binary compatibility with GCC; it does, but it follows a claim about how easy it is to port code from using GCC to using that proprietary compiler. Links to that kind of information aren't appropriate for the GCC site. It would be appropriate, though, for us to describe known incompatibilities or ABI corner cases, along with examples that demonstrate how real code is affected. I've been planning to add more of such examples as test cases in testsuite/g++.dg/compat/abi (feel free to nag me about that). Those tests (once they exist!) could be mentioned in the Binary Compatibility section of the GCC Manual. Erik, does that sound reasonable? Janis Johnson janis187@us.ibm.com
next reply other threads:[~2003-03-28 22:36 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-28 22:44 Janis Johnson [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-31 15:06 Erik Schnetter 2003-03-29 13:36 gerald 2003-03-28 11:56 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=20030328223601.31647.qmail@sources.redhat.com \ --to=janis187@us.ibm.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=gerald@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: linkBe 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).