Ian A Mason
Might want to be honest then, and remove go from the supported language targets. At least warn the gullible user that they may be disappointed.
I am claiming that I could not get the --visitor pattern to work. Nor could I find any working examples of other people getting it to work. What I did...
Might be an idea then to keep the issue open, so that someone with time and inclination may succeed where others have failed.
@ocurr indeed I did see that issue thread, though may have incorrectly got the impression that the matter was still unresolved. The certainly was no link to any working visitor...
@davesisson, a simple working example would go a long way to "resolving" this issue. Having to flesh out all the methods still sounds a simpler task than trying to get...
I have searched high and low for this "race". Usually restarting the build works. I have no idea what is going on. I used the go tool for race detection....
Excellent. Thank you @DanielKriz! I will give you a tour later today.
Lets concentrate on `gclang`, `gclang++` is almost identical. The entry point is `gllvm/cmd/gclang/main.go` which passes all the work on to `shared.Compile(args, "clang")`, `args` here being the cmd line args not...
Note that you could pretty easily instrument the code to dump each pr object out to the log. Something like: ``` LogWarning("pr: %v", @pr) ``` say by adding this to...
By the way, do you mean that ``` Another interesting thing, clang doesn't know option --mfentry and I don't need it for my purposes, so I removed it from makefile...