Message ID | 20230426165347.599616-1-apinski@marvell.com |
---|---|
State | Unresolved |
Headers |
Return-Path: <gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:b0ea:0:b0:3b6:4342:cba0 with SMTP id b10csp381500vqo; Wed, 26 Apr 2023 09:54:50 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7q/M+D7w2HQ4kiHRSQeLks7k++hse+jpH7sIuAW+4WFN7YPAqDiELw4F+a+ob0VALUNZx0 X-Received: by 2002:aa7:c796:0:b0:509:f4d8:ac5b with SMTP id n22-20020aa7c796000000b00509f4d8ac5bmr5616966eds.28.1682528090212; Wed, 26 Apr 2023 09:54:50 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1682528090; cv=none; d=google.com; s=arc-20160816; b=YWq5UesKgo22HT1g0UjSohJFs7Z+44+HoEOzDemgztJoqpV3me0za7g261S6syTYxF 8ka5jWDaav9yxFH2JUw+eLoFvYkkPetNJOYWcQ8wBzZSAA6prLze7SrTupVpRCh980Cx IQLb7eIL8s7khnZjTHT0TkeSpTDtDU5omBTZe5kkXRU8edHtVxl1Emgh9WPe3ScGPSU6 9wENj1iwsRTK1Hy7i/O9jCcgyQ5fyM3JJG45GRKA8V2eGOSAKbfBCfqGhTPJ9QBpNEWX IA//3Z+0/BmZeyU1a2KQtumCTqTrdu7/iXvUZWtm4Qvb1a5/22U/Qnk/0Rul1imK4/fW AN6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=sender:errors-to:reply-to:from:list-subscribe:list-help:list-post :list-archive:list-unsubscribe:list-id:precedence :content-transfer-encoding:mime-version:message-id:date:subject:cc :to:dmarc-filter:delivered-to:dkim-signature:dkim-filter; bh=bfP8ZuRTVtT5/DEjjcaxpKiJl0fToZrzo0fUFA9bzw4=; b=cw9Y4U2Z7LPDaex/7aHya6vCV5Dd2cCFCMZ0qziTUZzRskMt6IHSA2L+72YECe18GR QdTG4BUvm8QyMGixUE8b8G+gH2tNj/MDqSzU2OdgcuVZcJI9WhH1kWO3vvMAPLAfPgYp a/GHWQI8WUQE+cVPhG1cSZd9BzQEwu3RUV2APZzhNO+sNKVnZ9LcrbRuAUT3Z3Kv1Lxq p1BC+noDTbG86125t0JoqM3D4/3KI/lniveWmBJABZLHP0AU3n2UMrtAL5N8viOK7x03 ByUL3zwUd6OcEpbiEbJBa1vosngcYnc38JH25EgvHBmKwZRDWQBgwGs79+VNLOun/0gz j0WQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gcc.gnu.org header.s=default header.b=cLmO5t4X; spf=pass (google.com: domain of gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org designates 8.43.85.97 as permitted sender) smtp.mailfrom="gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gnu.org Received: from sourceware.org (server2.sourceware.org. [8.43.85.97]) by mx.google.com with ESMTPS id k9-20020a05640212c900b00509c6e8905dsi9034692edx.86.2023.04.26.09.54.49 for <ouuuleilei@gmail.com> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 26 Apr 2023 09:54:50 -0700 (PDT) Received-SPF: pass (google.com: domain of gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org designates 8.43.85.97 as permitted sender) client-ip=8.43.85.97; Authentication-Results: mx.google.com; dkim=pass header.i=@gcc.gnu.org header.s=default header.b=cLmO5t4X; spf=pass (google.com: domain of gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org designates 8.43.85.97 as permitted sender) smtp.mailfrom="gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org"; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=gnu.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 1A2EE3858C27 for <ouuuleilei@gmail.com>; Wed, 26 Apr 2023 16:54:49 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1A2EE3858C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1682528089; bh=bfP8ZuRTVtT5/DEjjcaxpKiJl0fToZrzo0fUFA9bzw4=; h=To:CC:Subject:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=cLmO5t4Xt3KOFDxuZqsQjYCLwrCvL9vj866GMl5dZ4XoCpPT7GZLmjV7a/J0slmIb ZT7cLoCR7qwNTwSBIjido7G74FO12Sxp7c2JpfVz6wLwaZAX7qeMqfO/r64o/YZGon umnc9hQCorVrTFdbMfhE09Ii5wF0Pgq4Po/T7k8s= X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from mx0b-0016f401.pphosted.com (mx0b-0016f401.pphosted.com [67.231.156.173]) by sourceware.org (Postfix) with ESMTPS id BD9243858C20 for <gcc-patches@gcc.gnu.org>; Wed, 26 Apr 2023 16:54:03 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org BD9243858C20 Received: from pps.filterd (m0045851.ppops.net [127.0.0.1]) by mx0b-0016f401.pphosted.com (8.17.1.19/8.17.1.19) with ESMTP id 33QFl6JK031240 for <gcc-patches@gcc.gnu.org>; Wed, 26 Apr 2023 09:54:03 -0700 Received: from dc5-exch02.marvell.com ([199.233.59.182]) by mx0b-0016f401.pphosted.com (PPS) with ESMTPS id 3q4f3pf557-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <gcc-patches@gcc.gnu.org>; Wed, 26 Apr 2023 09:54:03 -0700 Received: from DC5-EXCH02.marvell.com (10.69.176.39) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server (TLS) id 15.0.1497.48; Wed, 26 Apr 2023 09:54:00 -0700 Received: from maili.marvell.com (10.69.176.80) by DC5-EXCH02.marvell.com (10.69.176.39) with Microsoft SMTP Server id 15.0.1497.48 via Frontend Transport; Wed, 26 Apr 2023 09:54:00 -0700 Received: from vpnclient.wrightpinski.org.com (unknown [10.69.242.187]) by maili.marvell.com (Postfix) with ESMTP id 9DD3D3F703F; Wed, 26 Apr 2023 09:54:00 -0700 (PDT) To: <gcc-patches@gcc.gnu.org> CC: Andrew Pinski <apinski@marvell.com> Subject: [PATCH] GCC-13/changes: Add note about iostream usage Date: Wed, 26 Apr 2023 09:53:47 -0700 Message-ID: <20230426165347.599616-1-apinski@marvell.com> X-Mailer: git-send-email 2.31.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Proofpoint-ORIG-GUID: wCopimVQOqOz-_BEbOWCLeOXTfQk4wXc X-Proofpoint-GUID: wCopimVQOqOz-_BEbOWCLeOXTfQk4wXc X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.254,Aquarius:18.0.942,Hydra:6.0.573,FMLib:17.11.170.22 definitions=2023-04-26_08,2023-04-26_03,2023-02-09_01 X-Spam-Status: No, score=-14.5 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org> List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe> List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/> List-Post: <mailto:gcc-patches@gcc.gnu.org> List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help> List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe> From: Andrew Pinski via Gcc-patches <gcc-patches@gcc.gnu.org> Reply-To: Andrew Pinski <apinski@marvell.com> Errors-To: gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org Sender: "Gcc-patches" <gcc-patches-bounces+ouuuleilei=gmail.com@gcc.gnu.org> X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1764258574881369748?= X-GMAIL-MSGID: =?utf-8?q?1764258574881369748?= |
Series |
GCC-13/changes: Add note about iostream usage
|
|
Checks
Context | Check | Description |
---|---|---|
snail/gcc-patch-check | warning | Git am fail log |
Commit Message
Andrew Pinski
April 26, 2023, 4:53 p.m. UTC
This adds a note about iostream usage so it does not catch others in surpise like it has already. OK? --- htdocs/gcc-13/changes.html | 5 +++++ 1 file changed, 5 insertions(+)
Comments
On 26/04/23 09:53 -0700, Andrew Pinski wrote: >This adds a note about iostream usage so it does not catch others >in surpise like it has already. > >OK? Thanks, I agree we should add something, but have some comments below. >--- > htdocs/gcc-13/changes.html | 5 +++++ > 1 file changed, 5 insertions(+) > >diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html >index 70732ec0..7c83f7c4 100644 >--- a/htdocs/gcc-13/changes.html >+++ b/htdocs/gcc-13/changes.html >@@ -25,6 +25,11 @@ You may also want to check out our > <!-- .................................................................. --> > <h2>Caveats</h2> > <ul> >+ <li>libstdc++ uses constructors inside the library to initialize std::cout/std::cin, etc. >+ instead of having it done in each source which uses iostream header. We should use code font for std::cout, std::cin and iostream, and style it as <iostream> not just iostream. >+ This requires you to make sure the dynamic loader to load the new libstdc++v3 library >+ (examples of how to do this is to use -Wl,-rpath,... while linking or LD_LIBRARY_PATH >+ while running the program). </li> I think it would be better to link to https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dynamic_or_shared.html#manual.intro.using.linkage.dynamic How about: <li>For C++, construction of the global iostream objects <code>std::cout</code>, <code>std::cin</code> etc. is now done inside the standard library, instead of in every source file that includes the <code><iostream></code> header. This change improves the start-up performance of C++ programs, but it means that code compiled with GCC 13.1 will crash if the correct version of <code>libstdc++.so</code> is not used at runtime. See the <a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dynamic_or_shared.html#manual.intro.using.linkage.dynamic">documentation</a> about using the right <code>libstdc++.so</code> at runtime. </li>
On Wed, Apr 26, 2023 at 12:07 PM Jonathan Wakely via Gcc-patches <gcc-patches@gcc.gnu.org> wrote: > > On 26/04/23 09:53 -0700, Andrew Pinski wrote: > >This adds a note about iostream usage so it does not catch others > >in surpise like it has already. > > > >OK? > > Thanks, I agree we should add something, but have some comments below. > > >--- > > htdocs/gcc-13/changes.html | 5 +++++ > > 1 file changed, 5 insertions(+) > > > >diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html > >index 70732ec0..7c83f7c4 100644 > >--- a/htdocs/gcc-13/changes.html > >+++ b/htdocs/gcc-13/changes.html > >@@ -25,6 +25,11 @@ You may also want to check out our > > <!-- .................................................................. --> > > <h2>Caveats</h2> > > <ul> > >+ <li>libstdc++ uses constructors inside the library to initialize std::cout/std::cin, etc. > >+ instead of having it done in each source which uses iostream header. > > We should use code font for std::cout, std::cin and iostream, and > style it as <iostream> not just iostream. > > >+ This requires you to make sure the dynamic loader to load the new libstdc++v3 library > >+ (examples of how to do this is to use -Wl,-rpath,... while linking or LD_LIBRARY_PATH > >+ while running the program). </li> > > I think it would be better to link to > https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dynamic_or_shared.html#manual.intro.using.linkage.dynamic > > How about: > > <li>For C++, construction of the global iostream objects > <code>std::cout</code>, <code>std::cin</code> etc. is now done > inside the standard library, instead of in every source file that > includes the <code><iostream></code> header. This change > improves the start-up performance of C++ programs, but it means that > code compiled with GCC 13.1 will crash if the correct version of > <code>libstdc++.so</code> is not used at runtime. See the > <a href="https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dynamic_or_shared.html#manual.intro.using.linkage.dynamic">documentation</a> > about using the right <code>libstdc++.so</code> at runtime. > </li> This looks better than my version. Thanks, Andrew > >
diff --git a/htdocs/gcc-13/changes.html b/htdocs/gcc-13/changes.html index 70732ec0..7c83f7c4 100644 --- a/htdocs/gcc-13/changes.html +++ b/htdocs/gcc-13/changes.html @@ -25,6 +25,11 @@ You may also want to check out our <!-- .................................................................. --> <h2>Caveats</h2> <ul> + <li>libstdc++ uses constructors inside the library to initialize std::cout/std::cin, etc. + instead of having it done in each source which uses iostream header. + This requires you to make sure the dynamic loader to load the new libstdc++v3 library + (examples of how to do this is to use -Wl,-rpath,... while linking or LD_LIBRARY_PATH + while running the program). </li> <li>OpenMP offloading to Intel MIC has been removed.</li> <li>The support for the <code>cr16-elf</code>, <code>tilegx*-linux</code>, <code>tilepro*-linux</code>, <code>hppa[12]*-*-hpux10*</code>, <code>hppa[12]*-*-hpux11*</code>