[LLVMdev] dragonegg FSF gcc merge?

Jack Howarth howarth at bromo.med.uc.edu
Fri Apr 9 12:09:00 PDT 2010

On Fri, Apr 09, 2010 at 10:14:30AM -0700, Chris Lattner wrote:
> On Apr 9, 2010, at 10:11 AM, Jeffrey Yasskin wrote:
> >> 
> >> Duncan,
> >>   I'll broach the topic on gcc at gcc.gnu.org and see what the
> >> responses are. Why can't dragon-egg live in both places and
> >> be re-merged regularly?
> > 
> > Re-merging it regularly sounds like it would require extra work beyond
> > what Duncan's already doing to maintain it. Please don't suggest other
> > people do extra work unless you're also offering to do it for them.
> Random thought:
> If the GCC community is actually interested in this, it would probably make sense for the gcc tree to have a version of dragonegg that worked with the last released version of llvm, not for it to try to chase tot.  The LLVM tree would have a version of dragonegg that chased llvm ToT but worked with hte last released version of gcc.

This certainly makes sense. The llvm repository dragonegg would be built
against the current release of FSF gcc and the development version of llvm
while the FSF gcc repository dragonegg would be built against the development
gcc version and the current release of llvm. Upon either a llvm or FSF gcc
release, the two repositories would merge.

> Of course, this would depend on someone being willing to do the work :)

I would try to be an optimist (that llvm represents enough value to drive
the dragonegg development once folks are exposed to it).

> -Chris

More information about the llvm-dev mailing list