Perry Smith wrote:
> How do I keep track of the "LTO" design process? I may not be able to
> help 'cause I don't know enough about gcc's internals but I'd like to
> if possible.
I think the best approach is to subscribe to gcc@gcc.gnu.org and
[EMAIL PROTECTED] That's where discussion and patc
Perry Smith <[EMAIL PROTECTED]> writes:
> How do I keep track of the "LTO" design process? I may not be able
> to help 'cause I don't know enough about gcc's internals but I'd like
> to if possible.
You read the mailing list [EMAIL PROTECTED] So you're already doing
the right thing.
Ian
How do I keep track of the "LTO" design process? I may not be able
to help 'cause I don't know enough about gcc's internals but I'd like
to if possible.
On Feb 13, 2006, at 2:47 PM, Mark Mitchell wrote:
Gabriel Dos Reis wrote:
Tom Tromey <[EMAIL PROTECTED]> writes:
[...]
| I think it wo
Gabriel Dos Reis wrote:
> Tom Tromey <[EMAIL PROTECTED]> writes:
>
> [...]
>
> | I think it would be more advisable to design something with AST
> | database generation as an explicit goal.
>
> I believe that is a sensible approach, one that I thought a by-product
> of the "Link Time Optimizatio
Tom Tromey <[EMAIL PROTECTED]> writes:
[...]
| I think it would be more advisable to design something with AST
| database generation as an explicit goal.
I believe that is a sensible approach, one that I thought a by-product
of the "Link Time Optimization" proposal. Such a format will be
tremen
> "Perry" == Perry Smith <[EMAIL PROTECTED]> writes:
Perry> gcc/g++ has the -M options to help in creating Makefiles. It struck
Perry> me this morning that a similar switch to help in the creation of a
Perry> database to use to create a "cscope" type facility would be very
Perry> nice. It wo
gcc/g++ has the -M options to help in creating Makefiles. It struck
me this morning that a similar switch to help in the creation of a
database to use to create a "cscope" type facility would be very
nice. It would be nice if both cpp and gcc/g++ had this ability.
Has/Does anything like t
