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 web/35777] no DFP announcement, no example text, very vague documentation
Date: Sat, 05 Apr 2008 00:08:00 -0000 [thread overview]
Message-ID: <20080405000713.13622.qmail@sourceware.org> (raw)
In-Reply-To: <bug-35777-365@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from pinskia at gcc dot gnu dot org 2008-04-05 00:07 -------
(In reply to comment #4)
> > I don't see OpenMP documented there at all.
>
> What about <http://gcc.gnu.org/onlinedocs/gcc-4.3.0/libgomp/>?
Still not part of the C/C++ Language Extension section of the documentation. I
filed a bug about this too, see
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26154 I had to reopen it too.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35777
next prev parent reply other threads:[~2008-04-05 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-31 18:40 [Bug web/35777] New: " bkoz at gcc dot gnu dot org
2008-03-31 19:53 ` [Bug web/35777] " pinskia at gcc dot gnu dot org
2008-03-31 23:02 ` janis at gcc dot gnu dot org
2008-04-01 0:00 ` bje at gcc dot gnu dot org
2008-04-04 23:54 ` brian at dessent dot net
2008-04-05 0:08 ` pinskia at gcc dot gnu dot org [this message]
2009-08-06 14:41 ` manu at gcc dot gnu dot org
2009-10-15 17:29 ` bkoz 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=20080405000713.13622.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).