beckerzito

Results 12 comments of beckerzito

issue building with the following options: ./build --mode=gcc-9.3.0 --arch=x86_64 --threads=posix --exceptions=sjlj --enable-languages=c,c++

I'm having the same problem. Any update on that?

issue building with the following options: ./build --mode=gcc-9.3.0 --arch=x86_64 --threads=posix --exceptions=sjlj --enable-languages=c,c++

Master

issue building with the following options: ./build --mode=gcc-9.3.0 --arch=x86_64 --threads=posix --exceptions=sjlj --enable-languages=c,c++

@niXman I realized that it haves using the 'sjlj' exception model

Gcov only reports coverage results for modules which have a test file

@tobyjwebb I saw that this feature was merged to master, but I still have a question. On the optional list of files to exclude, is it possible to add an...

Improved support for separate out directories

Hey @aschlicht just to let you know that I really enjoyed this feature! I have been looking for a way to generate coverage reports to the same module based on...

Improved support for separate out directories

@mvandervoord any plan to integrate that? This is a very useful feature! Thank you!

Improved support for separate out directories

Hey guys, any update on this feature @mvandervoord . I'm also needing this update at work, but we don't want to use versions under development. We need to be using...

Errno::E2BIG: Arg list too long

@mvandervoord help me out here! Is there any solution already done for that?

Errno::E2BIG: Arg list too long

> Maybe not related, but I wonder how linux does it... The link list is probably really long, so there might be some trick to avoid that. > > Are...

Errno::E2BIG: Arg list too long

Yes, the point is that since the start of the command "gcc.exe" until the end of it with "-DTEST -DGNU_COMPILER", the complete command has almost 37.815 characters. So, I see...