public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bryan Carroll <bcarroll1@uco.edu>
To: gcc@gcc.gnu.org
Subject: Re: GSoC OMPD
Date: Wed, 03 Apr 2019 19:17:00 -0000	[thread overview]
Message-ID: <CAMxxcCYLcXWQ42dvGjrSvXu0MDqJuGqcBYk4HQNR6vXHw+yiuw@mail.gmail.com> (raw)
In-Reply-To: <CAMxxcCbHC6ShLcaKLvADh1xhM0iLKuuT4sv5ioMxTq+HD+Pocw@mail.gmail.com>

Hi,

I know my first email is vague. I wanted to throw it out there since
the April 9th deadline is coming up. So far, I've built gcc several
times. I downloaded the gcc source code. Also I compiled a program
with the -fdump options and looked through the files. I've been using
gcc for a few years now for projects.. If you think that OMPD will too
much for a first time GCC developer, I'm willing to try for a
different project.

Thank you,
Bryan Carroll

On Mon, Apr 1, 2019 at 2:05 PM Bryan Carroll <bcarroll1@uco.edu> wrote:
>
> Hi,
>
> My name is Bryan Carroll and I'm a M.S. student in the Applied
> Mathematics and Computer Science program at University of Central
> Oklahoma. I'm interested in the OpenMP and GDB debugger project.
>
> A little bit about myself: I've been programming for about 6 years,
> the majority of those years in C++ or C. Last year I started learning
> about parallelization. I taught myself MPI and recently started
> learning OpenMP. I have some experience with compiling - I'm taking a
> Progamming Languages class right now.  The final project is an
> assembler.
>
> I know how to debug programs. However, I don't really know much about
> how debuggers work. I also don't really know about how OpenMP works
> underneath the directives. I very much want to learn about these
> topics. I'm very much willing to learn and think I could be of help to
> this project.
>
> What I'd like to know and discuss: What other pre-requisites are there
> other than those listed on the GNU GSoC page? Also what would the
> goals and timeline look like?
>
> Thank you for your time,
>
> Bryan Carroll
> M.S. at University of Central Oklahoma

  reply	other threads:[~2019-04-03 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-01 19:05 Bryan Carroll
2019-04-03 19:17 ` Bryan Carroll [this message]
2019-04-04 12:24   ` Martin Jambor
2019-04-04 14:22     ` Jeff Law
2019-04-08 13:45     ` Jakub Jelinek

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=CAMxxcCYLcXWQ42dvGjrSvXu0MDqJuGqcBYk4HQNR6vXHw+yiuw@mail.gmail.com \
    --to=bcarroll1@uco.edu \
    --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).