public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: SAIFI <msk@strikr.io>
To: gcc@gcc.gnu.org
Subject: Re: [RFC] database with API information
Date: Fri, 09 Sep 2022 16:41:40 +0000	[thread overview]
Message-ID: <20220909164140.41729.qmail@s810.sureserver.com> (raw)
In-Reply-To: <CAH6eHdQtfrNSYU+K-=wjKEMY+N3gAB344+K=oLL7h3JLN+CT_Q@mail.gmail.com>

>  -------Original Message-------
>  From: Jonathan Wakely <jwakely.gcc@gmail.com>
>  
>  > 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.

  reply	other threads:[~2022-09-09 16:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07  6:22 Ulrich Drepper
2022-09-07 10:56 ` Richard Sandiford
2022-09-07 12:33   ` Martin Liška
2022-09-09 15:26     ` Iain Sandoe
2022-09-09 17:07       ` Ulrich Drepper
2022-09-09 17:13         ` Iain Sandoe
2022-09-09 11:40 ` SAIFI
2022-09-09 11:47   ` Jonathan Wakely
2022-09-09 12:29     ` SAIFI
2022-09-09 15:06       ` Jonathan Wakely
2022-09-09 16:41         ` SAIFI [this message]
2022-09-09 18:21           ` Jonathan Wakely
2022-09-09 18:40             ` SAIFI
2022-09-09 20:05               ` Jonathan Wakely

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=20220909164140.41729.qmail@s810.sureserver.com \
    --to=msk@strikr.io \
    --cc=gcc@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).