public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26154] [4.2 Regression] OpenMP extensions to the C language is not documented
Date: Tue, 11 Apr 2006 03:00:00 -0000 [thread overview]
Message-ID: <20060411030009.30654.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26154-6528@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from pinskia at gcc dot gnu dot org 2006-04-11 03:00 -------
It should be something like what XLC does at:
http://publib.boulder.ibm.com/infocenter/lnxpcomp/v8v101/topic/com.ibm.xlcpp8l.doc/compiler/ref/ruprpdir.htm#RUPRPDIR
Which is actually much better than what is even in the current GCC docs which
is nothing even at the toplevel of extensions that GCC supports.
--
pinskia at gcc dot gnu dot org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever Confirmed|0 |1
Last reconfirmed|0000-00-00 00:00:00 |2006-04-11 03:00:09
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26154
next prev parent reply other threads:[~2006-04-11 3:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 13:44 [Bug c/26154] New: " pinskia at gcc dot gnu dot org
2006-02-07 13:44 ` [Bug c/26154] [4.2 Regression] " pinskia at gcc dot gnu dot org
2006-04-11 3:00 ` pinskia at gcc dot gnu dot org [this message]
2006-06-04 17:35 ` mmitchel at gcc dot gnu dot org
2006-06-04 18:04 ` dnovillo at gcc dot gnu dot org
2006-06-17 0:20 ` mmitchel at gcc dot gnu dot org
2006-06-17 0:23 ` [Bug c/26154] [4.2 Regression] OpenMP extensions to the C language is not documented or doumented in the wrong spot pinskia at gcc dot gnu dot org
2006-06-17 0:23 ` pinskia at gcc dot gnu dot org
2006-06-17 0:28 ` pinskia at gcc dot gnu dot org
2006-06-17 0:50 ` mmitchel at gcc dot gnu dot org
2006-06-17 0:59 ` [Bug c/26154] " pinskia at gcc dot gnu dot org
2006-09-29 9:22 ` jakub at gcc dot gnu dot org
2007-05-14 21:31 ` mmitchel at gcc dot gnu dot org
2007-07-20 3:50 ` mmitchel at gcc dot gnu dot org
2007-10-09 19:30 ` mmitchel at gcc dot gnu dot org
2008-02-01 16:54 ` jsm28 at gcc dot gnu dot org
2008-05-19 20:25 ` jsm28 at gcc dot gnu dot org
2008-07-04 19:49 ` [Bug c/26154] [4.2/4.3/4.4 Regression] " jsm28 at gcc dot gnu dot org
2009-03-31 19:29 ` [Bug c/26154] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org
2009-08-04 12:51 ` rguenth at gcc dot gnu dot org
2010-05-22 18:16 ` [Bug c/26154] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org
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=20060411030009.30654.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).