[cfe-dev] clang library cycles

[don hinton]

On Aug 20, 2012, at 13:39, Sean Silva <silvas at purdue.edu> wrote:

> Why don't you try a Clang plugin?

I'd still have to solve the same problems, so I don't see any advantage right now. 

Btw, do these plugins fire during the linking stage as well?

> 
> A while back I wrote a clang plugin that incidentally does most of the
> setup you need:
> 
> https://github.com/chisophugis/clang_plugin_example
> 
> Then just rebuild all of clang hooking the plugin in with CXXFLAGS (I
> can be more specific if you need some more guidance).

I already do that.  I can generate HTML pages for the entire llvm/clang tree right now.  The only issue I still need to deal with concerns resolving links in the presents of cycles. 

However, this is a general problem, not something specific to clang.  

I'm trying to put my code up on github, but since I've never used it before, I'm not sure how long that might take.  Unfortunately, clang-tools-extra isn't included in the llvm-mirror repo, so I guess I need to remote it myself.  Advice welcome...

take care...
don

> 
> --Sean Silva
> 
> On Mon, Aug 20, 2012 at 11:42 AM, don hinton <don.hinton at gmx.com> wrote:
>> Hi Sean:
>> 
>> Here's the script.  It's real simple, but should give you and idea.
>> I can refine it later if you want.  I'd hoped to use it to do a topo
>> sort to get the correct order to generate documentation -- the
>> makefiles don't contain this info for libs.  However, the cycles plus
>> additional include files not in any lib subdirectory, e.g., in llvm,
>> make that impossible.
>> 
>> Therefore, I'll hack the makefiles to generate docs on the include
>> directories first, then use those tag files when generating the
>> libs.  I can then go back and redo the include directory and include
>> those tags to get everything wired up again -- sorta like multiple
>> passes in a linker.
>> 
>> take care...
>> don
>> 
>> 
>>> ----- Original Message -----
>>> From: Sean Silva
>>> Sent: 08/20/12 12:47 AM
>>> To: don hinton
>>> Subject: Re: [cfe-dev] clang library cycles
>>> 
>>> Could you produce some sort of visualization? My suspicion is that
>>> some of the cycles are unintended and a good visualization would
>>> pinpoint some problematic dependencies.
>>> 
>>> --Sean Silva
>>> 
>>> On Sun, Aug 19, 2012 at 8:12 PM, don hinton <don.hinton at gmx.com> wrote:
>>>> Hi:
>>>> 
>>>> I'd planned to document each clang library separately and include tag files for libraries each depends on, but have found cycles between several of the libs. Based on the #includes, cycles exist between AST, Basic, Sema, Parse, and Serialization.
>>>> 
>>>> At this point, I'll probably just do them all as one big lib, but am open to suggestion.
>>>> 
>>>> thanks...
>>>> don
>>>> _______________________________________________
>>>> cfe-dev mailing list
>>>> cfe-dev at cs.uiuc.edu
>>>> http://lists.cs.uiuc.edu/mailman/listinfo/cfe-dev
>>