I don't think that should be necessary, GCC has supported all of C++14 since version 6 (mid 2016), and all of C++17 since last year.
On Wednesday, February 14, 2018 at 10:22:49 AM UTC, Yang Guo wrote: > > I think you also need to disable cxx14. > > On Wed, Feb 14, 2018, 09:37 Ben Noordhuis <[email protected] > <javascript:>> wrote: > >> On Wed, Feb 14, 2018 at 12:59 AM, <[email protected] <javascript:>> >> wrote: >> > I'm working on a RISC-V target for V8. Currently the LLVM toolchain for >> > RISC-V is less mature and accessible than the GCC one (which is >> available >> > upstream as of GCC 7.1 or thereabouts), so I'm wondering if and how I >> might >> > could the V8 build to use GCC to compile V8 (so that I can run V8 as a >> whole >> > in QEMU before getting the in-tree simulator up and running). >> > >> > Thanks. :- ) >> >> It's been some time since I last tried it but passing `is_clang=false >> use_sysroot=false` to tools/dev/v8gen.py should do it. >> >> -- >> -- >> v8-dev mailing list >> [email protected] <javascript:> >> http://groups.google.com/group/v8-dev >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
