From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: guray ozen <guray.ozen@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: About gsoc 2014 OpenMP 4.0 Projects
Date: Wed, 19 Mar 2014 03:02:00 -0000 [thread overview]
Message-ID: <7119F1D5-9BCC-4942-9251-E2452BBE60BB@linaro.org> (raw)
In-Reply-To: <CA+ga0G6c=xCpmvWH5MY0ynxLXmaknAjhB8N+8=WSKvaNfFRHFg@mail.gmail.com>
On Feb 26, 2014, at 12:27 AM, guray ozen <guray.ozen@gmail.com> wrote:
> Hello,
>
> I'm master student at high-performance computing at barcelona
> supercomputing center. And I'm working on my thesis regarding openmp
> accelerator model implementation onto our compiler (OmpSs). Actually i
> almost finished implementation of all new directives to generate CUDA
> code and same implementation OpenCL doesn't take so much according to
> my design. But i haven't even tried for Intel mic and apu other
> hardware accelerator :) Now i'm bench-marking output kernel codes
> which are generated by my compiler. although output kernel is
> generally naive, speedup is not very very bad. when I compare results
> with HMPP OpenACC 3.2.x compiler, speedups are almost same or in some
> cases my results are slightly better than. That's why in this term, i
> am going to work on compiler level or runtime level optimizations for
> gpus.
>
> When i looked gcc openmp 4.0 project, i couldn't see any things about
> code generation. Are you going to announce later? or should i apply
> gsoc with my idea about code generations and device code
> optimizations?
Guray
Do you have a proposal for a GSoC GCC project? If you do want to apply, please make sure you are registered at the GSoC website and have a application filed by end of Thursday (only 2 days left!).
Thank you,
--
Maxim Kuvyrkov
www.linaro.org
prev parent reply other threads:[~2014-03-19 3:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 11:27 guray ozen
2014-02-26 7:20 ` Evgeny Gavrin
2014-02-27 17:25 ` guray ozen
2014-02-27 20:25 ` Thomas Schwinge
2014-03-19 3:02 ` Maxim Kuvyrkov [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=7119F1D5-9BCC-4942-9251-E2452BBE60BB@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=gcc@gcc.gnu.org \
--cc=guray.ozen@gmail.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).