From: Jakub Jelinek <jakub@redhat.com>
To: Mohamed Atef <mohamedatef1698@gmail.com>
Cc: gcc@gcc.gnu.org, Martin Jambor <mjambor@suse.cz>,
Tobias Burnus <tobias@codesourcery.com>
Subject: Re: OMPD patch
Date: Mon, 21 Nov 2022 11:31:50 +0100 [thread overview]
Message-ID: <Y3tTllevEzzaC1Eb@tucnak> (raw)
In-Reply-To: <CAPFh8NJ0gp3TW39KxZFW06h2tRS2USVMdx_MVKtTUi8fAJCxKw@mail.gmail.com>
On Mon, Nov 21, 2022 at 12:21:25PM +0200, Mohamed Atef wrote:
> Sorry for sending this mail lately. As you know my team, and I are
> responsible for adding OMPD support to libgomp, but the project is still
> unfinished I added a big part you can find it on devel/omp/ompd/ branch and
> here in my country the military service is a must so I joined the army and
> I don't have time to work on tge project, I haven't even touched a keyboard
> for 40 days. Surfing gcc-patch history the guys didn't post any related
> patches. I wonder what is the future of my patches?
We'll need to find time to finish the project ourselves. As it is on
a branch on gcc.gnu.org, we can (and will) use the patches that have
been committed there, but as GCC entered into stage3 already, it will be
deferred till next year and so targetted at GCC 14.
Jakub
prev parent reply other threads:[~2022-11-21 10:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 10:21 Mohamed Atef
2022-11-21 10:31 ` Jakub Jelinek [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=Y3tTllevEzzaC1Eb@tucnak \
--to=jakub@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=mjambor@suse.cz \
--cc=mohamedatef1698@gmail.com \
--cc=tobias@codesourcery.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).