Joel Rosdahl wrote:
(Sorry about the very delayed answer.)
No problem!
The patch looks good! I plan to only apply fixes to serious bugs on
3.1-maint, so I'll focus on the 3.2-maint version.
That it is OK, we can backport to 3.1 downstream if needed. Will focus on
master (and 3.2).
Two
Hi!
We've added support for gcc --coverage (including -fprofile-arcs and
-ftest-coverage) to ccache.
You can find the patches, for the maint versions, over on
https://github.com/itension/ccache:
https://github.com/itension/ccache/compare/3.1-maint...coverage-3.1.10.patch
(Sorry about the very delayed answer.)
No problem!
The patch looks good! I plan to only apply fixes to serious bugs on
3.1-maint, so I'll focus on the 3.2-maint version.
That it is OK, we can backport to 3.1 downstream if needed. Will focus on
master (and 3.2).
Here is a delayed update,
Hi Joel and all!
I also found the idea of storing failures interesting, and made a quick sample
implementation earlier:
https://github.com/itension/ccache/compare/store_failures
Feature is enabled by setting $CCACHE_STOREFAILURES
It does store the status as a separate file, but on the other
vkr wrote:
> Hello,
> I stumbled across this thread -
> https://lists.samba.org/archive/ccache/2012q2/000879.html which is years
> old,
> Coincidentally, I did some work along similar lines already, without
> realizing there was this discussion about this topic here,
> and I appreciate some
Hi all!
While the idea of using memcached with ccache is nothing new (*),
it seems to be more popular now with more memory being available...
* https://lists.samba.org/archive/ccache/2010q4/000686.html
https://lists.samba.org/archive/ccache/2013q2/001120.html
Pierre Tardy made a PR
Pierre Tardy wrote:
>
> i don't think getting rid out of the fs makes sense, but having memcache
> be available dynamically as an additional layer sounds fine.
>
> It does make a lot of sense for me as I have a high performance network,
> which is faster than local harddrive. So I would
> The option to switch the to_cache/from_cache can be made available
> separately, like it was in your PR. But it can use another config ?
> Probably needs some updating and refactoring, and it would be nice
> to try and keep the code duplication between them to a minimum...
>
> i.e. between the
Den 2015-12-07 kl. 04:48, skrev Mike Frysinger:
> On 02 Dec 2015 20:16, Pierre Tardy wrote:
>>> i don't think getting rid out of the fs makes sense, but having memcache
>>> be available dynamically as an additional layer sounds fine..
>>
>> It does make a lot of sense for me as I have a high
Andrew Stubbs wrote:
>> I would be interested in your thoughts on how to speed that part up.
>
> My implementation, which does a bunch of other things besides, hence why
> it's not fit to post[*], launches a background task which creates a unix
> domain socket in the cache directory (the windows
Ragnar Rova wrote:
> Thanks, i'll try it out. How stable is the memcached support?
>
>> It would also be interesting to test sharing a cache between containers
>> on different hosts, by using the "memcached" feature over the network:
>>
>>
Stéphane Charette wrote:
>> I created a new web page with some example graphs from the ccache plugins
>> in case anyone wants to see what it looks like:
>> https://www.ccoderun.ca/ccache-munin/
>
> ...and I should have mentioned, if anyone has more ideas on additional
> graphs I can extract from
Éric Chamberland wrote:
>>> How can I retrieve the documentation warnings with ccache? Do I do
>>> something wrong?
>> Hmm, since you are using CCACHE_CPP2=1 you *should* be getting
>> source-level warnings too. However, if you cached the previous
>> result without using that setting
Anders Björklund wrote:
> Michael Kolomeytsev wrote:
>> I've discovered that there is too small buffer size for IO in ccache: 16k
>> or 10k
>> (in hash_fd, copy_fd, copy_file).
>>
>
> But your observations are very interesting, and please post
> more if you have
Wilson Hong wrote:
> Hi ccache, I am trying to improve ccache build performance by
> improving cache hit rate. One thing I wanna try is to have multiple
> folders specified in CCACHE_DIR. Where first level is local cache,
> and second level in LAN NFS, third level on AWS s3. Ccache will start
>
Joel Rosdahl wrote:
>> If not, would be a good idea to implement that?
>
> I think that it could be interesting to investigate, but there are lots of
> things to think about before implementing it. For instance:
>
> What should happen on a cache miss? Should ccache store the result in all
>
Mats Nilsson wrote:
> Thank you very much!
>> Is there a way to instruct ccache to not cache the object file from a
>> specific compilation?
>>
> Look for the following configuration file options in the ccache(1) man
> page for disable, read_only, and read_only_direct to decide which one you
Mats Nilsson wrote:
> I'm a new-bee on ccache and I run clang on Ubuntu 14.04/64bit.
>
> Where can I find an apt-get package with ccache 3.2 or higher?
I think you have to request a backport, or do a PPA repository:
https://wiki.ubuntu.com/UbuntuBackports
https://help.launchpad.net/Packaging/PPA
Mats Nilsson wrote:
> I'm experimenting with having a common NFS-disk as cacche for all build
> agents in TeamCity.
It works, but is kinda slow and full of issues (like cleaning, for
instance). Using NFS only as secondary cache works (somewhat) better.
I wanted to focus on memcached, but
Hi ccache!
We have earlier had some problems on testing on other *Unix* platforms,
like Solaris or FreeBSD. Mostly because none of us are running those...
https://github.com/ccache/ccache/issues/148
https://svnweb.freebsd.org/ports/head/devel/ccache/
We are also seeing some bugs that are
Jean-Dominique GASCUEL wrote:
> Dear ccache developers,
>
> I just started a fork to try to make ccache compatible with Visual C/C++
> compiler (cl), so one can use it with msbuild or nmake based projects...
> You can review the current state here: https://github.com/jd-gascuel/ccache
>
> Current
Aashaka Shah wrote:
> I recently came across ccache as I have an assignment to think of a novel
> compiler design or related problem, and having a cache for compilers was
> the first thing that came to my mind. I thought of trying it out on
> QuantLib, a financial computation library.
Hi! It
Jimmy Yue wrote:
> I was wondering if anybody in this list has tried support swift and maybe
> even ibtool. I'm looking to implement this myself if there's a gap here,
> but if anybody has tried it before and ran into problems I'd love to know.
I think the only thing Swift has in common with C++
Andreas Wettstein wrote:
> In function `make_relative_path` (file `ccache.c`), the given
> path is made "canonic" before it is converted to a path relative
> to the current working directory. In particular, "canonic" means
> that symbolic links are removed. I understand that it makes
> sense to
Karanam Suryanarayana Rao Venkata Krishna wrote:
> Hello,
> I think I discovered a scenario that results in cache misses in spite of
> using CCACHE_BASEDIR.
> Consider the following command:
>
> CCACHE_BASEDIR=$PWD /bin/bash -c "ccache clang++
> -fdebug-prefix-map=/proc/self/cwd= -g -c -MD -MF
Den 2018-03-14 kl. 19:31, skrev Basile Starynkevitch via ccache:
>
>
> On 03/14/2018 06:54 PM, Jason Zhou via ccache wrote:
>> Hi,
>>
>> I am looking for an efficient way to correctly combine multiple ccache from
>> hundreds of build machines into a single ccache to build a super set ccache.
>
26 matches
Mail list logo
