public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Tue, 31 Dec 2019 06:03:00 -0000 [thread overview]
Message-ID: <bug-93059-4-Uq3OSioNqP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
fdlbxtqi <euloanty at live dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47559|0 |1
is obsolete| |
Attachment #47560|0 |1
is obsolete| |
Attachment #47570|0 |1
is obsolete| |
Attachment #47571|0 |1
is obsolete| |
--- Comment #33 from fdlbxtqi <euloanty at live dot com> ---
Created attachment 47574
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47574&action=edit
copy_backward bug fixed for the last patch
going to further run testsuite
>From gcc-bugs-return-664254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 31 07:25:35 2019
Return-Path: <gcc-bugs-return-664254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122678 invoked by alias); 31 Dec 2019 07:25:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122613 invoked by uid 48); 31 Dec 2019 07:25:31 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Tue, 31 Dec 2019 07:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93059-4-Dl8viYmTcM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02324.txt.bz2
Content-length: 333
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #34 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to fdlbxtqi from comment #33)
> Created attachment 47574 [details]
> copy_backward bug fixed for the last patch
>
> going to further run testsuite
Your test does not contain any test cases.
>From gcc-bugs-return-664255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 31 08:44:17 2019
Return-Path: <gcc-bugs-return-664255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18542 invoked by alias); 31 Dec 2019 08:44:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18511 invoked by uid 48); 31 Dec 2019 08:44:13 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/93109] New: #undefine suggests #define but not #undef
Date: Tue, 31 Dec 2019 08:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02325.txt.bz2
Content-length: 729
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93109
Bug ID: 93109
Summary: #undefine suggests #define but not #undef
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: enhancement
Priority: P3
Component: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
t.c:24:2: error: invalid preprocessing directive #undefine; did you mean
#define?
24 | #undefine shift
| ^~~~~~~~
| define
I was not thinking when I was writing code for a second but the preprocessor
definitely could do better at the suggestion.
>From gcc-bugs-return-664256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 31 09:35:55 2019
Return-Path: <gcc-bugs-return-664256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86817 invoked by alias); 31 Dec 2019 09:35:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86804 invoked by uid 89); 31 Dec 2019 09:35:55 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-15.4 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=H*Ad:U*rth, HX-Languages-Length:1223, anybody
X-HELO: us-smtp-delivery-1.mimecast.com
Received: from us-smtp-2.mimecast.com (HELO us-smtp-delivery-1.mimecast.com) (207.211.31.81) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 31 Dec 2019 09:35:53 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t\x1577784951; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SCoIGxjgEKS7o529mrjIp6IRUNH1tgMP+pFZI2LMAuQ=; b=ajXSvpvPiEvQB//QIDRJJ6V52gvPbRhie3QGCizNmtXewQyD+2/xH0ljZ4MOEysXbNG4WU IGnOKA88pSXfJ5HTtY0n3wPCzPemTej9/UYAbbdvA9Bjstnsn26jnjPvSmlRW2MQ0YFDLq 6R9K0g35fojxrEDuMzYSuIwL9P70i2oReceived: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-421-VuVxMzQ5Okuj9fluJwnNZw-1; Tue, 31 Dec 2019 04:35:49 -0500
Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id B07B3800D4E; Tue, 31 Dec 2019 09:35:47 +0000 (UTC)
Received: from tucnak.zalov.cz (ovpn-116-112.ams2.redhat.com [10.36.116.112]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 1C1C7107A44C; Tue, 31 Dec 2019 09:35:43 +0000 (UTC)
Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.15.2/8.15.2) with ESMTP id xBV9Zf5D019144; Tue, 31 Dec 2019 10:35:42 +0100
Received: (from jakub@localhost) by tucnak.zalov.cz (8.15.2/8.15.2/Submit) id xBV9ZeOH019143; Tue, 31 Dec 2019 10:35:40 +0100
Date: Tue, 31 Dec 2019 09:35:00 -0000
From: Jakub Jelinek <jakub@redhat.com>
To: Ayush Mittal <ayush.m@samsung.com>
Cc: gcc-bugs@gcc.gnu.org, rth@redhat.com, jakub@gcc.gnu.org, avnish.jain@samsung.com, a.sahrawat@samsung.com, v.narang@samsung.com, maninder1.s@samsung.com, akhilesh.k@samsung.com
Subject: Re: [v2] libgomp: Add destructor to delete runtime env keys
Message-ID: <20191231093540.GX10088@tucnak>
Reply-To: Jakub Jelinek <jakub@redhat.com>
References: <CGME20191230141205epcas5p10746a819f7b169270122c56bf3309e18@epcas5p1.samsung.com> <1577714048-1939-1-git-send-email-ayush.m@samsung.com>
MIME-Version: 1.0
In-Reply-To: <1577714048-1939-1-git-send-email-ayush.m@samsung.com>
User-Agent: Mutt/1.11.3 (2019-02-01)
X-Mimecast-Spam-Score: 0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SW-Source: 2019-12/txt/msg02326.txt.bz2
Content-length: 1197
On Mon, Dec 30, 2019 at 07:24:08PM +0530, Ayush Mittal wrote:
> --- a/ChangeLog
> +++ b/ChangeLog
> @@ -1,3 +1,7 @@
> +2019-12-30 Ayush Mittal <ayush.m@samsung.com>
> +
> + * libgomp: Add destructor to delete runtime env keys
This line should have been instead something like:
* oacc-init.c (goacc_runtime_deinitialize): New function.
and it should go into libgomp/ChangeLog rather than toplevel ChangeLog.
Otherwise, LGTM.
Do you have anybody that can commit it for you, or do you want me to commit
it for you?
> 2019-12-20 Jerome Lambourg <lambourg@adacore.com>
>
> * MAINTAINERS (write_after_approval): Add myself.
> diff --git a/libgomp/oacc-init.c b/libgomp/oacc-init.c
> index 487a2cca61f..6aa5fd297d6 100644
> --- a/libgomp/oacc-init.c
> +++ b/libgomp/oacc-init.c
> @@ -858,6 +858,15 @@ goacc_runtime_initialize (void)
> goacc_host_init ();
> }
>
> +static void __attribute__((destructor))
> +goacc_runtime_deinitialize (void)
> +{
> +#if !(defined HAVE_TLS || defined USE_EMUTLS)
> + pthread_key_delete (goacc_tls_key);
> +#endif
> + pthread_key_delete (goacc_cleanup_key);
> +}
> +
> /* Compiler helper functions */
>
> attribute_hidden void
Jakub
next prev parent reply other threads:[~2019-12-31 6:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-93059-4@http.gcc.gnu.org/bugzilla/>
2019-12-29 3:33 ` euloanty at live dot com
2019-12-31 6:03 ` euloanty at live dot com [this message]
2020-09-02 14:51 ` cvs-commit at gcc dot gnu.org
2021-04-27 11:38 ` jakub at gcc dot gnu.org
2021-04-27 11:57 ` redi at gcc dot gnu.org
2021-10-06 10:40 ` m.cencora at gmail dot com
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=bug-93059-4-Uq3OSioNqP@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).