From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from s810.sureserver.com (s810.sureserver.com [195.42.142.37]) by sourceware.org (Postfix) with ESMTPS id E383A3858C52 for ; Fri, 9 Sep 2022 16:41:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org E383A3858C52 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=strikr.io Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=strikr.io DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=strikr.io; h=message-id :reply-to:from:to:subject:date:mime-version:in-reply-to :references:content-type:content-transfer-encoding; s=dkim; bh=A bszs/DhM3JxfM5rGJw7Fbdv83p5TwLch5Y1NgK8MbE=; b=TAYY7KwRc/3j2DFSr 1mUb3y45bhtaoxAMROYhEwdddNZJ8ZZKvwSQg14xMv+Kq5svSTvqva5ueZ04ECqr zsk1PiSEcdng3/mznfJnVBBPTGagiqPFoiyPoCJ6BL6iOqr/ZjVVrvKXNWw514IO XBs4fFLijdOtlEkGDqgh+3jcbY= Received: (qmail 41730 invoked by uid 1021); 9 Sep 2022 16:41:40 -0000 Message-ID: <20220909164140.41729.qmail@s810.sureserver.com> Reply-To: "=?utf-8?Q?SAIFI?=" From: "=?utf-8?Q?SAIFI?=" To: gcc@gcc.gnu.org Subject: =?utf-8?B?UmU6IFtSRkNdIGRhdGFiYXNlIHdpdGggQVBJIGluZm9ybWF0aW9u?= Date: Fri, 09 Sep 2022 16:41:40 +0000 MIME-Version: 1.0 X-Mailer: WebMail 2.55.13.14 X-Suremail-Sender: 223_231_178_167 X-Originating-Email: msk@strikr.io In-Reply-To: References: Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,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 List-Id: > -------Original Message------- > From: Jonathan Wakely > > > Am i missing something here ? > > OK ... > > This script would be needed to bootstrap GCC. Using C++ would mean > that we need to restrict it to C++11 (since that's all that is needed > for bootstrapping GCC), and deal with all the peculiarities of the > platform's C++ compiler and linker. We already do that to build GCC > itself, but now we'd also need to do it for this tool that has to be > built first, and would need to use all the right CXXFLAGS and LDFLAGS > etc. to compile on the build machine (which might have unconventional > linker properties, for example). Perhaps this is something the current build scripts take care of anyway. Is it possible to reuse ? > We'd also need to implement a CSV parser from scratch. > Would any of the C++11 compliant CSV parsing libraries make the cut in your analysis ? Vince CSV parser (RFC4180 + flavours) https://github.com/vincentlaucsb/csv-parser C++11 header only (MT can be turned on/off). https://github.com/ben-strasser/fast-cpp-csv-parser If not, Is there is something else that is needed for the CSV parsers to qualify ? Thanks for sharing your perspective. Much appreciated ! warm regards Saifi.