From: Steven Bosscher <s.bosscher@student.tudelft.nl>
To: per@bothner.com
Cc: OpenMP for GCC project <gomp-discuss@nongnu.org>, gcc@gcc.gnu.org
Subject: Re: [Gomp-discuss] Re: Implementing OpenMP pragmas for the C frontend
Date: Mon, 10 Feb 2003 07:37:00 -0000 [thread overview]
Message-ID: <1044862653.743.7.camel@steven> (raw)
Per Bothner wrote:
> David Edelsohn wrote:
> > Unfortunately, this is a public standard.
>
> There are all kinds of "public" standards.
Some public standards are supported by the major compiler vendors, some
are not. OpenMP is one of those standards that *is* supported, probably
because it was designed by the compiler vendors (OpenMP Review Board
members: HP, Fujitsu, IBM, Intel, KAI, SGI, Sun, US Gov.(DEO))
> > Somehow we need to be compatible.
>
> "We" only need to be compatible if we make
> a comittment to implementing OpenMP. I don't
> think we should make any comittment to accepting
> an OpenMP implementation in the offical CVS tree.
Why not? What is wrong with accepting a much-requested feature, that is
implemented by most other serious compilers? Any technical objections
apart from the #pragma/_Pragma() thing?
Greetz
Steven
next reply other threads:[~2003-02-10 7:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 7:37 Steven Bosscher [this message]
2003-02-10 8:13 ` Per Bothner
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=1044862653.743.7.camel@steven \
--to=s.bosscher@student.tudelft.nl \
--cc=gcc@gcc.gnu.org \
--cc=gomp-discuss@nongnu.org \
--cc=per@bothner.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).