Re: [v8-dev] Building with GCC

2020-03-25 Thread 吴伟
Hi there,

FYI, we (PLCT group in Chinese Academy of Sciences) are working on this.
Hopefully we would finish porting V8 to RISC-V[0] before July, 2020[1], and
start to contribute to upstream & maintain.

WIP patches will be available at [2] in late April. All comments or 
suggestions are
welcome ;)

[0] both RV32 and RV64.
[1] Pass SunSpider, Octane and Kraken. Support for WASM is postponed to 
Nov, 2020.
[2] https://github.com/isrc-cas/v8-riscv

On Thursday, November 28, 2019 at 4:44:53 PM UTC+8, Yang Guo wrote:
>
> There are no plans to port V8 to RISC-V. If you are interested to 
> implement and maintain, please reach out to hab...@chromium.org 
>  and hpa...@chromium.org .
>
> Basic requirements are:
>  - signing Google's CLA 
>  - commitment to maintain
>  - a simulator (example 
> ) 
> to execute generated code for cross-platform testing.
>
> Cheers,
>
> Yang
>
> On Wed, Nov 27, 2019 at 11:15 PM Nick K  > wrote:
>
>> Curious about the status of your efforts to port V8 to RISC-V. RISC-V 
>> backends are currently upstream in both the Clang/LLVM and GNU toolchains. 
>> Please let me know if/how I can contribute!
>>
>> On Wednesday, February 14, 2018 at 7:20:41 AM UTC-8, 
>> aa...@correspondwith.me wrote:
>>>
>>> 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  wrote:

> On Wed, Feb 14, 2018 at 12:59 AM,   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
> v8-...@googlegroups.com
> 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 v8-dev+un...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
 -- 
>> -- 
>> v8-dev mailing list
>> v8-...@googlegroups.com 
>> 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 v8-...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/v8-dev/7d877035-633d-48a5-8590-cf71eb531f90%40googlegroups.com
>>  
>> 
>> .
>>
>

-- 
-- 
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-dev/1136ae58-297b-4c28-8652-ae685abd43ec%40googlegroups.com.


Re: [v8-dev] Building with GCC

2019-11-28 Thread Yang Guo
There are no plans to port V8 to RISC-V. If you are interested to implement
and maintain, please reach out to habl...@chromium.org and
hpa...@chromium.org.

Basic requirements are:
 - signing Google's CLA 
 - commitment to maintain
 - a simulator (example
)
to execute generated code for cross-platform testing.

Cheers,

Yang

On Wed, Nov 27, 2019 at 11:15 PM Nick K  wrote:

> Curious about the status of your efforts to port V8 to RISC-V. RISC-V
> backends are currently upstream in both the Clang/LLVM and GNU toolchains.
> Please let me know if/how I can contribute!
>
> On Wednesday, February 14, 2018 at 7:20:41 AM UTC-8,
> aa...@correspondwith.me wrote:
>>
>> 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  wrote:
>>>
 On Wed, Feb 14, 2018 at 12:59 AM,   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
 v8-...@googlegroups.com
 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 v8-dev+un...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.

>>> --
> --
> v8-dev mailing list
> v8-dev@googlegroups.com
> 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 v8-dev+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/v8-dev/7d877035-633d-48a5-8590-cf71eb531f90%40googlegroups.com
> 
> .
>

-- 
-- 
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-dev/CAFSTc_jg0zSMww4-PfZdhyGXq2Z_5WxyPCmnMH0tFqToBjFxFA%40mail.gmail.com.


Re: [v8-dev] Building with GCC

2019-11-27 Thread Nick K
Curious about the status of your efforts to port V8 to RISC-V. RISC-V 
backends are currently upstream in both the Clang/LLVM and GNU toolchains. 
Please let me know if/how I can contribute!

On Wednesday, February 14, 2018 at 7:20:41 AM UTC-8, 
aa...@correspondwith.me wrote:
>
> 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  wrote:
>>
>>> On Wed, Feb 14, 2018 at 12:59 AM,   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
>>> v8-...@googlegroups.com
>>> 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 v8-dev+un...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
-- 
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/v8-dev/7d877035-633d-48a5-8590-cf71eb531f90%40googlegroups.com.


Re: [v8-dev] Building with GCC

2018-02-14 Thread aaron
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  > wrote:
>
>> On Wed, Feb 14, 2018 at 12:59 AM,   
>> 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
>> v8-...@googlegroups.com 
>> 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 v8-dev+un...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
-- 
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [v8-dev] Building with GCC

2018-02-14 Thread aaron
Thanks, I'll give it a try!

On Wednesday, February 14, 2018 at 9:37:00 AM UTC, Ben Noordhuis wrote:
>
> On Wed, Feb 14, 2018 at 12:59 AM,   
> 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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [v8-dev] Building with GCC

2018-02-14 Thread Yang Guo
I think you also need to disable cxx14.

On Wed, Feb 14, 2018, 09:37 Ben Noordhuis  wrote:

> On Wed, Feb 14, 2018 at 12:59 AM,   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
> v8-dev@googlegroups.com
> 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 v8-dev+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
v8-dev mailing list
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [v8-dev] Building with GCC

2018-02-14 Thread Ben Noordhuis
On Wed, Feb 14, 2018 at 12:59 AM,   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
v8-dev@googlegroups.com
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 v8-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.