Re: [v8-users] Error graph-builder-tester.h:172:56: error: no matching function for call to 'v8::internal::compiler::SimplifiedOperatorBuilder::ChangeFloat64ToTagged()' when trying to build V8 with GC

2017-08-02 Thread Jakob Kummerow 
On Wed, Aug 2, 2017 at 1:04 PM, Georgi Sotirov  wrote:

> Yes, sure. We have gcc-4.8 bots on our waterfall and they're happy. Feel
>> free to submit a patch  for
>> gcc-7.1 support :-)
>>
>
> GCC 4.8 is at least 4 years old and as I see in GitHub V8 is under very
> active development, so strange that only newer GCC versions are not
> considered...
>

GCC 4.8 is what ships in Ubuntu Trusty, which is still our main development
platform. Usually ensuring that older toolchains are still supported is
more difficult (and hence more important) than supporting newer toolchains.
Most people build with the bundled clang; GCC support is mostly community
driven at this point. The fact that it has been broken for a while until
you found it tells you how few people care about it...


> A patch commenting out the offending function? OK, I could submit such
> patch, but I'm not sure this is the right solution and I do not know V8's
> source at all to make a real fix.
>

Unused functions, especially in tests, can just be deleted. (No point in
commenting out code that doesn't work, just drop it.)


> When I asked about version, I did mean version, not cloning instructions.
>> "fetch v8" gives you a different thing every day, because V8 is under
>> active development. (You can "git pull && gclient sync" to stay up to date
>> after the initial "fetch v8".)
>>
>
> Yes, I got you point, but I find V8 version numbering as confusing as the
> official documentation and the procedure
>  I
> referred was the only one working for me so far. And I pretty much
> understand what cloning means, so at least it's clear the problem is in the
> most recent source. However, I'm just trying to build V8 library without
> having to read tons of documentation and learning new tools (mostly used
> internally in Google as it seems), because V8 is not my primary development
> interest, but just a dependency I need to satisfy.
>

I wasn't asking you to learn any new tool or understand V8 version
numbering. I was just saying: next time you report a problem, please
indicate the version you were using. The git hash of your most recent
commit is perfectly fine for that.


> Anyway, now that I was able to build V8 with the help of the people from
> this group (including you) how could I install it? There is no "make
> install":
>
> $ make install
> $ make: *** No rule to make target 'install'.  Stop.
>
>
Indeed, there is no "make install". V8 is designed to be embedded/bundled;
installing it as a system library does not make much sense.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] Error graph-builder-tester.h:172:56: error: no matching function for call to 'v8::internal::compiler::SimplifiedOperatorBuilder::ChangeFloat64ToTagged()' when trying to build V8 with GC

2017-08-02 Thread Georgi Sotirov 


> Feel free to delete the offending function 
> (in test/cctest/compiler/graph-builder-tester.h:171-173), it doesn't seem 
> to be used (which is presumably why clang doesn't complain here).
>

Sure, I did it and build continues, but isn't this supposed to be fixed 
upstream? I though V8 is buildable with both Clang and GCC.
 

> I'm trying to build V8 with the following command:
>

Sorry, cloned from the source repository like this 
:

$ git clone https://chromium.googlesource.com/chromium/tools/depot_tools.git
$ export PATH=`pwd`/depot_tools:"$PATH"
$ fetch v8

Because cloning directly V8 from GitHub as shown below results in error 
about missing third party software:

$ git clone 'https://github.com/v8/v8.git'
$ time make V=1 ia32.release GYPFLAGS='-Dclang=0 -Dwerror= 
-Dcomponent=shared_library'
make: *** No rule to make target 'third_party/icu/icu.gypi', needed by 
'out/Makefile.ia32.release'.  Stop.

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [v8-users] 32-bit powerpc -- a lost cause?

2017-08-02 Thread michael_dawson 
Based on current priorities, going forward 32 bit is not going to be a 
priority.  We will not be testing it in v8 or the Node.js repos.

On Tuesday, August 1, 2017 at 10:40:32 AM UTC-4, Håvard Eidnes wrote:
>
> Hi,
>
> although NetBSD runs on various PPC hardware, some possibly also with no 
> FPU,
> my personal interest is in >= G4 (possibly >= G3), which AFAIK means 
> 32-bit but with FPU.
> However, reading what you write I get the sense that you're going to drop 
> all 32-bit PPC support?
>
> Regards,
>
> - Håvard
>
> fredag 28. juli 2017 00.10.42 UTC+2 skrev bjai...@ca.ibm.com følgende:
>>
>> Hi,
>>
>> We currently do not support PPC 32bit hardware and going forward with 
>> Node8 will be dropping support for PPC 32bit mode builds on PPC 64bit 
>> architecture. Also, it is possible the 32 bit PPC system you are using 
>> is only implementing a subset of the architecture and missing FPU.
>>
>> Regards,
>> Jaideep
>>
>  
>

-- 
-- 
v8-users mailing list
v8-users@googlegroups.com
http://groups.google.com/group/v8-users
--- 
You received this message because you are subscribed to the Google Groups 
"v8-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to v8-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.