public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Qihang Huang <qihang.huang@gmail.com>
To: Antoniu Pop <antoniu.pop@mines-paristech.fr>
Cc: gcc@gcc.gnu.org
Subject: Re: OpenMP 3.0 libgomp ABI documentation for TASK construct
Date: Tue, 06 Oct 2009 03:09:00 -0000	[thread overview]
Message-ID: <1104fbfa0910052009i3000316bpe06d06ae5acd55dd@mail.gmail.com> (raw)
In-Reply-To: <1b8617c60910041229lff0c3f5re8c3ed26b7bcc3f7@mail.gmail.com>

That's super! Thank you Antoniu. With the capacity of printing the
expanded code, it feels a lot more freedom now when reading the source
code of libgomp.

Cheers,
Tim

On Mon, Oct 5, 2009 at 8:29 AM, Antoniu Pop
<antoniu.pop@mines-paristech.fr> wrote:
> Hi Tim,
>
>
>> From gcc online docs (http://gcc.gnu.org/onlinedocs/libgomp/), I found
>> documentations for most of OpenMP constructs, except one very
>> important construct TASK.
>
> I cannot answer this. It may be that the documentation was written
> before tasks (which were introduced in a latter version  of OpenMP)
> were added to GCC OpenMP.
>
>>
>> I don't know why it is missing, but I really
>> need to find out how TASK get transformed into GOMP_* routines. I
>> posted this question before, but haven't got a reply yet. I am very
>> grateful if someone can point me to the right track. For example, is
>> there a pretty-print feature of the AST after processing the OpenMP
>> pragmas? If so, how? Of course, if someone have the expertise, and
>> directly show me how TASK get transformed, it would be even better!
>
>
> For the pretty print, just use -fdump-tree-ompexp-all on the compile
> line and look for the file *.c.*ompexp that is generated. It contains
> the dump just after OpenMP expansion.
>
> If you need to check out the code generation routines by yourself,
> take a look at gcc/omp-low.c
> Most of everything happens there. There are two passes, OpenMP
> lowerring then expansion. The generation of the GOMP_* routine calls
> happens during expansion pass and so you should start from the
> "expand_omp_taskreg" function (in gcc/omp-low.c).
>
> Best,
> Antoniu
>

      reply	other threads:[~2009-10-06  3:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-04  3:00 Qihang Huang
2009-10-04 19:29 ` Antoniu Pop
2009-10-06  3:09   ` Qihang Huang [this message]

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=1104fbfa0910052009i3000316bpe06d06ae5acd55dd@mail.gmail.com \
    --to=qihang.huang@gmail.com \
    --cc=antoniu.pop@mines-paristech.fr \
    --cc=gcc@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).