From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 6C1A93858401 for ; Mon, 21 Nov 2022 10:31:59 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 6C1A93858401 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1669026719; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=DqAjl0P5DjvSzFf3CdsLcIddWsjM+fWhHlii9IzujNI=; b=N40Wnx3spiuYGrJIkawqn71WWwsnLumpNqXlu2hb7HiAeeOVCEzmQs9vOAGrDz/F8OeuQJ up3w7zXzp1jFJXxyPcQ7ZSsy4Cy2aFBDyMD0wMWOqPLxohF/GHTzb3h9DCPFIjEDUfXxOa 37MPXKO7l6mgZgsCo7ghmNr6J+YOlGY= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-644-7tiMr1gOOsqH_MvmL5sTsw-1; Mon, 21 Nov 2022 05:31:57 -0500 X-MC-Unique: 7tiMr1gOOsqH_MvmL5sTsw-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 6F330101A528; Mon, 21 Nov 2022 10:31:57 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.39.194.202]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 16A4AC15BB3; Mon, 21 Nov 2022 10:31:56 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 2ALAVp5K005343 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Mon, 21 Nov 2022 11:31:52 +0100 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 2ALAVoNd005342; Mon, 21 Nov 2022 11:31:50 +0100 Date: Mon, 21 Nov 2022 11:31:50 +0100 From: Jakub Jelinek To: Mohamed Atef Cc: gcc@gcc.gnu.org, Martin Jambor , Tobias Burnus Subject: Re: OMPD patch Message-ID: Reply-To: Jakub Jelinek References: MIME-Version: 1.0 In-Reply-To: X-Scanned-By: MIMEDefang 3.1 on 10.11.54.8 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: 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